Main Page/


Designing WCAG

This page contains and links to information relevant to designing and evaluating models for future work for WCAG. At this time, most of the information here is related to work on Extensions being developed by the Mobile, Cognitive, Low Vision Task Forces. See the WCAG Next Steps Workshop link for some of the brainstorming data that is more relevant to a major WCAG revision.

WCAG Next Possible Models

Alternative models for producing a minor revision of WCAG that incorporates the work being done in Task Forces on Extensions to WCAG.

WCAG Next Steps Workshop archived material

This is material that was originally developed for the first meeting. It is combined with notes from the first meeting that would be useful for brainstorming sessions for long-range work on WCAG.

First Session: March 14, 2016

Scheduled for: 8:00 AM - 10:30 AM Central Daylight Time (9:00 AM Boston, 1:00 PM UTC/London).

Minutes of the meeting:

Second Session: Teleconference 18 March 2016

IRC channel #WCAGnext


  • Introductions (5 minutes)
  • Level Set (5 minutes)
  • What Models do we think we have? (20 minutes) (worksheet)
  • Readiness states by TF (20 minutes)
  • Socialization & Feedback/Comments (20 minutes)
  • Next Steps (10 minutes)


Minutes of 18 March Teleconference

Third Session: Open Meeting at CSUN 24 March 2016

Minutes of 24 March at CSUN

Summary of Minutes

WCAG wiki:

  • WCAG 2.0 is 8 yrs old and is showing its age. Technology has changed and some user needs were not addressed
  • Task Forces (mobile, low vision and cognitive) of the WCAG WG were formed to address these issues.
  • The existing plan for WCAG Extensions has ambiguity
  • Mobile Accessibility Task Force has identified 4 Guidelines and associated success criteria. How do we publish it?
  • Sites declare conformance to the WCAG version they select: e.g WCAG 2.0, or WCAG 2.1. It is for people who want guidance above and beyond WCAG 2.0, not to force people to upgrade before they are ready.
  • Option: WCAG 2.1 model could be WCAG 2.0 plus the work of Mobile TF. Then WCAG 2.2 could be WCAG 2.1 plus the work of the next task force ready.
  • Option: Another WCAG 2.1 model could be by milestone date: whatever work (from all the task forces) is ready by a milestone date could be included in that update (WCAG 2.1, 2.2, etc). How often should these updates occur? 6 months is too short, 3 years is too long.
  • WCAG 3.0 (or whatever name) is a later project that could include ATAG and UAAG. Planning needs to begin in parallel to Task Force work.
  • There is a need to coordinate more between task forces so WCAG WG can also work on WCAG 3
  • There are concerns with timing of announcements and the impact on EU legislation

Related Documents