On 10 September 2026 the W3C published a new Working Draft of WCAG 3.0, the W3C Accessibility Guidelines, alongside an updated Explainer. As of mid-November it is still the latest version: the W3C publication history lists nothing newer, and the “latest published version” of WCAG 3.0 is this draft.
We covered the March 2026 draft when it renamed outcomes to requirements. The September draft goes further. It does not just add requirements. It rewrites what it means to conform. We compared both drafts requirement by requirement, counting everything from the published HTML.
The short version: WCAG 3 is still a Working Draft with, in the working group’s own words, several years of work left. WCAG 2.2 remains the standard to conform to, and W3C’s own advice is that meeting WCAG 2.2 now is the best way to prepare.
The September draft at a glance
- Published: 10 September 2026, as a W3C Working Draft on the Recommendation track. The previous draft was 3 March 2026.
- Companion document: an updated Explainer, published the same day as a Group Note Draft. It is informative and is not expected to become a W3C Recommendation.
- Conformance: a single bar. A defined scope conforms when all core requirements are met. Supplemental requirements and assertions are no longer needed to conform.
- Bronze, Silver and Gold: moved out of conformance into a new, informative Reporting section, where they are tiers 4 to 6 of six reporting tiers.
- Size: 46 guidelines and 216 provisions, up from 44 guidelines and 182 provisions in March (our count).
- Maturity: every provision in both drafts is at Developing status. Nothing has reached Refining or Mature. Exploratory provisions are left out of the published draft by design.
- Still undecided: the contrast algorithm, the numeric values for text readability, which requirements carry which severity tag, and the number of supplemental requirements needed for each tier above conformance.
The big change: conformance is now one bar
In the March draft, the Conformance section defined three conformance levels. Bronze, the minimum, required every page or process in scope to meet all core requirements plus some portion, still to be determined, of the supplemental requirements and assertions. Silver and Gold required larger portions.
The September draft removes that “Conformance level” subsection entirely. Section 3.2 now says that for a defined scope to conform, all core requirements must be satisfied. That is the whole test. An editor’s note explains that the update “moves the concept of leveling from conformance to reporting”, and that the draft calls them reporting tiers to keep them distinct from the old conformance levels.
Two smaller changes in the same section reinforce the point. Supplemental requirements are now described explicitly as not required for conformance, and their definition changed from requirements that are currently more difficult or expensive to implement, to requirements that are disproportionately burdensome to implement. What March called best practices are now recommended practices, and the draft states that they are informative.
The Conformance section itself moved from Exploratory to Developing status. By the draft’s own definitions, that means the direction is roughly agreed but details are still being worked out.
A correction to the record: many descriptions of WCAG 3, including the first version of our own March article (since corrected), described a graded or scored conformance model. That idea dates from earlier drafts and is not what the September draft says. Conformance is binary: every core requirement is met, or the scope does not conform. Scoring survives only as an alternative proposal for reporting progress, described below.
The new Reporting section and its six tiers
Section 4, Reporting, is new. It is marked Exploratory and informative, which means it gives advice and sets no requirements. It introduces tags for core requirements, based on the worst harm that failing them could cause:
- Physical harm: failure can cause a disabled person immediate physical harm.
- Risk: failure unreasonably increases financial, medical, legal, privacy or security risk.
- Barrier: failure can stop a disabled person from proceeding.
- Friction: failure can hinder a disabled person, and several such failures together can stop them.
The tiers are cumulative:
- Tier 1, avoid physical harm: all physical harm and risk requirements are met.
- Tier 2, foundational access: tier 1 plus all barrier requirements.
- Tier 3, conformance: tier 2 plus all friction requirements, which means every core requirement.
- Tier 4, Bronze: conformance plus a to-be-determined number of supplemental requirements and content assertions.
- Tier 5, Silver: a larger, still undetermined number of the same.
- Tier 6, Gold: adds assertions about the organization, such as staff training or public accessibility statements.
The draft says plainly that WCAG declares conformance when the core requirements are met, and that policymakers have the flexibility to require additional tiers. W3C’s blog post on the draft frames this as WCAG being the ruler and laws being the rules: the tags could let a regulator ask more of essential government services than of less important websites.
One thing to know if you try to use the tiers today: the published draft defines the four tags but, in our check of the HTML, does not yet assign a tag to any individual requirement. You cannot yet work out which requirements fall into tier 1 or tier 2.
The rival proposal: scoring
The tiers are not settled. An editor’s note in the draft invites comment on an alternative that the Explainer sets out in full. Under that proposal, the same tags weight a percentage score toward conformance: 3 points for physical harm and risk provisions, 2 for barrier, 1 for friction and the rest. Once a scope conforms, counting supplemental requirements and assertions would lead to WCAG 3 Bronze, Silver and Gold awards. In both versions, Bronze, Silver and Gold sit above conformance rather than defining it. The working group has also not decided whether assertions can ever be required for conformance.
Scope, support sets and functional needs
- Wider scopes. March allowed claims about pages or views and processes. September lets a claim cover a product, site, subsite, application or other defined set, and adds paths and components as limited scopes. The draft says paths and components are still being defined.
- Accessibility support set. As in March, a conformance claim must include the accessibility support set, the browsers and assistive technologies the methods were checked against. The default set is described as supporting web methods rather than HTML methods, and it has still not been defined.
- Functional performance statements. The expanded list grew from 17 to 18 and was rewritten. New entries include use with hyposensitivity, use with hypersensitivity, use with very limited or no identifying characteristics (for biometrics), and use with intersectional disabilities, such as deafblind people.
What changed in the guidelines
By our count of the published HTML, the March draft contained 182 provisions: 92 core requirements, 61 supplemental requirements, 28 assertions and 1 best practice. The September draft contains 216: 106 core requirements, 74 supplemental requirements, 35 assertions and 1 recommended practice. Guidelines went from 44 to 46. Two guidelines, Figure captions and Control text, still have no provisions at Developing status in either draft.
Bear in mind that the published draft only includes provisions that have reached Developing status. A provision that disappears may have been merged, renamed or sent back for more work. The draft does not say which.
Media alternatives were broken up
March had a single Media alternatives guideline. September replaces it with three: Transcripts, Sign language and Accessible media player. Requirements that used to apply to media alternatives in general, such as identifying speakers, sounds and visual information, are now written separately for transcripts, captions and audio descriptions. Captions and audio descriptions each gained an “equivalent” requirement, plus assertions about style guides, usability testing and review by content authors. A live sign language assertion was replaced by one about having a policy to provide interpretation at live events, including how to request it.
Text appearance grew, but the numbers are blank
Text appearance went from 3 provisions to 11. New core requirements cover readable blocks of text, readable text style, text contrast, and the ability to adjust blocks of text and text style, with enhanced versions as supplemental requirements. Almost every value is a placeholder. In the text contrast requirement, the contrast measure itself is a bracketed placeholder marked as still to be determined, and an editor’s note says the WCAG 3 contrast algorithm is yet to be determined. The draft does not name APCA or any other method. The readability requirements also leave margins, line length, line height and type properties as values to be determined.
Other notable additions and removals
- Clear language gains Summaries available, a core requirement for pages of long-form text with 300 or more words, and Common words used, a supplemental requirement. An editor’s note says the 300-word threshold needs research.
- No flashing is now No flashing over threshold. An editor’s note says research into size and frequency metrics is under way and the values are likely to change.
- No repetitive links became No repetitive adjacent interactive elements, a supplemental requirement aimed at the common pattern of an image link and a text link going to the same place.
- Expected behavior gains Consistent control location, and Media control gains Media chapters available. Both are supplemental.
- Keyboard navigable if responsive, a March core requirement, no longer appears in the published draft.
What has not changed
WCAG 3 is not close to final. Nothing is at Refining or Mature status. The Explainer states that WCAG 3 will not be published until it covers at least as much as WCAG 2.2, and W3C’s introduction says WCAG 2 will not be deprecated for several years after WCAG 3 is finalized. W3C’s blog post on the draft says the core requirements build on the WCAG 2.2 Level A and AA success criteria, so work toward WCAG 2.2 AA is not wasted.
Laws and procurement rules today reference WCAG 2.x, directly or through standards such as EN 301 549. No regulator can point to WCAG 3 conformance yet, because the conformance model is still in draft.
What to watch next
- A December draft. The working group’s schedule page, which carries a note that it may not represent group consensus, plans an updated Working Draft in December 2026 with updated provisions and a revised accessibility supported section. It targets a Candidate Recommendation Snapshot in 2027. Treat both as plans.
- Tiers or scoring. The public review questions ask directly which approach is better. Whichever wins will decide how accessibility progress is reported in audits and procurement.
- Tag assignments. Once requirements are tagged as physical harm, risk, barrier or friction, the tiers become something you can measure against.
- Contrast. The schedule page notes that a planned note on a colour algorithm was put off because the research is not yet sufficient. Until the draft names a method, do not plan around one.
- Movement to Refining. Refining is the first status the working group describes as ready for experimental adoption. Nothing has reached it yet.
What this means for your team
Keep building and testing to WCAG 2.2 AA. If you want to get ahead, the September draft suggests two habits worth starting now. First, rank your accessibility issues by impact, separating anything that could cause harm or block a task from friction, because that is how WCAG 3 reporting is likely to work. Second, look at the assertions, such as caption style guides, usability testing with disabled people and accessibility training. They describe processes that improve products regardless of how the standard ends up scoring them.
Our resources can help with both:
- Read our WCAG 3 overview, updated for the September 2026 draft.
- Understand core requirements, assertions and reporting tiers in WCAG 3 key concepts.
- See how the new model compares with today’s in our WCAG 2 vs WCAG 3 comparison.
- Plan ahead with our WCAG 3 preparation guide.
- Meet the standard that applies now with our WCAG 2.2 checklist.
- Find issues on a live page with the URL accessibility auditor.
- For the previous step, read our coverage of the March 2026 draft.
Sources
- W3C: W3C Accessibility Guidelines (WCAG) 3.0, Working Draft (10 September 2026)
- W3C: W3C Accessibility Guidelines (WCAG) 3.0, Working Draft (3 March 2026)
- W3C: WCAG 3.0 publication history
- W3C: Explainer for W3C Accessibility Guidelines (WCAG) 3.0, Group Note Draft (10 September 2026)
- W3C Web Accessibility Initiative: For Review: WCAG 3 Working Draft, September 2026 (10 September 2026)
- W3C Web Accessibility Initiative: WCAG 3 Introduction (updated 16 November 2026)
- W3C Blog, Shawn Lawton Henry: Crafting WCAG 3 for more accessible user experiences (25 September 2026)
- Accessibility Guidelines Working Group: WCAG 3 schedule (project wiki)