Our target
Brainback aims to meet WCAG 2.1 Level AA across all core surfaces (marketing, auth, and the study app). We audit against this target on every meaningful release. This is a target, not a certification — we are honest about the gaps below.
What works today
- Keyboard navigation is supported on every interactive element in the study surface, with visible focus rings.
- All form inputs have programmatic labels tied via
for/htmlFor. - Colour contrast on primary text meets or exceeds 4.5:1 in both day and night themes.
- The interface honours
prefers-reduced-motionfor large animations and page transitions. - Structural landmarks (
main,nav,header,footer) are used consistently for screen-reader navigation. - Icon-only buttons carry
aria-labeltext. - Alerts and inline errors are announced to assistive tech via
role="alert"oraria-live.
Known gaps
- Some marketing pages contain decorative graphics that have
alt=""but should have descriptive alt text. - Our command palette (Cmd+K) is fully keyboard operable but the trigger area needs a more discoverable label for screen-reader users.
- Complex product illustrations do not yet include full long descriptions.
- Some marketing typography uses colour combinations that meet AA for text but fall short of AAA at smaller sizes.
We track these in our internal accessibility backlog and fix them with every release. If any of them blocks you, tell us — we will prioritise it.
How to report an issue
Email accessibility@brainback.chat with a short description and, if possible, the URL and the assistive tech you were using. A real human will reply within 3 business days.
If you prefer a form, write to us here and we’ll open a ticket on your behalf.
Assistive-tech we test with
- VoiceOver on macOS + iOS (Safari)
- NVDA on Windows (Firefox)
- TalkBack on Android (Chrome)
- Keyboard-only navigation in Chrome, Firefox, and Safari
- Windows High Contrast Mode
Third parties
Some parts of Brainback rely on third-party surfaces we don’t fully control (Stripe checkout, magic-link email clients, our auth vendor’s hosted pages). We choose vendors that publish their own accessibility statements and we escalate any user-reported issue directly to them.
Formal complaints
If you feel your accessibility need has not been met, or you disagree with how we’ve responded, you can also escalate to your national equivalent (e.g. in the US: the Department of Justice ADA information line; in the EU: national equality body; in Canada: Accessibility Commissioner).