Components / Accessibility
<Accessibility />
From 36% to 54% RGAA compliance on one of France's largest e-commerce platforms.
15% of the world lives with a disability.
Can everyone read this?
8.58:1AA ✓ passAAA ✓ passLarge text ✓
Romain joined Carrefour inside the Accessibility squad and drove the e-commerce platform's RGAA score from 36% to 54%, aligning with French compliance requirements: audits, remediation, developer training, and tooling.
He also wrote webforallguide.com, a free practical guide to web accessibility (contrast, semantic HTML, ARIA, keyboard navigation, forms, screen readers), built on the conviction that designing for people with disabilities makes the web better for everyone.
Props
| Prop | Type | Value | Description |
|---|---|---|---|
standard | 'WCAG' | 'RGAA' | both | Audits and remediation against WCAG 2.x and the French RGAA referential. |
score | delta | 36% → 54% | Measured RGAA compliance improvement at carrefour.fr. |
method | string[] | ['audit','fix','train','tool'] | Fix the code, then fix the process that produced the code. |
guide | url | webforallguide.com | Self-published, practical, free. |
Do
- Start with semantic HTML. Most ARIA is a patch for a wrong element.
- Test with a keyboard and a screen reader, not just an automated scanner.
- Sell accessibility on the curb-cut effect: it improves the experience for everyone.
Don’t
- Sprinkle aria-label everywhere and call it accessible.
- Treat the audit score as the goal. The goal is people being able to use your product.
- Postpone accessibility to a compliance sprint.
This website targets WCAG 2.2 AA: semantic landmarks, skip link, full keyboard navigation, visible focus, reduced-motion support, AA contrast on every token combination.
Found an issue? Email romain.malnoult@gmail.com. Accessibility bugs get priority support.