Expertise
Web Accessibility: designed in from the start
The majority of accessibility audits that arrive too late share the same original flaw: accessibility was treated as a list of corrections, never as a design constraint. I integrate accessibility analysis and compliance upstream of projects, not as a late fix.
My approach
- Full accessibility audit: contrast, semantic structure, keyboard navigation, screen reader compatibility
- Accessibility by design: integrated into the design system, not revised screen by screen
- Prioritisation of corrections by real impact on users, not just legal compliance
- Team awareness to prevent the same non-conformities from recurring
Tool for web accessibility
Contrast Checker
In nine accessibility audits out of ten, contrast issues on disabled states or placeholders go unnoticed. Designers test main text, not every interface state. This tool checks everything, to WCAG standards.
Heading Hierarchy Checker
Heading hierarchy (H1-H6) is one of the most frequent and fastest-to-fix accessibility non-conformities. It is also one of the least checked, because you need to read raw HTML. This tool does it in seconds.
Hidden Focus Detector
Invisible keyboard focus is often introduced by a single global CSS selector (outline: none) and makes the entire interface inaccessible by keyboard. It is rarely detected without active testing. This tool analyses your CSS and identifies the offending rules.
Accessibility Scope Diagnostic
Before checking a specific criterion, you first need to know which ones apply to you. This questionnaire first situates your legal obligation (public sector, private thresholds, European Accessibility Act), then identifies which points to check based on your site's actual content, with the option to scan up to 4 key pages to pre-fill the answers.
Site health scan: eco-design, accessibility, security
Loads a page in a real browser to measure its actual weight, estimated CO2 footprint, WCAG accessibility issues and missing security headers.
Frequently asked questions
Is WCAG compliance legally required?
In the EU, the European Accessibility Act requires digital products and services of private organisations to meet WCAG 2.1 AA by June 2025. In France, RGAA compliance is mandatory for public bodies and companies with turnover above 250 million euros. For others, it is a strong practice and is often required in public tenders.
What is the difference between WCAG and RGAA?
WCAG (Web Content Accessibility Guidelines) is the international standard produced by the W3C. RGAA is the French transposition, produced by DINUM, which adds specific tests and clarifies evaluation methods. In practice, RGAA compliance implies WCAG AA compliance.
How long does an accessibility audit take?
For a standard-sized site (5 to 10 distinct templates), allow 3 to 5 working days for a complete manual audit. The report includes the list of non-conformities by criterion, their severity level, and prioritised correction recommendations.