Légal12 min de lecture

Les fondations de l'architecture WCAG 2.2

Portrait of Ewan Réveillé--Adam

Ewan Réveillé--Adam

Fondateur d'AIA Handicap • 9 avril 2026

modern architectural abstraction of steel and glass beams crossing in a clear blue sky, representing digital structure

Digital accessibility is often treated as an afterthought—a decorative layer applied to a building already constructed. In reality, truly accessible experiences require us to treat the Web Content Accessibility Guidelines (WCAG) as the foundational blueprints of our digital environment.

Understanding WCAG 2.2 for Modern Web Design

The release of WCAG 2.2 marks a significant evolution in how we perceive user interaction. While previous versions focused heavily on screen reader compatibility and visual contrast, 2.2 delves deeper into cognitive loads, pointer interactions, and the mechanics of modern authentication.

"Accessibility is not a feature; it is the infrastructure upon which every other feature is built."
lightbulb

Key Takeaway

The shift from 2.1 to 2.2 emphasizes the human experience of error—ensuring that users with cognitive or motor impairments aren't punished for the inherent complexity of web interfaces.

New Success Criteria in 2.2

The nine new success criteria introduced in WCAG 2.2 provide actionable targets for designers and engineers. These additions specifically address low-vision users, people with cognitive and learning disabilities, and those with motor impairments using mobile devices.

  • 01
    Focus Not Obscured (Minimum/Enhanced)

    Ensuring that the item receiving keyboard focus is not hidden by other page content like sticky headers or pop-ups.

  • 02
    Target Size (Minimum)

    Interactive targets must meet a minimum size of 24x24 CSS pixels, unless there is sufficient spacing between them.

  • 03
    Redundant Entry

    Users shouldn't have to re-enter information they've already provided in the same session, reducing cognitive fatigue.

Architectural Impact

Implementing these changes isn't just about passing an audit; it's about changing the architectural intent. For instance, the 'Accessible Authentication' criterion (3.3.8) prevents the use of "cognitive function tests" like memorizing passwords or solving puzzles during login.

terminal

Technical Tip

Use autocomplete attributes effectively. This allows browsers to fill in stored info, directly satisfying the Redundant Entry requirement without custom engineering.

The Path Forward

As we move toward a more inclusive digital future, the role of the designer becomes more akin to that of a civic planner. We aren't just making pretty pages; we are building public squares that must be traversable by everyone, regardless of their hardware or biological capabilities.

Est-ce que cet article vous a été utile ?