a11y teacher edition W3C WCAG 2.2 & WCAG 3.0 draft reference
Plain English Accessibility Hub

Translating W3C Standards for Designers, Developers, QA & Product teams

Reviewed 8 October 2026. Publication dates are checked against the W3C documents themselves every week, and rule counts against the WAI rules data. Every fact links to a source at the bottom of the page.

In plain English

ACT exists because tools disagree. The ACT Rules Format is a W3C Recommendation that says how a test rule must be written: what it applies to, what it expects, its assumptions and worked pass and fail examples. Rules written in that format are then checked against real tools.

Two groups share the work. The ACT Rules Community Group writes rules, which have no formal W3C standing. The ACT Task Force in the AG Working Group maintains the format and reviews rules for approval, which needs at least one tool or methodology to implement the rule fully. Approved rules are still informative and are not required to determine WCAG conformance.

What is published today

Published documents for ACT, with status and date
Document Status Date What it is
ACT Rules Format 1.1 Recommendation 5 February 2026 The current format. It coexists with 1.0 and is not fully backward compatible.
ACT Rules Format 1.0 Recommendation 31 October 2019 The original format.
ACT Rules on the WAI site Informative Ongoing 94 rules listed: 37 approved, 50 proposed and 7 deprecated. 17 map to no WCAG success criterion (mostly ARIA checks).

In development

What changed in ACT Rules Format 1.1

Recommendation, 5 February 2026

Candidate Recommendation 19 August 2025, Recommendation 5 February 2026 with no changes in between.

  • Accessibility requirements are now marked as conformance requirements or secondary requirements.
  • Applicability may now be subjective, and the objective and plain-language rules were relaxed from must to should.
  • Accessibility Support and Assumptions move under a Background section, with optional Related Rules and Other Resources.
  • Each rule must say which format version it targets, and Change Log is renamed Rule Versions.
  • A new Implementations section says how to judge whether a tool's check is consistent with a rule.
  • Outcomes can now be cantTell and untested as well as passed, failed and inapplicable.

Recent Task Force work includes a glossary review, a new resizing rule, and an impact review of ARIA 1.3 on existing rules (ACT issue 2400), which found the impact small.

How it connects to WCAG

WCAG 2.2

ACT rules map to WCAG 2 success criteria and to ARIA. When a tool says it implements an ACT rule, you can read the rule to see exactly what it tests and, just as usefully, what it assumes and leaves out.

WCAG 3 draft

The rules list maps only to WCAG 2 and ARIA today. There are no ACT rules for WCAG 3 provisions yet, which fits a draft where nothing has reached refining status. ACT is on the agenda for the TPAC 2026 session on 29 October. The 1.1 changes for subjective applicability and the cantTell outcome are the kind WCAG 3's less binary provisions would need, though no group has said so.

What the future holds

Each item says how firm it is: something that has happened, a plan the group has stated, a proposal not yet agreed, or this site's own reading of where things are heading.

  1. Ongoing

    Proposed rules move to approved as tools implement them. Counts on this page refresh weekly from the WAI rules data.

    Planned by the group
  2. 29 Oct 2026

    ACT is on the agenda for the TPAC 2026 session in Dublin.

    Planned by the group
  3. After ARIA 1.3

    Rules updated for ARIA 1.3 changes such as names no longer required on dialog, and possible push-back on the braille attributes.

    Proposed, not yet agreed
  4. Open question

    When ACT rules start being written for WCAG 3. That likely waits until WCAG 3 provisions stabilise.

    This site's reading

What this means for your team

Start now

Useful whatever happens next

  1. Ask your testing tool vendor which ACT rules it implements.

    The implementation reports show which rules each tool fully or partly matches, which tells you where its results can be trusted.

  2. Use ACT rule examples to settle disputes.

    Each rule has passed and failed examples. They are a neutral reference when a tool and a tester disagree.

Cheap hedges

Low cost, likely to pay off

  1. Treat proposed rules as signals, not verdicts.

    They are community rules without formal standing until approved.

Wait

Too early to build for

  1. Do not build WCAG 3 test suites yet.

    There are no ACT rules for WCAG 3, and the provisions are still changing.

What this site watches

  1. Approved rule count rising
  2. Rules updated for ARIA 1.3
  3. Any ACT rules or test work for WCAG 3 provisions
  4. TPAC 2026 outcomes on ACT and techniques

Sources