Legal · Accessibility
Accessibility
Draft · statement of commitment
A feedback mechanism that only works for people who can read a small font on a good phone is not a feedback mechanism. It is a filter. Accessibility here is not compliance theatre — it decides who is able to be heard.
01Our commitment
- Public reporting forms are built to WCAG 2.1 AA: semantic markup, labelled inputs, keyboard operability, visible focus, contrast ratios at or above 4.5:1 for body text, and error messages tied to the field that caused them.
- Forms are designed for low-bandwidth connections and older devices; the target is under 100 KB on first load.
- Languages are configurable per form, including right-to-left layouts.
- Nothing in the public form requires an account, a cookie wall, or JavaScript to reach the submit button.
02Known limitations
We publish these rather than wait for someone to find them:
- The staff console has not yet completed an external accessibility audit. It is keyboard-operable and tested with screen readers internally, but we do not claim conformance for every admin screen.
- Some data tables are wide by nature; below 900px they become horizontally scrollable rather than reflowed.
- Audio transcription of voice submissions is not yet available; voice reports are stored as recordings for human review.
03This website
- Text meets AA contrast in both light and dark display settings.
- All interactive elements are reachable by keyboard, with visible focus states, and targets are at least 44px on touch screens.
- Motion is limited to short reveals and is disabled entirely when your system requests reduced motion. Content never depends on JavaScript to appear.
- No autoplaying media, no time limits, no CAPTCHA on this site.
04Reporting a barrier
If something here or in the product is hard to use with your setup, tell us: [ACCESSIBILITY EMAIL]. Say what you were trying to do and what happened. We acknowledge within two business days, fix what we can in the next release, and will tell you plainly if we cannot.