Accessibility
The commitment, what the build checks automatically, and what it does not.
Commitment #
This service aims to meet the Web Content Accessibility Guidelines version 2.2 at level AA. Accessibility is treated as a build requirement rather than an afterthought: the checks below fail the build rather than producing a report nobody reads.
What the build checks #
Colour contrast is computed for every foreground and background pair the design uses, in both themes, and a pair below its required ratio fails the build. Every interactive control is at least forty-four pixels tall. Every page declares a mobile viewport, supports both colour schemes, and carries no fixed width that would force sideways scrolling.
Motion is disabled for readers who ask for less of it, focus is always visible, and the wizard is walked from first question to finished assessment by a machine on every build, which catches a page that renders but cannot be used.
Known limitations #
No independent audit has been carried out, and no testing with assistive technology beyond keyboard navigation. The findings tables are wide, and on a small screen they scroll sideways within their own panel rather than reflowing.
Feedback #
If something here is unusable with your assistive technology, please say so via the contact page. Accessibility defects are treated as defects, not as requests.