Accessibility

What we aim for

We build TradePolaris to meet WCAG 2.2 level AA. That is the target for the public pages, for signing up and signing in, and for the product itself. We have not reached it everywhere yet, and the gaps we know about are listed below.

What we check on every change

Every pull request runs an automated accessibility pass with axe-core against a real production build of the site. It covers the home page, pricing, the FAQ, this page, a product page, the terms and privacy pages, the login and sign-up forms, the dashboard, and a security workspace. A finding rated serious or critical fails the build, so the change does not ship. Findings rated moderate or minor are recorded with their counts and worked through in order.

An automated pass catches part of the standard, not all of it. Tools like axe can check contrast, names, roles and structure. They cannot tell you whether a page makes sense when you hear it read aloud, or whether a keyboard path is a reasonable one. We have not completed a full manual audit, and no third party has audited the site. When that changes, this page will say so and give the date.

What works today

Pages declare their language. On the pages the pass covers, text meets the AA contrast ratio, images that carry meaning have a text alternative, and the sign-up and sign-in fields have labels bound to them. Animation on the marketing pages stops when your system asks for reduced motion.

Known gaps

These are the findings the automated pass reports today. None of them is rated serious or critical, and each one is a real thing to fix.

• Marketing pages do not yet wrap their content in a main landmark, so a screen reader cannot jump straight to the content of the page. This statement page does.
• Some sections on the home page, the FAQ and the legal pages sit outside a landmark region, which makes the same kind of navigation harder.
• Heading levels skip a step in a few places on the home page, the FAQ and the legal pages.
• Charts are drawn on a canvas and carry no text alternative yet.
• Some controls turn the browser focus outline off and draw a ring of their own. We are going through them one at a time, because a control with no visible focus state cannot be used from a keyboard.

No accessibility overlay

We do not use an accessibility overlay or a third-party widget that claims to fix a site from the outside. Overlays sit on top of a page and often make screen reader output worse. The fixes go into the pages themselves.

Tell us about a problem

Email support@tradepolaris.com and include the address of the page, what you were trying to do, and the browser and assistive technology you were using. If something stops you from finishing a task, say so. We will tell you what we plan to fix and when.

If you would rather write to us another way, the contact page lists our other addresses.

How this page is kept current

We review this statement whenever the automated pass changes what it covers or what it reports, and we date the review at the top of the page. The list of known gaps comes from the last run of that pass, not from memory.