WCAG-EM 2.0: What a Better Audit Methodology Actually Changes

Most organizations conducting accessibility audits are doing them wrong — not because they lack technical knowledge, but because they lack a shared methodology for what an audit is supposed to accomplish in the first place.

The Accessibility Guidelines Working Group published WCAG Evaluation Methodology (WCAG-EM) 2.0 (opens in new window) on July 23, 2026, as a W3C Group Note. The document describes a structured, step-by-step process for evaluating how well digital products conform to WCAG 2 (opens in new window). That description sounds modest. The implications are not. WCAG-EM 2.0 arrives at a moment when accessibility evaluation has fractured into wildly inconsistent practices — where two auditors examining the same website can produce findings that barely overlap, where automated tools are mistaken for comprehensive audits, and where organizations confuse checking boxes with understanding access. A rigorous shared methodology doesn't just improve audit quality. It changes what organizations can credibly claim to know about their own accessibility.

Why Methodology Has Always Been the Missing Piece

WCAG 2.1 (opens in new window) and its successor criteria tell you what conformance requires. They do not tell you how to determine whether you've achieved it. That gap has produced a cottage industry of inconsistent evaluation practices. Some auditors test five pages. Others test fifty. Some define "representative sample" by page type; others by traffic volume; others by gut instinct. The result is that two organizations with identical accessibility profiles can have dramatically different audit findings — not because one is more accessible, but because their auditors used different evaluation frameworks.

This isn't a minor technical problem. It's a systemic one. As our research on the methodology paradox in accessibility testing documents, the field has become trapped between automated tools that promise scalability but miss critical barriers, and manual audits that catch nuanced failures but lack reproducibility. WCAG-EM 2.0 doesn't resolve that tension by choosing a side. It provides the procedural scaffolding that makes either approach more defensible.

The methodology structures evaluation into five core phases: defining the evaluation scope, exploring the target product, selecting a representative sample, evaluating that sample, and reporting findings. Each phase has explicit inputs and outputs. That structure matters more than it might appear.

The Sampling Problem Is the Central Problem

Of the five phases, representative sample selection is where most evaluation failures originate. An audit that tests the homepage, the contact form, and two interior pages has not evaluated a website — it has evaluated four pages. Yet this is common practice, particularly in self-assessments and lower-cost third-party reviews.

WCAG-EM 2.0's technology-agnostic approach to sampling guidance is its most practically significant contribution. By providing structured criteria for what constitutes a representative sample — across functionality, page types, user journeys, and content categories — the methodology gives auditors a defensible basis for scope decisions. It also gives organizations a basis for evaluating whether the audit they commissioned was actually comprehensive.

This connects directly to a pattern documented in our research on automated testing versus manual audits: automated tools detect at most 37% of accessibility barriers when measured against comprehensive manual audits. The gap isn't primarily about tool sophistication. It's about what gets evaluated at all. A methodology that enforces representative sampling closes that gap more effectively than any tool improvement.

What "Technology-Agnostic" Actually Means for Practitioners

WCAG-EM 2.0 explicitly provides technology-agnostic guidance. This is a deliberate design choice with real consequences. The methodology applies whether you're evaluating a React single-page application, a PDF-heavy government portal, a native mobile application, or a legacy content management system with inconsistent template behavior.

For practitioners, technology-agnostic guidance means the methodology doesn't become obsolete when frameworks change. The five-phase process for defining scope, sampling, evaluating, and reporting remains valid regardless of what the underlying technology stack looks like. The WCAG success criteria handle the technology-specific conformance questions. WCAG-EM 2.0 handles the evaluation process.

This matters particularly for organizations navigating multiple compliance frameworks simultaneously. As our research on the compliance framework paradox shows, organizations frequently experience paralysis when trying to satisfy WCAG 2.1, Section 508 (opens in new window), and EN 301 549 (opens in new window) simultaneously. A technology-agnostic evaluation methodology that maps cleanly onto WCAG 2 conformance levels provides a common evaluation language across those frameworks — which is exactly what organizations in multi-standard environments need.

The CORS View: Four Pillars, One Methodology

Analyzing WCAG-EM 2.0 through the CORS framework — Community, Operational, Risk, and Strategic — reveals why methodology reform matters beyond technical compliance.

Community: Disabled users are directly harmed when audits miss barriers. A self-assessment that tests three pages and declares conformance doesn't just mislead regulators — it misleads the people who depend on that product to participate in education, employment, government services, and daily life. Rigorous methodology is, at its core, a mechanism for ensuring that accessibility claims reflect actual access.

Operational: Most organizations lack internal capacity to conduct comprehensive evaluations. WCAG-EM 2.0's structured approach helps organizations understand what they're buying when they commission a third-party audit, and what they're actually measuring when they conduct a self-assessment. That clarity has direct operational value — it allows organizations to allocate evaluation resources more effectively and to recognize when a low-cost audit is producing low-quality findings.

Risk: The DOJ's web accessibility guidance under Title II (opens in new window) has raised the stakes for public entities claiming WCAG 2.1 AA conformance. An organization that claims conformance based on an inadequate evaluation methodology now faces a different kind of legal exposure — not just for the barriers that exist, but for the evaluation process that failed to find them. WCAG-EM 2.0 provides the procedural foundation for defensible conformance claims.

Strategic: Leadership buy-in for accessibility investment is easier when accessibility claims are credible and verifiable. A rigorous evaluation methodology transforms accessibility from a recurring cost center into a measurable, improvable system. Organizations that adopt WCAG-EM 2.0 as their evaluation standard can track progress over time, compare findings across audit cycles, and demonstrate genuine improvement — not just compliance theater.

What WCAG-EM 2.0 Does Not Do

The document is explicit about its scope. It does not define feature-specific evaluation instructions — those remain with the WCAG success criteria and supporting techniques documents. It does not add new WCAG 2 requirements. It does not replace or supersede WCAG 2 in any way.

This is worth stating plainly because methodology documents sometimes get misread as new compliance requirements. WCAG-EM 2.0 is a Group Note, not a W3C Recommendation. It carries significant technical authority but is not itself a normative standard. Organizations should treat it as the most rigorous available guidance on how to evaluate, while the underlying conformance obligations remain anchored in WCAG 2.1 AA (or WCAG 2.2 AA, depending on the applicable regulatory framework).

The distinction also matters for organizations worried about standards fragmentation. WCAG-EM 2.0 doesn't add another standard to navigate. It provides a methodology for evaluating conformance to the standards that already govern accessibility obligations.

Practical Steps for Practitioners

For accessibility professionals and compliance officers, WCAG-EM 2.0 warrants immediate integration into evaluation practices:

| WCAG-EM 2.0 Phase | What to Verify in Practice | Common Failure Mode | |---|---|---| | Define Scope | Written scope document specifying technologies, conformance level, and accessibility support baseline | Scope defined verbally or post-hoc | | Explore Target | Structured discovery of all page/component types, user journeys, and functional processes | Discovery limited to homepage and navigation | | Select Sample | Documented rationale for sample selection tied to scope criteria | Sample selected by convenience or traffic alone | | Evaluate Sample | Combination of automated and manual testing against WCAG 2 success criteria | Automated-only evaluation reported as comprehensive | | Report Findings | Findings mapped to success criteria with severity, scope, and remediation guidance | Findings listed without prioritization or context |

Organizations commissioning third-party audits should request that auditors document their methodology against WCAG-EM 2.0's five phases. If an auditor cannot explain their sampling rationale in writing, the audit's findings are not defensible — regardless of how technically sophisticated the testing was.

For organizations conducting self-assessments, the methodology provides a structured checklist for ensuring evaluations are comprehensive enough to generate actionable findings. The Northeast ADA Center (opens in new window) has consistently emphasized that self-assessment capacity is a critical component of long-term accessibility maturity — WCAG-EM 2.0 gives organizations the procedural framework to build that capacity systematically.

The publication of WCAG-EM 2.0 doesn't change what accessibility requires. It changes what organizations can credibly claim to know about whether they've achieved it. That's not a small thing.