Skip to main content
Accessibility.com, LLC
Category: Testing and Evaluation

WCAG Evaluation Methodology

Also known as: WCAG-EM, WCAG Evaluation Methodology, WCAG-EM 2.0
Simply put

WCAG-EM is a structured approach published by the W3C for checking how well a website or other digital product meets the Web Content Accessibility Guidelines (WCAG). It provides a step-by-step process so that evaluations are done consistently rather than ad hoc. A companion online tool can help turn evaluation findings into a report.

Formal definition

WCAG Evaluation Methodology (WCAG-EM) is a W3C/WAI methodology that defines a step-by-step process for determining how well a digital product conforms to the Web Content Accessibility Guidelines (WCAG). It offers a structured framework for scoping and evaluating conformance and is supported by the WCAG-EM Report Tool, which converts evaluation findings into a report. WCAG-EM is a methodology for assessing conformance and is distinct from WCAG itself, which defines the success criteria being evaluated; note that following the methodology supports consistent evaluation but does not by itself guarantee accessibility or legal compliance. This entry is informational and not legal advice.

Why it matters

Accessibility evaluations that are performed ad hoc can produce inconsistent results, where different reviewers reach different conclusions about the same site or miss entire sections of a digital product. WCAG-EM matters because it provides a shared, structured process for scoping and evaluating conformance to the Web Content Accessibility Guidelines, which helps organizations produce evaluations that are more repeatable and comparable across teams, vendors, and points in time.

For compliance officers, legal counsel, and accessibility teams, a documented and methodical evaluation approach can support internal decision-making and demonstrate that testing followed a recognized framework rather than an improvised checklist. It is important to keep the roles distinct: WCAG-EM is a methodology for assessing conformance, while WCAG itself defines the success criteria being measured. Following the methodology supports consistent evaluation but does not by itself guarantee that a product is accessible to all users or that it satisfies any particular legal obligation.

WCAG-EM should be understood as one part of a broader testing and evaluation practice. Because conformance evaluation and real-world usability are not the same thing, and because legal requirements evolve through regulation and case law, organizations should treat WCAG-EM as a way to structure their assessment work rather than as a source of legal safety. This entry is informational and is not legal advice; questions about specific obligations should be directed to qualified legal counsel and current agency guidance.

Who it's relevant to

Accessibility engineers and evaluators
Practitioners who assess digital products against WCAG can use WCAG-EM to scope their work and follow a consistent, repeatable process, and can use the WCAG-EM Report Tool to turn their findings into a structured report.
Compliance officers and accessibility program managers
Those responsible for accessibility programs can adopt WCAG-EM as a recognized framework to standardize how evaluations are performed across teams and vendors, supporting more comparable results over time. Following the methodology does not by itself guarantee accessibility or legal compliance.
Legal counsel and risk professionals
Counsel reviewing an organization's accessibility practices may find value in evaluations conducted through a documented, W3C-published methodology. This entry is informational and not legal advice, and specific obligations should be confirmed with qualified counsel and current agency guidance.
UX designers and product teams
Design and product teams can use the structure WCAG-EM provides to understand how their products are evaluated for conformance, while recognizing that conformance evaluation does not fully capture real-world usability for all users and that manual and assistive technology testing remain important.
Third-party auditors and testing vendors
Vendors that deliver accessibility evaluations can align their process with WCAG-EM to provide clients with consistent, methodical assessments and reports based on a recognized W3C approach.

Inside WCAG-EM

Website Accessibility Conformance Evaluation Methodology (WCAG-EM)
A W3C-published methodology, developed through the Web Accessibility Initiative, that describes a structured process for evaluating how well a website conforms to the Web Content Accessibility Guidelines. It is guidance rather than a normative standard, and it does not itself add or change any WCAG success criteria.
Defining the evaluation scope
The first step, in which evaluators establish what is being assessed, including the target WCAG version and conformance level (for example WCAG 2.1 Level AA), the boundaries of the website, and the goals of the evaluation.
Exploring the website
A step for becoming familiar with the site's purpose, key functionality, types of content, and the technologies used, so that evaluators can identify representative and essential pages and processes.
Selecting a representative sample
Guidance for choosing a sample of pages and complete processes to evaluate when testing every page is impractical, aiming for a selection that reflects the variety of content, templates, and functional workflows on the site.
Auditing the selected sample
The step in which each selected page and process is evaluated against the chosen WCAG success criteria, commonly using a combination of automated tooling, manual inspection, and assistive technology testing rather than automated checks alone.
Reporting the findings
The final step, in which results are documented, including the scope, methods used, criteria evaluated, outcomes, and any aggregated conformance information, so the evaluation can be understood and, where relevant, reproduced.

Common questions

Answers to the questions practitioners most commonly ask about WCAG-EM.

Does using WCAG-EM guarantee that a website is WCAG-conformant or legally compliant?
No. WCAG-EM is an evaluation methodology, not a conformance standard. It describes a structured process for assessing how well content meets WCAG success criteria, but following the methodology does not by itself produce or guarantee conformance. Conformance depends on whether the content actually meets the applicable success criteria at the chosen level (commonly AA). Separately, meeting WCAG does not guarantee immunity from legal claims, and legal compliance depends on the applicable authority and evolving case law. This is not legal advice; consult qualified legal counsel for questions about your obligations.
Is WCAG-EM a required standard or an official part of WCAG?
No. WCAG-EM is a supporting resource published by the W3C's Web Accessibility Initiative to guide evaluation of conformance to WCAG; it is not itself a set of success criteria and is not a mandated standard. It is generally offered as recommended guidance for how to conduct and document an evaluation, rather than a rule that authorities require you to follow. Which WCAG version and level apply to you, and whether any evaluation is required, depends on the relevant regulation, agency guidance, or settlement.
How do you define the scope of a website when applying WCAG-EM?
WCAG-EM begins with defining the scope of the evaluation, which commonly includes identifying the website or set of web pages to be assessed, the target conformance level (AA is the level most frequently cited as a target), the technologies relied upon, and the range of user agents and assistive technologies to be considered. Establishing a clear scope helps ensure the evaluation is repeatable and that results can be interpreted against a defined boundary.
How does WCAG-EM suggest selecting a representative sample of pages?
For sites too large to test exhaustively, WCAG-EM describes selecting a representative sample that reflects the variety of the site. This generally involves exploring the site to understand its common functionality, page types, and workflows, then choosing a structured sample of pages alongside a random sample. The goal is to cover distinct templates, states, and processes so the evaluation captures the range of content rather than a narrow slice.
What kinds of testing does WCAG-EM expect beyond automated checks?
WCAG-EM treats evaluation as combining multiple methods rather than relying on automated tooling alone. Automated testing detects only a portion of potential issues, so the methodology generally calls for manual evaluation and testing with assistive technologies to assess criteria that require human judgment. Combining these approaches helps produce a more complete picture of how content performs against the applicable success criteria.
How should the results of a WCAG-EM evaluation be recorded and reported?
WCAG-EM emphasizes documenting the evaluation so it is transparent and repeatable. This commonly includes recording the defined scope, the pages sampled, the WCAG version and conformance level targeted, the methods used, and the outcomes against the relevant success criteria. Clear documentation supports review by others and can help track remediation, though it is a record of the assessment process rather than a certification of compliance.

Common misconceptions

WCAG-EM is itself a set of accessibility requirements that a site must meet.
WCAG-EM is a methodology for how to evaluate conformance, not a source of requirements. The requirements come from WCAG success criteria; WCAG-EM describes a process for assessing them and does not create new criteria or conformance levels.
Following WCAG-EM and passing the evaluation guarantees legal compliance under the ADA or Section 508.
WCAG-EM addresses technical evaluation of WCAG conformance and is separate from legal compliance. Meeting WCAG success criteria does not guarantee immunity from legal claims, and applicable obligations depend on the relevant authority and evolving regulation and case law. Consult qualified legal counsel for compliance questions.
Because WCAG-EM allows sampling, evaluating a small number of pages is sufficient to characterize the whole site.
Sampling is a practical accommodation when full evaluation is not feasible, but the method emphasizes selecting a representative sample that covers key templates and complete processes. A poorly chosen or overly small sample may miss issues, and conclusions apply only within the defined scope.

Best practices

Clearly document the evaluation scope up front, including the specific WCAG version, the target conformance level (AA is the level most commonly cited as a target), and the boundaries of the site being assessed.
Build a representative sample that includes key page templates and complete end-to-end processes, such as forms and multi-step workflows, rather than only a handful of static pages.
Combine automated tooling with manual inspection and assistive technology testing, since automated checks detect only a portion of accessibility issues.
Record your methodology and outcomes in enough detail that the evaluation can be understood and, where practical, reproduced, noting the criteria evaluated and the results for each.
Treat WCAG-EM results as an assessment of technical conformance within the defined scope, and recognize that conformance is distinct from real-world usability and from legal compliance.
Where legal exposure or regulatory obligations are a concern, involve qualified legal counsel and monitor current agency rulemaking, as this guidance is not legal advice and requirements evolve.