The four groups
- 1.3 in draft
ARIA
Accessible Rich Internet Applications Working Group
The roles, states and properties that tell assistive technology what a custom control is and what it is doing.
- Draft Note
WCAG2Mobile
Guidance on Applying WCAG 2.2 to Mobile Applications
How each WCAG 2.2 success criterion reads when the thing being tested is a native or hybrid app screen instead of a web page.
- 5 new drafts
COGA
Cognitive and Learning Disabilities Accessibility Task Force
Research and design guidance for people with cognitive and learning disabilities, including needs WCAG's testable criteria do not reach.
- Format 1.1
ACT
Accessibility Conformance Testing
A shared format for writing accessibility test rules, so two tools testing the same criterion reach the same answer.
What is coming, across all four
Items the groups have planned or proposed. Things that already happened, and this site's own readings, are on each group's page.
- Late 2026
ARIA: WAI lists an updated ARIA 1.3 draft for September to November 2026, ahead of Candidate Recommendation.
Planned by the group - 1 Jan 2027
ARIA: The current charter ends. A draft charter runs 1 January 2027 to 31 December 2028.
Proposed, not yet agreed - 2027 to 2028
ARIA: The draft charter makes ARIA a Living Recommendation: new features chosen in March 2027, a call for review of amendments in March 2028, and an amended Recommendation in December 2028. It names no ARIA 1.4 or 2.0. The ACT Task Force heard in June 2026 that ARIA will become evergreen, with numbering possibly revisited later.
Proposed, not yet agreed - 2027 to 2028
ARIA: New deliverables in the draft charter: AT-Driver (a standard way for test tools to drive screen readers), CSS Accessibility API Mappings, and PDF Accessibility API Mappings. MathML-AAM is listed as tentative.
Proposed, not yet agreed - Sep to Nov 2026
WCAG2Mobile: WAI lists an updated WCAG2Mobile draft for this window.
Planned by the group - 29 Oct 2026
WCAG2Mobile: Task Force session at TPAC 2026 in Dublin covering mobile, ACT and techniques.
Planned by the group - Later draft
WCAG2Mobile: Guidance for the criteria with the largest deviations from the web reading, plus guidance at the principle and guideline level.
Planned by the group - When complete
WCAG2Mobile: Publication as a final Group Note, as WCAG2ICT was. It stays informative. After that the Task Force may turn to mobile techniques.
Planned by the group - Open question
WCAG2Mobile: Whether the scope widens. At the 15 September meeting one participant asked the group to consider a broader scope, and several others argued the narrow version fills a real gap for developers and auditors.
Proposed, not yet agreed - 2026
COGA: The three new research modules reach final edit and pre-publication. Getting one module ready takes about a month.
Planned by the group - End of 2026
COGA: Finish the WCAG 3 provision review, if possible.
Planned by the group - 2027
COGA: Update the Supported Decision-Making module.
Planned by the group - Ongoing
ACT: Proposed rules move to approved as tools implement them. Counts on this page refresh weekly from the WAI rules data.
Planned by the group - 29 Oct 2026
ACT: ACT is on the agenda for the TPAC 2026 session in Dublin.
Planned by the group - After ARIA 1.3
ACT: 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
Why these four
ARIA changes what correct markup is. WCAG2Mobile changes how WCAG is read for apps. COGA shapes the cognitive provisions in WCAG 3, many of them assertions. ACT decides how tools test all of it. Other W3C groups matter too, such as CSS for user preference media queries, but these four are closest to WCAG itself.