
How I automated 62% of Europe's RGAA accessibility criteria
In Europe, web accessibility became mandatory in June 2025 under the European Accessibility Act (EAA) . But the EU doesn't define how to test — each country has its own standard. The French standard is RGAA 4.1 : 106 criteria, published by the government, with precise test procedures. Every tool out there (Axe, WAVE, Lighthouse) speaks WCAG. None of them map to RGAA natively. So I built one. The problem: RGAA ≠ WCAG RGAA 4.1 is based on WCAG 2.1 AA, but it goes further: 106 criteria instead of 78, with specific test methodology 13 thematic areas (images, colors, links, forms, navigation...) Precise test procedures — not just "what to achieve" but "how to verify" When a public agency or a company under the EAA needs an audit, they need RGAA — not WCAG. And there was no SaaS tool for that. What's automatable? Out of 106 criteria, 66 (62%) can be tested automatically . The best coverage by theme: Mandatory elements — 9/10 automatable (90%) — missing lang , invalid HTML, page titles Naviga
Continue reading on Dev.to
Opens in a new tab



