Accessibility
This site is meant to work for everyone who reaches it, with a keyboard, a screen reader, a small screen or a preference for less motion. Here is what it meets, how we checked, and how to tell us when it falls short.
What it meets
We hold the site to WCAG 2.2 at level AA. Text contrast is at or above 4.5 to 1 in both themes, every control can be reached and operated with a keyboard, focus is always visible, and nothing depends on colour alone: severity is written as a word as well as a colour.
What moves, and what does not
- The three-dimensional test on the home page is decorative. The same information is in the text beside it, and phones get still images with descriptions instead.
- With a system preference for reduced motion, the scroll-linked animation, the route transitions and the dog in the footer are all switched off and every section shows its final state.
- Nothing flashes, autoplays with sound, or moves without scrolling.
- On desktop the chips at the break are placed by scroll position, so scrolling back flies them home. Under reduced motion the specimen is shown repaired and still.
How we checked
- Lighthouse accessibility audit on every build, held at 100 by the continuous integration budget.
- Keyboard walkthroughs in Chromium and Firefox: the skip link, the menu, the theme control, the service rows, the report tabs and the contact form, including its error messages.
- Automated end-to-end tests for the skip link, keyboard operation of the service rows, form validation and the reduced-motion state.
- A screen reader pass with NVDA and VoiceOver is scheduled before launch and is not yet done. This line will change when it is.
Known limits
- The sample report PDF is generated from the page and carries its headings and reading order, but has not yet been checked with a PDF accessibility tool.
- The brand page shows the mark at small sizes to document minimum size; those tiny instances are decorative and marked as such.
Tell us
If something here does not work for you, write to hello@breakfirst.dev and say what you were trying to do and what happened. We reply within one working day and fix what we can on this site directly.