2026 est le point de bascule
Pendant des années, l’accessibilité numérique a été traitée comme un point de contrôle projet : réaliser un audit WCAG avant la mise en ligne, corriger une partie des problèmes, puis passer à autre chose. En 2026, cette approche est trop fragile. L’accessibilité devient une discipline de conformité et de gouvernance, pas seulement une revue qualité.
ADA Title II now points public entities to WCAG 2.1 Level AA for web content and mobile apps, with compliance dates in 2026 and 2027 depending on entity size. In Europe, the European Accessibility Act has applied since 28 June 2025 to key products and services such as e-commerce, banking, e-books, communications, and parts of transport.
La leçon pratique pour l’enseignement supérieur, les organismes publics et les organisations parapubliques est claire : l’audit reste nécessaire, mais il ne constitue que la baseline. Il faut aussi du monitoring, des responsabilités claires et des preuves que l’accessibilité est pilotée dans le temps.
Abstracte headerafbeelding van een webinterface met toegankelijkheidsiconen, hoogcontrastgrafieken en een checklist op een rustige zakelijke achtergrond.
Alt-tekst: Abstract dashboard met toegankelijkheidsiconen, grafieken en een checklist.
Ce qui change juridiquement, sans brouillard juridique
Digital channels are now treated as gateways to education, public services, healthcare, transport, employment, and consumer services. If a login, payment step, enrolment form, or support journey is inaccessible, that is not merely a UX defect. It can block equal participation.
ADA Title II applies to U.S. state and local governments and their web and app services. The relevant technical standard is WCAG 2.1 Level AA. The EAA works differently, but the direction is similar: important digital services must be usable by people with disabilities, especially where users search, choose, order, sign, log in, pay, or communicate.
Regulators are also becoming more visible. In the Netherlands, ACM ConsuWijzer explains that webshops and communication services must be accessible and that problems can be reported. Broken journeys such as checkout, login, booking, and support are therefore especially risky.
Eenvoudige tijdlijn met drie stappen: nu audit en inventarisatie, 2026-2027 deadlines en implementatie, na 2027 striktere handhaving en bewijsvoering.
Alt-tekst: Tijdlijn van audit nu, deadlines in 2026-2027 en strengere handhaving daarna.
Pourquoi les audits ponctuels échouent en pratique
The pattern is familiar: a large audit produces a thick report, teams fix a selection of findings, and six months later the same type of defects return. A new modal traps focus. A new form has unclear errors. A new PDF has no structure. A new component ships without an accessible name.
This usually happens because accessibility is not embedded in the release process. A one-off audit gives you a snapshot; it does not prove that the organization remains in control after new content, new suppliers, new developers, and new design components enter the system.
If a complaint or investigation arrives, you need more than last year’s report. You need to show what you know, what you prioritized, what you fixed, what remains, and how regressions are detected.
Cartoonachtige zakelijke illustratie met links een stoffig auditrapport op een plank en rechts een live accessibility dashboard met meldingen.
Alt-tekst: Vergelijking tussen een oud auditrapport en een live toegankelijkheidsdashboard.
À quoi ressemble un audit moderne en 2026
A professional audit starts with scope: websites, apps, portals, documents, and the user journeys that matter most. In education, that might include enrolment, login, course information, exam accommodations, payments, timetables, and support.
The work combines automated scans with expert review. Automated tools find many technical patterns, but humans still need to test keyboard use, screen reader behaviour, magnification, mobile interaction, understandability, and journey logic.
The output should include a WCAG matrix, impact-based priorities, examples from real journeys, screenshots or selectors, guidance for reusable components, and where relevant a mapping to EN 301 549.
- Scope domains, apps, documents, and critical user journeys.
- Combine automated testing with manual expert review.
- Test keyboard, screen reader, zoom, and mobile interaction.
- Prioritize by user impact, not just issue count.
Close-up van een fictief WCAG-auditrapport met gekleurde prioriteitslabels, WCAG-matrix en actiepunten voor teams.
Alt-tekst: Fictief WCAG-auditrapport met prioriteiten, matrix en actiepunten.
De l’audit au monitoring continu
The audit is the baseline. After that, organizations need a layer that makes new issues visible. Think of security scanning or performance monitoring: you do not run one annual check and then ignore releases, dependencies, and incidents for the rest of the year.
An accessibility monitoring layer checks important pages and journeys periodically, detects regressions, tracks scores, and shows trends. It does not replace expert audits; it helps teams see problems earlier and act before users or regulators surface them.
Monitoring works best when it is connected to releases. Key templates are tested after deployment, product owners see recurring patterns, and compliance teams receive periodic evidence instead of isolated reports.
Dashboardachtige visual met toegankelijkheidsscore over tijd, regressie-alerts en een lijst met kritieke journeys.
Alt-tekst: Toegankelijkheidsdashboard met scoretrend, regressies en kritieke journeys.
Gouvernance et preuves
Accessibility often fails because ownership is unclear. IT expects UX to watch it. UX expects development to fix it. Development expects compliance to prioritize it. Compliance does not see the backlog. Meanwhile, content teams keep publishing.
A mature approach defines ownership across policy, design systems, code, content, procurement, and incident handling. Not everyone needs to be a WCAG specialist, but everyone should know when accessibility matters and where signals go.
Evidence does not need to start heavy. A policy, an issue backlog, prioritization decisions, release checks, and periodic reports already show that the organization is acting reasonably and proportionally.
- Assign one coordinator for governance, not every fix.
- Document exceptions and priorities with date and rationale.
- Track accessibility issues in the same backlog as product work.
- Report periodically to IT, UX, compliance, and leadership.
Illustratie van een teamworkshop met sticky notes en een groot scherm waarop een accessibility dashboard staat.
Alt-tekst: Teamworkshop rond een toegankelijkheidsdashboard en prioriteitenbord.
Un plan de 12 mois pour audit, monitoring et gouvernance
0-3 mois : baseline et parcours critiques
- Inventorier les sites, apps, portails et documents.
- Auditer les parcours utilisateur essentiels.
- Corriger d’abord login, formulaires, paiement et support.
- Créer un backlog central avec responsable et priorité.
3-6 mois : monitoring et composants
- Mettre en place des scans périodiques et des contrôles de release.
- Nettoyer la bibliothèque de composants.
- Rendre le reporting visible pour IT, UX et compliance.
- Formaliser les accords avec fournisseurs et équipes contenu.
6-12 mois : intégration et ré-audit
- Former designers, développeurs, rédacteurs et product owners.
- Ajouter l’accessibilité à la Definition of Done.
- Planifier des ré-audits ciblés.
- Rapporter les progrès aux instances de gouvernance.
Simpele roadmap-infographic met drie fases: 0-3 maanden, 3-6 maanden en 6-12 maanden, elk met een eigen icoon en checklist.
Alt-tekst: Roadmap met drie fases voor audit, monitoring en governance.
Passer de l’instantané au pilotage
Comparez votre approche actuelle avec ces étapes. Commencez par les parcours critiques, clarifiez les responsabilités et rendez les régressions visibles.