WCAG-EM 2.0: The Methodology Gap No One Is Talking About

Marcus's recent analysis of WCAG-EM 2.0 captures the regulatory momentum well. The scope expansion to apps and digital products is real, the regulatory alignment with EN 301 549 is meaningful, and practitioners genuinely needed a methodology that matched the actual digital landscape. All of that is accurate.

But there's a harder conversation underneath the publication announcement — one that methodology documents rarely surface on their own. Expanding an audit framework's scope is not the same as improving the quality of audits conducted under it. And in a field where audit quality varies enormously (opens in new window), that distinction matters more than most compliance coverage acknowledges.

The Sampling Problem Doesn't Disappear by Renaming It

WCAG-EM 1.0's most persistent criticism was never its website focus. It was the sampling methodology — specifically, how evaluators determine what constitutes a "representative" sample of pages or states. That problem becomes geometrically more complex when you extend the methodology to native apps, progressive web apps, and hybrid interfaces.

A website has pages. A native mobile app has states, flows, gestures, platform-specific behaviors, and OS-version dependencies. The W3C's own mobile accessibility guidance (opens in new window) has acknowledged for years that mobile evaluation requires different thinking about what constitutes a testable unit. WCAG-EM 2.0 extends the methodology to cover apps — but the fundamental question of how you sample a complex, stateful application remains genuinely difficult.

Practitioners working in enterprise mobile accessibility know this firsthand. A banking app might have 200 distinct interaction flows. An e-commerce app's checkout process behaves differently based on payment method, saved addresses, promotional states, and error conditions. Selecting a "representative sample" from that surface area requires judgment calls that no methodology document can fully prescribe — and those judgment calls are where audit quality diverges most sharply between practitioners.

This isn't an argument against WCAG-EM 2.0. It's an argument for being clear-eyed about what a methodology document can and cannot do.

The Practitioner Competency Question

As explored previously in this analysis of the new standard, WCAG-EM 2.0 gives evaluators a structured process that matches the regulatory scope of frameworks like the European Accessibility Act. That's genuinely useful. But regulatory alignment and practitioner competency are separate variables.

The Pacific ADA Center (opens in new window) and other regional technical assistance centers have documented consistently that the gap between accessibility compliance documentation and actual user experience for disabled people often comes down to evaluator expertise, not methodology gaps. A structured framework applied by an undertrained evaluator produces structured but unreliable results.

This matters particularly for mobile. Screen reader behavior on iOS VoiceOver and Android TalkBack differs in ways that require platform-specific knowledge. Deque's research on mobile accessibility testing (opens in new window) has shown that automated tools catch a smaller percentage of mobile accessibility issues than web issues — meaning mobile audits are more dependent on skilled manual evaluation than website audits ever were. Extending WCAG-EM's scope to apps without a corresponding investment in practitioner training and certification creates a methodology that looks comprehensive on paper but produces variable results in practice.

The Section 508 Trusted Tester program (opens in new window) represents one model for addressing this — a structured competency framework that goes beyond methodology documentation to establish what evaluators actually need to know. The accessibility field needs equivalent rigor for mobile evaluation, and WCAG-EM 2.0's publication is an opportunity to push for that, not just to celebrate the methodology expansion.

What a Balanced Assessment Actually Looks Like

Good accessibility journalism holds two things simultaneously: genuine progress deserves recognition, and genuine problems deserve honest analysis. WCAG-EM 2.0 is real progress. The field needed a methodology that covered apps. The regulatory alignment with EN 301 549 and the DOJ's Title II web accessibility guidance (opens in new window) removes a legitimate source of evaluator confusion.

But coverage that emphasizes methodology expansion without examining implementation quality encourages a compliance-theater dynamic — organizations commissioning audits under a new standard without asking harder questions about what those audits actually measure. Disabled people who rely on mobile interfaces as primary access points are the ones who bear the cost of that gap.

The organizations that will get the most value from WCAG-EM 2.0 are those that treat it as a floor, not a ceiling. That means:

Investing in evaluator competency before expanding audit scope. A methodology document tells evaluators what to do. It doesn't ensure they have the platform-specific knowledge to do it well on iOS, Android, and emerging form factors simultaneously.

Building in user testing with disabled people as a validation layer. The Web Accessibility Initiative's own guidance (opens in new window) is clear that conformance evaluation and usability testing with disabled users are complementary, not interchangeable. WCAG-EM 2.0 audits can confirm technical conformance while missing real-world barriers that only emerge in authentic use.

Treating the sampling methodology as a starting point for organizational judgment, not a complete answer. The hardest part of auditing complex applications isn't following a structured process — it's making defensible decisions about what to sample and why. Organizations should document those decisions explicitly, not treat them as implied by the methodology.

The Longer Arc

Building on this framework for understanding what WCAG-EM 2.0 actually changes, the publication represents the W3C catching up to a digital landscape that moved faster than its documentation. That's worth acknowledging. The European Accessibility Act's enforcement timeline and the DOJ's increasing attention to digital accessibility under the Americans with Disabilities Act (opens in new window) mean that having a methodology aligned with regulatory scope is practically important.

But methodology alignment and outcome improvement are different things. The accessibility field has enough compliance theater already — audits that produce conformance statements that don't reflect the experience of disabled users, reports that satisfy procurement requirements without improving products. WCAG-EM 2.0 can be a tool against that pattern, or it can become another layer of it, depending entirely on how practitioners and organizations choose to implement it.

The publication is good news. The harder work starts now.