Lausanne, Switzerland

Gwenaël
Magnenat

Scanners catch ~30% of accessibility errors.

I build for the rest.

What I actually think

A clear accessibility spec is the biggest development accelerator I know.

Not tests, not reviews, not better tooling. The spec. When developers know what's expected before they write a line of code, accessibility isn't a late phase — it's the default output.

Automated tools give false confidence. axe, Lighthouse, WAVE — useful, but they see about 30%.

The rest requires judgment: navigating with a keyboard, using a real screen reader, understanding why a pattern fails before it ships. Passing a scan is the floor, not the ceiling.

AI reproduces the inaccessibility of the web it learned from. That's not a bug — it's the dataset.

Models trained on a web that excludes most disabled users will output more of the same — unless someone specifies otherwise. Spec quality matters even more now.

Writing

AccessibilityLinkedIn · Jul 2025

Les outils automatisés ne voient pas 70% des problèmes d'accessibilité

axe, Lighthouse, WAVE sont utiles. Mais ils couvrent environ 30% des critères WCAG. Le reste exige du jugement, du contexte, et d'avoir utilisé un lecteur d'écran pour de vrai.

Read on LinkedIn →
AccessibilityLinkedIn · Jun 2025

L'accessibilité doit bloquer la mise en production

Pas comme suggestion. Pas comme «on regardera après le lancement». Bloquer. Voici comment structurer ça en équipe sans que ça devienne un frein à tout.

Read on LinkedIn →
AccessibilityLinkedIn · May 2025

L'IA reproduit l'inaccessibilité du web par défaut

Les modèles ont appris d'un web qui exclut la plupart des personnes handicapées. Sans spécification explicite, ils reproduisent ces patterns. Ce n'est pas un bug, c'est le dataset.

Read on LinkedIn →
AccessibilityBlog · 2024

25% of the World Struggles to Access the Web

Discover how 25% of the world's population faces web accessibility barriers and learn practical steps to enhance your website's usability. Improve engagement, boost SEO, and ensure legal compliance with our comprehensive guide on the accessibility steps you need to focus on.

Read post →
Creative codingBlog · 2024

Create a Spiral Drawing with JavaScript and canvasSketch

Learn how to code a spiral drawing using the canvasSketch library in JavaScript. This tutorial provides a step-by-step guide with explanations.

Read post →
Creative codingBlog · 2024

Understanding context.save() and context.restore()

Grasp the power of context.save() and context.restore() in canvasSketch. These methods ensure modular drawing, maintain code clarity, and simplify complex visuals.

Read post →

3× a week on LinkedIn

Mostly French. Real accessibility problems in real products.

Follow on LinkedIn ↗

About

I've been building web interfaces for over a decade. Most of the last several years have been accessibility work.

Writing specs developers can actually use. Auditing products with real assistive technology — not just scanners. Pushing back when something almost passes but isn't right.

Based in Lausanne, Switzerland. I work in French and English. I post on LinkedIn three times a week — mostly in French, mostly about real problems in real products.

I'm also interested in what happens when code is the medium. Spirals, grids, emergent patterns. That side lives on the blog.

Full bio →CV →

Specialities

  • Accessibility audits & specification
  • Full-stack development (TypeScript, Node, Astro)
  • Component architecture & design systems
  • Creative coding & generative art

Availability

Available for accessibility consulting and development work in Switzerland