Accessibility
We are committed to WCAG 2.2 AA conformance. Our users include people in stressful situations, on slow networks, on cheap phones, with low vision, and with limited reading ability. Accessibility is a feature, not a remediation step.
- Conformance
- WCAG 2.2 AA
- Last audit
- 2026-05-04
Conformance target
WCAG 2.2 Level AA. We self-assess against the W3C published criteria and run automated audits with axe-core and Lighthouse on every release.
We also publish the methodology so independent auditors can reproduce our findings.
What is implemented
- Color contrast ≥ 4.5:1 for body text and ≥ 3:1 for large text and UI components, verified against the brand palette tokens (--brand, --accent, --danger).
- Keyboard navigation works on every interactive element. Focus rings are 3px brand-color outline with 2px offset.
- Screen reader: all images carry alt text or are aria-hidden when decorative. The audio player uses aria-pressed + aria-live regions to announce play / pause state.
- Large tap targets: minimum 44×44 px on every primary action.
- Body type 17px / line-height 1.55. Headings use the Fraunces serif at large weights. No color-only signals.
- Reduced motion: every animation (including the donate heartbeat) honors prefers-reduced-motion: reduce.
- High contrast: prefers-contrast: more flips backgrounds to pure white and text to pure black.
- Bilingual lang attributes: <html lang> reflects the active locale.
- Quick Exit on every emergency page is the first focusable element after page load and is reachable via the keyboard.
- Service-worker offline cache so emergency pages work on slow / no networks.
- All form fields carry visible labels (no placeholder-as-label patterns).
Known limitations
Our audio recordings are currently text-to-speech (Apple Samantha + Paulina) and not yet human-recorded. Pronunciation is generally accurate but not perfect for legal terminology in either language. We are recruiting human voice actors and will update this section when human-reviewed clips ship.
Captions for full-guide narration: not yet shipped. Per-step transcripts are exposed via a 'show transcript' disclosure under each clip.
Resource directory submit form has not yet been audited with a screen-reader user. We are scheduling that audit and will publish results.
How to report a barrier
Email [email protected]. Include the page URL, your assistive technology + browser, and a short description of the barrier. We acknowledge reports within 3 business days and aim to fix critical barriers within 14 days.
Standards we reference
- WCAG 2.2 (W3C, October 2023).
- Section 508 (Revised, January 2018).
- EN 301 549 V3.2.1 (European Telecommunications Standards Institute, March 2021).
- ATAG 2.0 for our admin authoring tool.
- Mobile Accessibility Guidelines (BBC, latest revision).