On July 23, 2026, the World Wide Web Consortium (W3C) published WCAG Evaluation Methodology (WCAG-EM) 2.0 as a W3C Group Note. For businesses buying accessibility audits, agencies delivering them, and product teams responsible for digital accessibility, the update matters because it provides a clearer, broader methodology for evaluating how well a digital product conforms to WCAG.
WCAG-EM 2.0 is not a new version of WCAG and it does not add new success criteria. It is a methodology for conducting an evaluation. That distinction is important: WCAG tells you the accessibility requirements; WCAG-EM helps structure how an evaluator scopes, samples, tests, and reports an assessment. W3C explicitly states that WCAG-EM 2.0 does not replace or supersede WCAG requirements.
What is WCAG-EM 2.0?
WCAG-EM 2.0 is W3C’s updated methodology for evaluating digital products against WCAG 2. According to the W3C announcement, the methodology uses a step-by-step process that can be applied in different evaluation contexts, including self-assessment and third-party accessibility evaluations.
The biggest conceptual change is scope. WCAG-EM 1.0 was written specifically around websites and web pages. WCAG-EM 2.0 is designed to work with websites, web applications, mobile apps, and other digital products. That makes the methodology more relevant to organizations whose customer experience extends beyond a traditional marketing website.
The five core stages of a WCAG-EM 2.0 evaluation
WCAG-EM 2.0 emphasizes defining scope, representative sampling, evaluation, and reporting.W3C organizes the methodology around five major activities. A serious accessibility audit should be able to explain how each of these activities was handled.
- Define the evaluation scope. The evaluator identifies what product, version, environment, pages, screens, features, user journeys, and technologies are included. A vague statement such as “we tested the website” is not enough for a complex product.
- Explore the target product. Before choosing a sample, the evaluator needs to understand the product’s structure, major functionality, templates, components, workflows, technologies, and accessibility-relevant features.
- Select a representative sample set. For large products, testing every URL or screen may be impractical. The sample should represent the product rather than simply selecting a few convenient pages.
- Evaluate the selected sample. The evaluator tests the selected content and functionality against the applicable WCAG requirements using appropriate methods, including manual review where human judgment is necessary.
- Report the findings. The evaluation should document scope, methodology, sample, findings, limitations, and conclusions in a form that stakeholders can understand and developers can act on.
Why representative sampling matters more than page count
Many businesses still buy accessibility audits based primarily on a number of pages: five pages, ten pages, twenty pages. Page count can be useful for pricing, but it is not the same thing as evaluation quality.
A ten-page sample that includes the home page, product template, search, account login, form flow, modal dialog, checkout, error state, and an important third-party integration can reveal far more than twenty nearly identical marketing pages. WCAG-EM 2.0 reinforces the importance of understanding the product first and then choosing a representative sample.
For an e-commerce business, for example, a representative audit may need to include navigation, search and filters, product detail, variant selection, cart, checkout, account authentication, promotional dialogs, and third-party payment components. For a medical practice, the relevant sample may include appointment booking, patient forms, PDFs, portal entry points, and contact workflows.
WCAG-EM 2.0 makes audit scope easier to challenge and compare
One practical benefit for buyers is that the updated methodology gives them better questions to ask a vendor. Instead of asking only “Do you test WCAG?” a buyer can ask:
- How did you define the scope?
- How did you explore the site or application before sampling?
- Why were these pages, screens, and flows selected?
- Which browsers and assistive technologies were used?
- Which issues required manual testing?
- How are third-party components handled?
- What does the final report include?
- How are fixes verified during retesting?
These questions separate a real evaluation process from a scanner export branded as an “audit.” Automated tools remain useful, but they cannot independently determine whether every interaction is understandable, operable, and usable with assistive technology.
What changed from WCAG-EM 1.0?
The most visible change is that WCAG-EM 2.0 is no longer limited to websites and web pages. W3C’s WCAG-EM overview notes that the new version applies to apps and other digital products as well.
The methodology is also more technology-agnostic. That is useful for teams evaluating modern digital experiences where a single customer journey may span a responsive website, embedded third-party tool, authenticated web application, and mobile app.
For businesses, the takeaway is not that every audit suddenly needs to become larger. It is that the evaluation should match the real product and the real customer journeys rather than an arbitrary list of URLs.
Does WCAG-EM 2.0 require WCAG 2.2?
No. WCAG-EM is an evaluation methodology and does not itself create a new conformance target. The applicable WCAG version depends on the organization’s goals, contracts, policies, regulations, and other requirements.
W3C currently publishes WCAG 2.2 as the latest WCAG 2 Recommendation, while some laws and regulations specifically reference earlier versions. For example, the U.S. Department of Justice’s Title II web and mobile accessibility rule for state and local governments specifically uses WCAG 2.1 Level AA. Businesses should avoid assuming that one technical standard applies identically in every legal and contractual context.
What should a professional accessibility audit report include?
A useful audit does more than mark success criteria pass or fail. Developers need evidence and context. A developer-ready report should normally identify the affected page or component, the accessibility barrier, relevant WCAG criterion, user impact, reproduction steps, evidence, severity or prioritization, and practical remediation guidance.
It should also explain the evaluation scope and sample. Without that context, a report may look comprehensive while covering only a narrow portion of the product.
This is especially important when the report will be used by multiple teams: engineering, product, design, legal, procurement, or an outside agency. The methodology should make it possible for those teams to understand what was tested and what was not.
How WCAG-EM 2.0 affects small and midsize businesses
Small businesses do not need an enterprise accessibility program to benefit from a structured methodology. The same principles can be applied proportionally.
A dental practice may have a relatively small public website but depend on a third-party booking system and downloadable forms. A restaurant may rely on a menu, reservation platform, online ordering, and location pages. A hotel may depend on room search, booking, date pickers, accessible-room information, and third-party reservation technology.
In each case, the better audit is the one that examines the workflows customers actually need to complete.
What businesses should do now
If you are buying or planning a website accessibility audit in 2026, ask the vendor to document its evaluation methodology before work begins. Confirm the scope, representative sample, critical user journeys, manual testing approach, assistive technologies, deliverables, remediation support, and retesting process.
If you already have a recent audit, you do not necessarily need to repeat it because WCAG-EM 2.0 was published. Instead, review whether the audit clearly documented scope, representative sampling, methods, findings, and limitations. If those elements are missing, the next evaluation is an opportunity to improve the process.
ADA Access Group performs accessibility reviews that combine automated checks with manual testing of important components and user journeys. Request a Website Accessibility Review if you need a structured audit, developer-ready findings, remediation support, or retesting.
Sources
- W3C — WCAG Evaluation Methodology (WCAG-EM) 2.0
- W3C WAI — WCAG-EM 2.0 Note Published, July 23, 2026
- W3C WAI — WCAG-EM Overview
This article provides technical accessibility information and does not constitute legal advice.