(A11y) Accessibility statement
Accessible by default. Not by exception.
I was born deaf. Accessibility isn’t a checklist I learned, it’s how I experience the web every day. This site is built the way I ask teams to build theirs, and this page shows the proof.
Status
- Target
- WCAG 2.2, level AA
- and its French counterpart, RGAA 4.1
- Automated audit
- 0 violations
- 14 pages, desktop and mobile, axe-core 4.10 with WCAG 2.0 to 2.2 A/AA rules
- Last review
- 22 October 2026
- Re-run after every significant change
Automated tools catch only part of the barriers. They are a floor, not a finish line, so every page is also tested with the keyboard alone.
Seven decisions you won’t notice, until you need them.
What’s built in
- 01
Contrast
Every text meets the 4.5:1 AA ratio. The brand red was darkened for it, and a lighter variant is used on dark backgrounds.
- 02
Keyboard
A “skip to content” link, a visible focus ring on every interactive element, and scrollable areas you can reach with Tab.
- 03
Motion
With “reduce motion” turned on in your system, scroll animations, parallax and smooth scrolling are switched off.
- 04
Structure
Real landmarks and headings, a language set on every page, and English passages on French pages marked as such for screen readers.
- 05
Images
Descriptive alternative text on meaningful images. Purely decorative ones are hidden from assistive technologies.
- 06
Without JavaScript
Every page stays readable with scripts disabled: animations are an enhancement, never a requirement.
- 07
Light by design
A static site with no trackers, no cookies and responsive WebP images. Less data, faster on slow connections and older devices.
Known limitations
- Project screenshots show interfaces whose small text is not transcribed. The key information is always in the surrounding text.
- On large screens, selected projects scroll horizontally. The full list is also available as a simple list just below it.
- Links to Medium and Malt lead to sites I don’t control.
What I bring to product teams
In my work
-
Audits
Reviewing products against WCAG and RGAA, ranking issues by impact and turning them into stories developers can ship.
-
Accessible design systems
Components designed with their focus, error and disabled states, contrast-checked tokens and usage notes from day one.
-
Training
Masterclasses and workshops so designers, developers and product managers own accessibility instead of outsourcing it.
-
From the first wireframe
Inclusive design starts with research and flows, long before colours. Fixing it at the end always costs more.
“What makes him stand out is that he fights to bring accessibility into design, and few people take on this fight or know how to today.”
Read my articles on accessibility
Found a barrier?
If something on this site is hard or impossible to use for you, tell me. I’ll reply within a few days and fix what I can.
Report an issue