This repository was archived by the owner on Aug 20, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 265
WCAG 3 Intro page – Requirements Analysis
shawn_slh edited this page Jan 15, 2021
·
1 revision
Primary:
- Provide a single pointer for info about WCAG 3 (that can link to other info, as appropriate), and get this link established in the wild as the go-to place for the latest info on WCAG 3
- Provide a very simple introduction to the content of this draft
- Especially for those who know WCAG 2, provide a very simple description of the structure and conformance model, to help them make sense of the significant differences
- Guide the reactions and discussions in the wild to be appropriate based on the actual situation – e.g., this is far from “set in stone”
- Make it very clear that this is an incomplete draft with
- initial proposal/option for structure and conformance model
- only a very few actual guidelines, that are still very drafty
- the goal of getting input on these options (not even proposing them as nearly done yet)
- Guide reviewers to understand the background so that they provide useful input
Also:
- Reassure that WCAG 3 is at least a couple years from being completed, and even more from potentially being required – and, later when WCAG 3 is more complete, WAI will provide guidance for those currently using WCAG 2, to understand and potentially use WCAG 3
- For those who know “Silver”, make the connection from Silver to WCAG 3
- Communicate the goals and benefits of WCAG 3, e.g.:
- address more needs of people with disabilities, especially cognitive
- be more easily usable by a broader range of audiences
- cover a broader scope of web-based technologies
- be written in plainer language
- provide a conformance model with a more nuanced understanding of the accessibility of a website, app, or product