Summary

  • W3C’s page for the active AGWG charter gives 28 August 2026 as its end date.
  • Draft minutes for 1 September record continued WCAG 3 work, a resolution accepting reviewed updates and a statement that the document would be frozen.
  • The 7 July minutes had already recorded six Formal Objections to the successor charter, possible Council setup and the possibility that an extension would be needed.
  • The checked public sources do not identify the continuity instrument used after 28 August. That absence is not evidence that no valid extension or decision existed.
  • A public authority-continuity receipt should join charter version, review state, extension or interim decision, permitted work, effective interval and later supersession without exposing confidential Member material.

Two public clocks stopped lining up

The active AGWG charter page is unusually clear about its own history. The group was rechartered in November 2023, extended to 30 April 2026 and extended again to 28 August 2026. The status table still gives that last date as the end of the charter.

The draft minutes for 1 September show a functioning technical body. Participants continued word-by-word discussion of WCAG 3 conformance material. The minutes record a resolution accepting the updates outlined in the meeting and the reviewed document. The chair then said the document would be frozen. The meeting also described preparation for a Call for Consensus on the latest Working Draft.

Those are real public records, but they answer different questions. The charter page says when the displayed mandate ended. The minutes say what the group did next. Neither page supplies the public link between them.

The gap should not be inflated. A resolution in draft minutes is not a W3C Recommendation. The current public WCAG 3 report remained the 3 March Working Draft at the evidence cutoff. A planned September publication would still be a Working Draft, open to change. Nor do the minutes prove that a charter extension was absent. They simply do not name one.

July had already described the handoff problem

The sequence was foreseeable. In 7 July minutes, W3C staff said the Advisory Committee review had closed on 2 July with support from 27 Member organisations and Formal Objections from six. Council setup was beginning in case objections needed that route, while the Team would also talk with objectors. The minutes explicitly said an extension might be needed.

That statement preserved uncertainty correctly. A Council was a possibility, not an announced decision. An extension was a possible continuity tool, not an accomplished fact. Work on the core material would continue, but the successor-charter outcome remained separate.

The public objections show why the successor could not be reduced to a date change. One objection asked that the charter preserve the possibility of future normative WCAG 2.x maintenance. A second asked for a separate conformance-model deliverable and tighter WCAG 3 scope. A third supported continued work but sought deadlines, a scope-freeze date, intermediate milestones and a monthly progress dashboard.

These are not votes against accessibility work. They are disputes over scope, sequence and accountability. Continued editing cannot silently dispose of them; equally, their existence does not require the technical group to stop every preparatory task.

The Process provides several lawful bridges

The W3C Process Document distinguishes the available instruments. A new or materially changed charter requires a W3C Decision after Advisory Committee review. A minor change, including a qualifying extension, may be approved by a Team Decision. For an extension, the Team must announce the new duration to the Advisory Committee and include rationale, a charter reference and the group homepage.

That architecture allows continuity without pretending that rechartering is complete. An unchanged extension can preserve the existing scope while objections to the successor are addressed. A later Call for Participation can mark the approved successor. Publication and maturity transitions remain separate decisions.

The problem is not that the rules lack a mechanism. It is that the checked public surfaces do not tell an outside reader which mechanism applies to the 1 September work. The active page still ends on 28 August; the minutes continue after it; the July minutes said an extension might be required.

The 27 August pre-CFC discussion sharpens the timing. It preserved a tentative plan for a 31 August–3 September Call for Consensus and 8 September publication. That schedule was expressly subject to change. It shows operational intent, not the authority instrument supporting the timetable.

A continuity receipt can protect both sides of the record

The repair can stay thin. Start with the group identifier and immutable expiring-charter version. Record its displayed end date. Add the proposed successor version, AC-review interval, Formal Objection count and public disposition state. Confidential Member submissions can remain protected.

Then name the continuity instrument: unchanged extension, approved recharter, bounded interim decision or another defined mechanism. Identify the authorised issuer, decision reference, effective time, new end date and permitted scope. Link the meetings, resolutions and publication requests that rely on it. When a successor charter arrives, close the interval rather than overwriting it.

The receipt should include explicit non-conclusions. Continued work does not prove that the new charter was approved. A missing public link does not prove that the group acted without authority. A Working Draft resolution does not make WCAG 3 a Recommendation. Six Formal Objections do not reveal six outcomes.

Lu Heng’s Multi-Stakeholder Mirage supplies the useful discipline: participation is evidence, while authority requires an identifiable principal and instrument. Here, the participants and their work are visible. The missing public object is the instrument connecting one mandate interval to the next.

Sources