On September 10, 2026, the W3C quietly published a new working draft of WCAG 3.0 — and this one is worth paying attention to, because it reworks the part of the standard that has confused people since the project started: how conformance actually gets measured. If you run a WordPress site and you’ve been half-following WCAG 3.0 since the March 2026 draft, the conformance model has moved, and it’s worth understanding what changed before anyone starts telling you it’s “the new legal standard.” (It isn’t. Not yet, and not for years.)
What Actually Changed in the September Draft
WCAG 2.x conformance is a scoring system built on letter grades: Level A, AA, AAA. Every success criterion is binary — you pass it or you fail it — and your overall conformance level is the lowest grade among everything you attempted to meet. It’s simple, but it’s also brittle. A site can pass 200 checkpoints and fail one contrast requirement on a single button, and technically it isn’t AA conformant.
The September 2026 draft pushes further on an idea that’s been developing since earlier this year: replacing the A/AA/AAA ladder with a different structure built around three types of requirements:
- Core requirements — the baseline any conformance claim has to meet, roughly analogous to today’s “must-fix” items.
- Supplemental requirements — things that go beyond the baseline, closer to what AAA covers today, but structured so sites can claim partial credit instead of an all-or-nothing grade.
- Assertions — a genuinely new category. Instead of a pass/fail test, an organization documents a policy or process it follows, like a captioning style guide or a record of usability testing with screen reader users.
That assertions category is the biggest departure from anything in WCAG 2.x. It acknowledges that some accessibility work — testing with actual disabled users, maintaining a consistent process — doesn’t reduce cleanly to a checklist item, even though it matters. The tradeoff is that assertions are harder to audit from the outside than a contrast ratio you can measure with a tool.
A Single Conformance Level, With Tiers Around It
The other notable shift in this draft is the conformance model itself. Rather than three distinct levels you climb (A, then AA, then AAA), the current proposal is a single conformance level, with additional reporting tiers below and above it. In plain terms: there’s one bar that counts as “conformant,” but the standard also wants a way to report how far above or below that bar a site actually lands, instead of forcing everything into three buckets.
If that sounds like it’s trying to fix WCAG 2.2’s biggest practical complaint — that a site can be excellent everywhere except one checkpoint and still get scored as a total failure — that’s roughly the intent. Whether it succeeds is an open question the W3C is actively asking reviewers about right now.
Why This Isn’t Actionable Yet — And Why You Should Still Care
It’s worth being direct about this: nothing in the September 2026 draft is enforceable, referenced by any regulation, or expected to be a finished W3C standard for years. The DOJ’s ADA Title II rule, state-level mandates like Washington’s and Missouri’s, and virtually every settlement in an accessibility lawsuit right now still point to WCAG 2.1 or 2.2 Level AA. If you’re prioritizing work on your WordPress site this quarter, WCAG 3.0’s conformance model changes nothing about that priority list.
So why track it at all? Two reasons:
- The underlying accessibility work doesn’t change. Whatever conformance model eventually ships, the actual fixes — proper heading structure, keyboard access, alt text, sufficient contrast, labeled form fields — remain the same work. WCAG 3.0 is reorganizing how conformance gets reported, not inventing a new definition of what “accessible” means.
- The assertions concept previews where documentation requirements are heading. Even under WCAG 2.2, more jurisdictions and more plaintiffs’ attorneys are asking for evidence of process — audit trails, testing records, remediation timelines — not just a scan result. Getting comfortable documenting what you did and when, now, will matter regardless of which version of WCAG eventually formalizes it.
What to Actually Do With This News
If you manage a WordPress site, the practical response to this draft is almost anticlimactic: keep doing the WCAG 2.2 AA work you should already be doing, and don’t let anyone sell you a “WCAG 3.0 ready” product today — there is no finished WCAG 3.0 to be ready for. The W3C itself is still collecting public comments on the conformance model in this draft, which means the structure described above could change again before it’s finalized.
What is useful right now is building the habit the assertions model anticipates: keeping records. When you fix a contrast issue, note it. When you test a form flow with a screen reader, log what you found. That documentation protects you today under WCAG 2.2 — a specific, dated record of remediation work is one of the more persuasive things you can show if a demand letter arrives — and it happens to be exactly the kind of evidence WCAG 3.0’s assertions category is trying to formalize for tomorrow.
Take Action
Standards will keep evolving, but the code-level work — fixing missing alt text, broken heading order, unlabeled form fields, and insufficient contrast — is what actually protects your visitors and your site today, whatever the conformance model is called. LEWCA scans your WordPress site for those real, WCAG-mapped issues and gives you a clear, dated record of what was found and fixed — not a widget bolted on top to mask problems, but a log of genuine code-level remediation. Pro adds AI-assisted fixes, scheduled scanning, and compliance reports, so you have exactly the kind of documentation this next generation of WCAG is starting to formalize. Check out LEWCA’s pricing or download LEWCA to start scanning your site today.