Accessibility
Cetagon is a tool people use to manage their own money. It should be usable by everyone who relies on it, including people who navigate by keyboard, use a screen reader or screen magnifier, control their computer by voice, or need reduced motion.
This page states the standard we build to, what is already in place, what we know is not good enough yet, and how to reach a person if something in the Service blocks you.
The standard we build to.
We use the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA as our internal bar for new work. WCAG 2.1 AA is the specification most commonly referenced in accessibility law and policy in the United States and Canada, including under the Americans with Disabilities Act and the Accessible Canada Act.
We are not claiming full conformance. Parts of the Service meet that bar and parts do not. We would rather publish the specific gaps than a blanket claim you cannot rely on. What is missing is listed in what we know is not there yet, and we update this page as items close.
What is already in place.
- Keyboard operation. Interactive controls are reachable and operable by keyboard, and every focused control draws a visible focus ring. Menus, dialogs, and comboboxes are built on accessible primitives that manage focus and expose the right roles and states.
- Page structure. Every page renders a single main landmark, navigation regions carry distinct labels, and headings run in order. A build-time check blocks any new page that ships without a main landmark.
- Skip to content. A skip link is the first thing you reach on every page, so you can jump past the header navigation straight to the main content instead of walking the whole menu on each page load.
- Charts carry their data as text. Every chart states what it shows and publishes its underlying series as a table a screen reader can read row by row. Where a chart uses colour to carry meaning, such as a gain against a loss, the table says which it is in words. Charts can also be traversed point by point with the arrow keys.
- Reduced motion. Animated elements, including the landing page sequences, respect the operating system
prefers-reduced-motionsetting and hold still when it is on. - Text and contrast. Body and interface text sits above a minimum size floor, and automated tests reject low-contrast and low-opacity text colors before they reach the app.
- Automated testing. The axe-core accessibility engine runs against key surfaces (sign-in, sign-up, onboarding, the rule builder, triggers, critiques, the investor profile, and the marketing shell) as part of our test suite, and reports violations live during development.
- Language and zoom. Pages declare their language for screen readers and reflow without horizontal scrolling at increased zoom levels.
What we know is not there yet.
These are open items, listed in the order we intend to fix them. This list is honest rather than complete: if you hit something that is not on it, please tell us and we will add it.
- Charts convey shape as well as numbers. Every chart now states what it shows and carries its full series as a table, so the figures are all reachable. What a table cannot hand you is the gestalt, the moment a curve flattens or two lines cross. If that matters for a decision you are making, write to us and we will describe the chart to you directly.
- Long series are sampled in the table. A chart covering hundreds of daily points lists a representative subset rather than every row, always including the first and last. The table says so when it happens, but the untabulated points are not currently reachable any other way.
- No dark or high-contrast theme. The interface is light only today. If you rely on a dark or high-contrast display, you will need your browser or operating system to supply it.
- Dense tables. Some portfolio and rule tables carry a lot of columns. They are readable, but they are not yet as easy to navigate cell by cell with a screen reader as they should be.
- No independent audit yet. Everything on this page comes from our own testing. We have not commissioned a third-party accessibility audit, and we will say so here when we do.
Screens we do not control.
Some steps run on systems operated by other companies, on their pages rather than ours. That includes connecting a brokerage account (SnapTrade and your broker) and paying for a subscription (our payment processor). We do not control the accessibility of those screens. If one of them blocks you, tell us anyway: we will raise it with the vendor and look for a way to get you through in the meantime.
How we assess this.
Self-evaluation, using a mix of automated and manual review. Automated checks run on every change to the codebase. Manual review covers keyboard-only navigation and screen-reader passes on the surfaces listed above. Automated tools catch roughly a third of real accessibility problems, which is why this page also relies on what users tell us.
Compatibility.
Cetagon is built to work with current versions of Chrome, Edge, Firefox, and Safari on desktop and mobile, together with the assistive technology built into those platforms. We do not test every browser and assistive-technology combination, and older browser versions may behave differently.
If something blocks you, tell us.
Email info@cetagon.com with Accessibility in the subject line. It helps if you can include:
- the page or feature you were on;
- what you were trying to do;
- the browser, operating system, and assistive technology you use, if you know them.
Cetagon is run by a very small team, so we cannot promise a fixed response time or a fixed date for a fix. What we can tell you is that a person reads every accessibility report that arrives, and replies. If we can suggest a way around the problem, or get you the information another way, we will.