Morgan Dutemple
All expertise areas

Web accessibility: designed in from the start

Most of the accessibility audits I take over share the same flaw: accessibility was treated as a list of fixes, never as a design constraint. I build it into scoping, I check it by hand against the 106 criteria of the French RGAA 4.1.2, and I train teams so the same errors do not come back.

Why accessibility can no longer wait

In France, the RGAA applies to public bodies, private bodies with a public service mission and companies whose average turnover in France exceeds 250 million euros. Since 28 June 2025, the European Accessibility Act also applies to a range of products and services for consumers, including e-commerce, banking services and transport.

Most non-conformities are quick to fix once found: contrast, heading hierarchy, keyboard focus. Yet they keep coming back, because they are introduced early, in the design system or a global stylesheet, and never checked before going live. Handling them at design stage costs far less than reworking them after launch.

Sources: DINUM, scope of accessibility obligations (in French) ; Directive (EU) 2019/882 on the accessibility requirements for products and services

My method

The order draws on the French government's (DINUM) evaluation method and on the Designers Éthiques approach: identify the obligation, measure, prioritise, then fix where the errors are born.

  1. Identify the obligation

    Who is covered, which services, which standard: RGAA 4.1.2 today, RGAA 5 announced for late 2026.

  2. Audit a representative sample

    Mandatory pages, key journeys and randomly drawn pages; the 106 criteria of RGAA 4.1.2 tested by hand.

  3. Prioritise by impact and publish a statement

    Blocking issues first, a roadmap that doubles as an action plan, an accessibility statement ready to publish.

  4. Fix at the source and keep it up

    Fixes in the design system and templates, teams trained on the errors found, a check at every release.

Sources: DINUM, conformity evaluation (in French) ; DINUM, accessibility statement (in French) ; DesignGouv, RGAA 5 (March 2026, in French) ; Designers Éthiques, accessibility approach training (in French)

In a web agency: accessibility checked from the prototype

On a web project run in an agency, the working prototypes produced with AI also served UX and accessibility. A prototype that runs in a browser can be tested with a keyboard, a screen reader and a contrast check before a single page of the final site is built.

That is when a fix costs least: a focus order, a heading hierarchy or a button label is reworked in the prototype, then carried as is into the design system. Automated tools catch some of the errors; manual review does the rest.

Frequently asked questions

Is accessibility legally required?

In France, RGAA compliance is mandatory for public bodies, private bodies with a public service mission and companies with an average French turnover above 250 million euros. Since 28 June 2025, the European Accessibility Act (Directive (EU) 2019/882) sets accessibility requirements for a range of consumer products and services across the EU. For other sites, it is a strong practice and often required in public tenders.

What is the difference between WCAG and RGAA?

WCAG (Web Content Accessibility Guidelines) is the international standard from the W3C. RGAA is its French counterpart, published by DINUM, which specifies the tests and the evaluation method. In practice, RGAA compliance implies WCAG AA compliance.

What does RGAA 5 change?

Its publication is announced for late 2026. It brings in WCAG 2.2, adds criteria for mobile apps and office documents, and names Arcom as the supervisory authority. Its criteria refine or complete those of RGAA 4.1.2 without contradicting them, so ongoing work has no reason to wait.