Accessibility
WCAG 2.1, EAA from June 28 2025, accessibility statement — for sites + apps.
- WCAG 2.1 AA checklistThe four principles (perceivable, operable, understandable, robust) translated into concrete checks for your site or app. EAA-compliant from 28 June 2025.Live
- EAA from 28 June 2025EAA requires commercial websites + apps selling products/services to EU consumers to comply with WCAG 2.1 AA. In force since 28 June 2025.Live
- Accessibility statementLegally required statement with: WCAG conformity, known issues, contact options + enforcement route. Footer link + dedicated page.Live
- Screen reader basicsHow NVDA + VoiceOver interpret your site. ARIA labels, heading hierarchy, alt text, focus order. Practical test instructions.Live
- Colour contrast WCAGWCAG 1.4.3 AA: text min. 4.5:1, large text 3:1, UI elements 3:1. Tools, exceptions, and why this helps sighted users too.Live
- Keyboard navigationTab order, focus visibility, skip links, modal traps. Essential for motor impairments + screen reader users + power users.Live
- Video accessibilitySubtitles for deaf/hard-of-hearing + audio description for blind users. When required (EAA + AVMSD), how to produce cheaply.Live
- Accessible formsLabels, error messages, help text, autocomplete, required fields. #1 place where even sighted users abandon bad design.Live
- PDF accessibilityTagged PDF, reading order, alt text, form fields. Mandatory for government + post-EAA for many commercial PDFs (invoices, contracts, product documentation).Live
- App accessibilityVoiceOver (iOS) + TalkBack (Android), touch targets min. 44x44pt, dynamic type, colour-blind modes. EAA covers apps too since 28 June 2025.Live