Accessibility

Pythia Research aims to meet WCAG 2.2 Level AA across the application and the public site. Dense financial interfaces are hard to make accessible; this page says what we do about it and how to reach us when something does not work for you.

What we build to

• One stable page heading per screen, landmarks for navigation and main content, and a skip link on every page.
• Every icon-only control carries an accessible name; async actions announce their state; tables declare their headers.
• Text is at least 12 px, interactive targets at least 24 px (44 px on touch), and colour is never the only signal — links are underlined, verdicts carry words.
• Motion respects the reduced-motion preference; nothing flashes or loops.
• Keyboard: the full application is reachable without a mouse; press ? anywhere for the shortcut list.

How it is checked

• Every interface change runs an automated accessibility audit (axe-core) at mobile and desktop widths before it can merge; zero violations is the bar.
• Screen-reader semantics for numbers: missing values read as “not applicable” or “pending” with a reason, never a bare dash.
• Known issues are tracked in an internal audit registry and fixed in the surface they live on.

Known limitations

• Some charts are visual first; each has a table or a text summary beside it, but the chart itself is not fully navigable by keyboard yet.
• Third-party embeds (payment forms, brokerage connection) follow their provider’s accessibility, not ours.

Tell us

If any part of Pythia is hard to use with assistive technology, write to support@pythiaresearch.org with the page and what happened. We reply within two business days and treat accessibility bugs as defects, not requests.