-
Notifications
You must be signed in to change notification settings - Fork 34
Home
This wiki provides project planning milestones for the W3C Accessibility Guidelines (WCAG) 3.0.
- WCAG 3.0 Maturity Labelling Process - decision policy for approving and publishing parts of WCAG3
- WCAG 3.0 Schedule - spreadsheet of the milestones
- WCAG3 Editors Draft
- WCAG3 Latest Working Draft
- Github repository - the main Github repository for WCAG3 documents and archival prototypes
- This Wiki - the information for each milestone including point of contact, IRC channel, minutes, issues, research, key decisions, and archival documents
- Projects
- Foundational Work - basic topics: requirements, structure, and conformance
- Scoring - measurement, critical errors, weighting
- Content Creation - migrating WCAG 2 content and writing new guidelines
- Guidelines - placeholder groupings of WCAG 2.1 success criteria for planning purposes.
- Projects are divided into milestones and organized by stage in the process.
- "Milestones" are a selection of topics that need to be completed in a specific order.
- Milestones provide a way to organize our work but are not permanent. Milestones may be added, closed, reorganized, or renamed when needed.
- Each Milestone has an associated wiki page, irc channel or Topic name, milestone label in github to group issues, and row on the schedule. These should all have the same name.
Foundational Work Github Project - Information pages for each of the following milestones:
- Accessibility Supported
- Alternate Versions
- ATAG (How and when to include this)
- Continued Improvement
- Equity
- Evaluating proposed solutions (QA)
- Policy Uptake
- Reporting
- Representative Sampling
- Requirements
- Scoping Paths/Tasks/Workflows/Components/Views
- Structure and terminology
- Test types and terminology
- Third Party Content
- Transition Plan
- UAAG (How and when to include this)
Scoring Github Project - Information pages for each of the following milestones:
- Measurement: Pass/Fail, Scale, Points, Percentage
- Scoring in Aggregate
- Addressing Gaps
Content Creation and Migration Github Project - Information pages for each of the following milestones:
- Placeholder guidelines
- Rework Methods
- Writing Process
- Reduce ambiguity in Outcomes (new template, definition, measure, interrater reliability)
- Tagging
Guidelines Github Project - Information pages for each of the following milestones: Note that these are placeholder guidelines. They were developed by the Silver Task Force in 2018 based on common user needs of WCAG 2.1 success criteria. They have not been approved or finalized. They are included for project planning purposes.
- Additional Content
- Alternatives for Audio
- Alternatives for Video
- Assistive Technology Access
- Augment Text
- Avoid Interruptions
- Avoid Movement
- Captions
- Clear Words
- Color Contrast
- Complimentary Information Conveyed
- Consistent Paths and Interactions
- Context of Interactions
- Error Prevention
- Give Users Time
- In-context Navigation
- Input Mechanisms
- Interaction Customizations
- Motor Control
- Multi-part Interactions
- Multiple Modalities
- Multiple Ways
- Name-based Interactions
- Physical Reactions
- Predictable Context
- Structured Content
- Switching Input Modalities
- Text Alternatives
- Text Rendering Customization
- Use Technologies Correctly
- Viewport Rendering Customization
- Visual Contrast of Text
WCAG 3 subgroups are small and temporary groups within the Accessibility Guidelines Working Group (AGWG), which are set up to work on proposals for specific topics or issues. Each subgroup has 4 to 6 members, including a facilitator, and will work for 8 weeks to come up with a proposal for AGWG. For details, read the subgroup handbook.
WCAG3 is a project of the W3C Accessibility Guidelines Working Group (AGWG). Research and prototyping was done by the Silver Task Force. Archival and additional material for this project can be found on the Silver wiki.
This Wiki page is edited by participants of the Accessibility Guidelines Working Group. It does not necessarily represent consensus and it may have incorrect information or information that is not supported by other Working Group participants, WAI, or W3C. It may also have some very useful information.