Art, design & a little curiosity
Accessible design ↗

WCAG 3.0 draft: read it as a design review, not a new rulebook

W3C published a new WCAG 3.0 Working Draft on 10 September 2026. Learn how to inspect its evolving requirements and use them to ask better design questions while keeping current WCAG 2 obligations clear.

Original abstract visual study for accessible design.
Original visual study / Accessible design

A new draft is an invitation to examine, not a compliance switch

On 10 September 2026, the W3C Accessibility Guidelines Working Group published an updated WCAG 3.0 Working Draft. It presents a developing model for accessibility guidance, with user needs expressed through guidelines, requirements, assertions, and technology-specific methods. That is a meaningful development for designers because it makes the structure and status of proposed guidance visible. It is not a finished replacement standard: W3C labels the document a work in progress, says it may change, and states that WCAG 3 does not deprecate WCAG 2.

This distinction changes how to use the document. A draft can broaden the questions in a design critique, expose a need that an older checklist did not make easy to discuss, or invite feedback about whether a proposed test is practical. It cannot by itself tell a team that its existing accessibility commitments have expired. Keep the version and status beside any note you take from it, especially when that note travels from a design review into a product requirement.

Read the maturity label before drawing conclusions

The draft marks sections with maturity stages such as Developing, Refining, and Mature. Those labels describe the working group’s state of development; they are not grades assigned to a product or a declaration that every “Mature” item is already an enforceable rule. The document also separates normative material from informative explanation. Before you turn a sentence into an acceptance criterion, check whether it sits in a requirement, an example, a plain-language summary, or an editor’s note.

That is a small information-design problem. Imagine a team copying a paragraph about a flexible input method into a ticket. Without its status, someone may read an exploratory draft as a settled specification. Add a compact note with the document title, publication date, section link, maturity label, and the question the team wants to explore. The note preserves context while still letting the draft inform current thinking.

Translate one draft idea into a useful design question

Choose one interface element and inspect the relevant draft requirement in context. For a chart, you might ask whether its meaning remains available when a reader changes input method, enlarges text, or reaches the same information through a nonvisual route. Do not assume that a similar phrase in a draft creates a new legal threshold. Compare the question with the current standard and with the actual user task, then record what is already supported, what is uncertain, and what would need testing.

A good critique separates evidence from aspiration. “The chart has labels and a table” is an observation. “A reader can use either route to answer the same question” is a claim to check. Try both routes with the chart’s real content, including units, exceptions, and any caveat that changes the interpretation. If one route loses an important relationship, revise the design and document why. The exercise improves the artifact even when the draft later changes.

Keep today’s obligations and tomorrow’s learning in separate columns

W3C explains that WCAG 2 remains in use and is not being deprecated by this draft. The working group also describes differences in testing and conformance, and says more transition support is expected for people who choose to migrate in the future. For a team, a practical response is to maintain two related records: the applicable current requirements and a separate learning list for ideas under discussion in WCAG 3. Give each record its version, owner, and review date.

This keeps design exploration active without making an unsupported promise to customers or colleagues. It also makes future revision easier: when a draft changes, update the learning list and recheck affected work instead of silently rewriting the current baseline. Accessibility is still judged by whether people can use the experience, not by how modern a checklist looks.

Put it into practice

Try it yourself

  1. Open the dated W3C Working Draft and note its status before reading a selected section.
  2. Choose one real screen or interaction and record the user task it supports.
  3. Separate what you observe from what you infer; label draft ideas as exploratory.
  4. Compare the experience with current applicable requirements and test the alternate route.
  5. Save the section link, version date, unresolved question, and review owner.
A worked example

Worked example: reviewing a chart in a museum guide

A guide uses a color-coded timeline to compare three galleries’ opening periods. First write the task: find which gallery is open latest and notice any seasonal exception. Record the existing WCAG 2 checks separately. Then use the WCAG 3 draft as a prompt for an exploratory review: can a keyboard user reach the timeline, can a screen reader identify each gallery and date range, and is the seasonal exception available in the text alternative? Try the graphic and its accompanying table without assuming either route is equivalent. If the table omits the exception, add it and retest. Label the WCAG 3 observation “draft exploration,” link the exact section, and keep it out of a formal conformance claim until the standard and applicable policy support that claim.

References & further reading

Examples and exercises in this guide are original teaching scenarios.

Keep following the thread.

More accessible design ↗

Keyboard focus: make the path visible

Design keyboard focus as a visible state that can be followed through an interface. Shape the indicator, test its contrast and placement, and check that fixed layers do not hide the control receiving focus.