The European Accessibility Act is here: a developer's field guide
The EAA has been enforceable since June 2025. What it actually requires, who it applies to, how EN 301 549 maps to WCAG 2.1 AA — and what to do first.
Practical, developer-first writing on WCAG, the European Accessibility Act, ARIA, and shipping accessible code — no compliance theater.
The EAA has been enforceable since June 2025. What it actually requires, who it applies to, how EN 301 549 maps to WCAG 2.1 AA — and what to do first.
If you sell software to governments or large enterprises, someone will ask for a VPAT. Here's what's inside one, how it relates to WCAG, and how to produce one honestly.
Focus appearance, dragging movements, target size, accessible authentication — what each new criterion means in real component code, with passing and failing examples.
An accessibility bug caught at code-time costs seconds. The same bug caught in a yearly audit costs a ticket, a sprint, and a regression risk. The economics of moving the check left.
Redundant roles, aria-labels that silence content, fake buttons, decorative noise, and live-region spam. The first rule of ARIA is still: no ARIA beats bad ARIA.
Where the famous ratio comes from, when 3:1 is enough, why AAA asks for 7:1, and how to keep a brand palette intact while passing every check.