Accessibility (A11y)

Définition

Digital accessibility, often abbreviated as A11y (with the number 11 representing the letters between “a” and “y”), refers to the practice of designing digital products that can be used by everyone, regardless of their physical or cognitive abilities. This includes people with disabilities (visual, motor, auditory, cognitive), as well as users facing situational limitations (such as screen glare in bright sunlight or noisy environments). As of 2025, accessibility is governed by the WCAG (Web Content Accessibility Guidelines) and is based on four fundamental principles: content must be Perceivable, Operable, Understandable, and Robust (the POUR framework).

No items found.

Exemple

Imagine a visually impaired user browsing your e-commerce website using a screen reader. If they reach a product page where the image lacks alternative text (alt text), the software may simply read “Image-452.jpg,” making the experience frustrating and the purchase uncertain. By adding a descriptive text such as “Red running shoes with white laces,” you allow the user to understand the offer and complete their purchase independently. This is not only helpful for visually impaired users. It is also what enables Google (which is effectively “blind”) to better understand and index your images.

Outils recommandés

  • Stark: A suite of tools integrated into Figma to test color contrast, simulate color blindness, and define keyboard navigation order directly during the design phase.
  • axe DevTools: An essential browser extension for developers to detect and fix accessibility-related code issues in real time.
  • WAVE (Web Accessibility Evaluation Tool): A visual tool that allows you to quickly identify semantic structure errors and insufficient color contrast on a web page.
  • Fable (Make it Fable): A specialized platform that enables testing prototypes and products with real users with disabilities, providing authentic, unbiased feedback grounded in lived experience.
  • And no 🙂 Google PageSpeed Insights is not listed here.This is intentional. While it is useful for performance and some basic technical signals, it remains too limited to assess real accessibility, which requires human, context-aware, and usage-oriented analysis. Accessibility cannot be reduced to an automated score.
  • Ouvrages recommandés

  • Accessibility for Everyone by Laura Kalbag: An excellent entry point that explains in a simple and human way how to make the web more inclusive.
  • Mismatch: How Inclusion Shapes Design by Kat Holmes and John Maeda: A visionary book showing that exclusion is the result of mismatched design, and how inclusive design drives innovation for everyone.
  • W3C (Web Accessibility Initiative): The official platform for WCAG standards. It is the ultimate technical reference for verifying both legal compliance and technical accessibility of digital interfaces. (Guidelines link in the references)
  • Références & sources

    No items found.