If your organization's last accessibility audit was scoped as "the website," that scope is now officially out of date. On July 23, 2026, the W3C's Web Accessibility Initiative published WCAG-EM 2.0 as an official W3C Group Note — the first update to the methodology auditors use to actually score conformance in years. The headline change is not a new success criterion or a new number to hit. It is a redefinition of what gets evaluated in the first place.
For compliance officers, procurement teams, and IT leaders who rely on "we passed our audit" as a defensible position, this matters more than it sounds. An audit methodology is the recipe. Change the recipe, and a report that looked complete last year can be incomplete this year — not because your team did anything wrong, but because the definition of "the whole thing" just got bigger.
What WCAG-EM Actually Is, and Why It Just Changed
WCAG-EM stands for Website Accessibility Conformance Evaluation Methodology. It is not a set of success criteria like WCAG 2.1 or 2.2 — it is the process document that tells an auditor how to conduct a defensible conformance evaluation: how to define the scope of what's being tested, how to select a representative sample of pages or screens, how to audit that sample, and how to report the results. Two auditors using two different informal processes can reach two different conclusions about the same site. WCAG-EM exists to make that process consistent and auditable.
A first draft of WCAG-EM 2.0 was published on February 5, 2026, and after a public review period, the W3C finalized it as a Group Note on July 23, 2026. The most consequential change in that update is scope: the original methodology was written specifically for websites. WCAG-EM 2.0 broadens that scope to explicitly cover "apps and other digital products" — a significant expansion from the web-only focus of the original version.
Why "Websites Only" Was Already a Problem
Most organizations subject to accessibility obligations today are not running a single monolithic website. They're running a public-facing site, a customer portal, a native mobile app, an internal employee tool, and increasingly, embedded product experiences that don't look or behave like a traditional webpage at all. An evaluation methodology written only for "websites" left a genuine gap: auditors doing rigorous, methodology-driven website testing while apps and other digital products got evaluated informally, inconsistently, or not at all. WCAG-EM 2.0 closes that gap by design, not as an afterthought.
The Stat: Nearly 96% of home pages tested still contain detectable WCAG 2 failures, which is exactly the baseline problem a more rigorous, broader-scope evaluation methodology is meant to catch earlier. (Source: WebAIM Million)
What This Means for How Your Organization Gets Evaluated
The scope change is not cosmetic. WCAG-EM's process — defining the evaluation scope, selecting a representative sample, auditing that sample against WCAG, and reporting results in a structured, defensible way — now applies formally to the same categories of digital assets that regulators, plaintiffs' counsel, and enterprise procurement teams already expect to be covered. An audit scoped narrowly to "the marketing website" while ignoring the mobile app or the customer portal was already a weak position. Under WCAG-EM 2.0, it is a position that runs against the published methodology itself.
WCAG-EM 1.0 vs. WCAG-EM 2.0
| WCAG-EM 1.0 | WCAG-EM 2.0 (July 2026) | |
|---|---|---|
| Scope of evaluation | Websites | Websites, apps, and other digital products |
| Published | Original W3C methodology | Group Note, July 23, 2026 |
| Draft stage | N/A | First draft published February 5, 2026 |
| Applies to mobile/native apps | Not explicitly | Explicitly in scope |
| Applies to internal/product tools | Not explicitly | Explicitly in scope |
That table is the entire strategic takeaway in one place: if your last conformance evaluation was written against the old, narrower assumption of "website," it was scoped correctly for the methodology that existed at the time. It is not automatically scoped correctly for the one that exists now.
What Compliance and IT Leaders Should Do Now
None of this requires panic. It requires a scoping conversation, and it requires it before your next audit cycle rather than after a regulator or plaintiff's counsel points out the gap for you.
- Inventory every digital product, not just the website — customer portals, native mobile apps, kiosks, embedded product UIs, and internal tools that employees or the public rely on.
- Ask your current or prospective auditor directly whether their evaluation methodology and sampling approach have been updated to reflect WCAG-EM 2.0's broadened scope, or whether they are still working from a website-only framework.
- Re-scope your next conformance evaluation to explicitly name which apps and digital products are included, and which are deliberately excluded and why — a defensible scope statement is now part of a defensible audit.
- Treat this as a floor, not a checkbox. A methodology update tells you what must be evaluated. It does not fix a single accessibility defect on its own — the underlying WCAG success criteria and the discipline of fixing what the audit finds still do that work.
It's worth remembering the scale of what's at stake here. Roughly 1 in 4 US adults has a disability, according to the CDC, and color vision deficiency alone affects an estimated 8.3% of men and 0.5% of women, per the WHO. Every app, portal, or product left out of an evaluation's scope is a live gap for a real proportion of the people trying to use it — not a theoretical compliance line item.
The Bottom Line
WCAG-EM 2.0 does not change what "accessible" means. It changes what counts as a complete evaluation of whether you've achieved it. For any organization that has been treating "the website" as the entire compliance surface area, this is the moment to correct that assumption on paper, before it gets corrected for you in a demand letter or a procurement review. The organizations that get ahead of this will be the ones who re-scope their evaluations proactively rather than reactively.
If you're not certain your current audit scope would hold up against WCAG-EM 2.0's broader definition of a digital product, don't guess. Get a full accessibility audit that evaluates your actual digital footprint — website, apps, and product experiences included — and know exactly where you stand.