WCAG21updates
This page tracks updates to WAI Resources for WCAG 2.1.
Status
I think I've got all the main pages listed below. If anything is missing, please let me know. ~Shawn~
In Sept 2018, we decided to change "WCAG 2" & "WCAG 2.0" to "WCAG" in most places. That still needs to be done in most places.
Note: Links go to the GitHub versions, not the published version. They should mostly be in synch.
WAI (Staff) resources
To Do
- [done? SLH asked MC] QuickRef - still needs Techniques from Michael, and there's an open issue (which I think Eric fixed by hand and cloesd; however, eventually need to get it fixed in the generated json). [this is actually an EOWG & AG WG Resource, but I'm leaving it at the top of this list so it doesn't get forgotten for now :-]'
- Address Instructions for Commenting issue
- "2.0" -> "2" in images such as WCAG docs (which is used in https://w3c.github.io/wai-intro-wcag/standards-guidelines/wcag/docs/)
Done
- WCAG 2 FAQ (August 2020)
- * Conformance logos pages: Adding WCAG Conformance Logos, A, AA, AAA (August 2020)
- Mobile Accessibility at W3C
- WCAG 2 Translations
- WCAG 2 Documents
- WCAG2ICT Overview has this new wording - that Judy might want to review:
Note: WCAG2ICT is still relevant for future versions of WCAG 2. For example, WCAG 2.1 does not change the requirements of WCAG 2.0 that are addressed in WCAG2ICT; WCAG 2.1 adds additional requirements. W3C may update WCAG2ICT in the future to add the additional requirements from later versions of WCAG 2.
- Changes are in place for rollout 5 June:
- WCAG Overview
- WCAG 2 FAQ
- W3C Accessibility Standards Overview
- What's New in WCAG 2.1 - Shawn sent draft to WAI staff, AG WG TFs, EOWG on Friday 25 May
- WCAG 2 at a Glance - Shawn sent proposed revision and addition to EOWG and AG WG for review on Monday 28 May
None Needed
- Overview pages (7): Planning and Policies Overview, Design and Develop Overview, Evaluating Web Accessibility Overview, Teach and Advocate Overview, Evaluation Tools Overview, Conformance Evaluation Overview, WCAG-EM Overview
- Essential Components
- Older Users and Web Accessibility: Meeting the Needs of Ageing Web Users (unless update sub-page, then update that link from 2.0->2)
- Overview of “Web Accessibility for Older Users: A Literature Review”
Not Updating
EOWG resources
Need to Do - EO
To be done with other projects:
- How People with Disabilities Use the Web 3 sub-pages — revisions in progress Q3 2020
- Easy Checks — major revision planned – consider additions to existing checks and new checks
- Training suite - will be updated with WAI-Guide Curricula project
To be prioritized:
- Perspectives Videos — proposed addition to Colors with Good Contrast, proposed addition to keyboard, suggestions from F2F in this google doc
- Tips for Getting Started [Writing, Designing, Developing] — analysis and suggestions from F2F in this google doc
- Tutorials
Done - EO
- WCAG-EM Report Tool (January 2020)
- Accessibility Principles (Thanks Shadi!)
- QuickRef — Tags for new 2.1 SCs (Thanks Laura, Becky, Sharron, Eric!)
- Tips for Getting Started Pages — Change links from 2.0 to 2.1. (Thanks Laura!)
- Easy Checks — Update links & WCAG 2.0->WCAG (Thanks Laura!)
- Developing Organizational Policies on Web Accessibility -- updates
- Introduction to Web Accessibility -- diff
- Web Accessibility First Aid: Approaches for Interim Repairs -- diff
- Implement -- diff
- Plan -- diff
- Involving Users in Web Projects -- diff
- Tips - Writing -- diff
- Tips - Developing -- diff
- Tips - Designing -- diff
- Template for Accessibility Evaluation Reports -- diff
- Using Combined Expertise to Evaluate Web Accessibility -- diff
- How to Make Your Presentations Accessible to All -- diff
- Example Outlines for Web Accessibility Presentations -- diff
- Example Outline for a Web Accessibility Workshop -- diff note: more to do after 2.1 published - listed above
- Topics for Web Accessibility Presentations and Training -- diff note: more to do after 2.1 published - listed above
None Needed - EO
- Selecting Web Accessibility Evaluation Tools
- Planning and Managing Web Accessibility
- Initiate
- Sustain
- Accessibility, Usability, and Inclusion
- Involving Users in Evaluating Web Accessibility
Future: Includes "2.1" so probably need to update if 2.2
- Plan (EOWG Resource)
- Developing Organizational Policies on Web Accessibility (EOWG Resource)
- Template for Accessibility Evaluation Reports (EOWG Resource)
- Using Combined Expertise to Evaluate Web Accessibility (EOWG Resource)
- ... several more above that are to be done after 2.1 published ...
Archived Info
Open Issue: WCAG 2.x
Sept 2018 update: WAI Team and EOWG agreed WCAG 2.0 & WCAG 2 -> WCAG (WAI minutes, EOWG minutes)
Issue description: In many, many places we had "WCAG 2.0". In almost all cases, that now applies to both WCAG 2.0 and WCAG 2.1. How do we handle that? In June we changed most instances of "WCAG 2.0" to "WCAG 2". Since WCAG 1.0 will be formally superseded soon, it seems 2 is not necessary. Also, it wasn't clear enough to some people (per below).
- Examples where 2.0 hasn't been changed yet: Accessibility Principles sub-headings.
- Note: There are a few places where we will always include a specific version number, for example, in "WCAG 2.0 is also an ISO standard: ISO/IEC 40500", in conformance statements, and in most example policies.
Proposal
Change most references from "WCAG 2.0" and "WCAG 2" to just "WCAG".
We could still clarify "WCAG 2.0 and WCAG 2.1" in text when we think it's needed and/or more useful than clutter.
Examples: Tips for Getting Started pages have sub-headings just "WCAG": Write, Design, Develop
Pro: The simplest and probably least confusing overall.
Note: We would want to make sure that people who only need to meet 2.0 can easily tell what is 2.0 and not be cluttered or confused by 2.1 requirements. This will mostly apply to the Quick Ref and AG documents, rather than most EOWG documents.
Options
1. "WCAG" <--proposed
(info above)
2. "WCAG 2"
Examples: Titles: "How to Meet WCAG 2 (Quick Reference)", "WCAG 2 Translations"
Con/One perspective: "I find this labeling a bit confusing. WCAG 2 could cause confusion, looks as though 2.1 is not included in 2" GitHub569 – Eric thinks that stems from years of using WCAG 2 as a synonym or short form for WCAG 2.0. Maybe we could say (in certain key descriptions) “WCAG 2 (including 2.1)” to help users unlearn.
3. "WCAG 2.0 and WCAG 2.1" or "WCAG 2.0 and 2.1"
Con: Too wordy.
4. “WCAG 2.x”
Maybe a bit too programmer jargon-y, I wonder if it is understood by a wider audience. {Eric}
5. “WCAG 2.0/2.1”
This would be explicit, but wouldn’t include other WCAG 2.x revisions in the future. Also a little bit harder to read. {Eric}
Con: A little bit more cognitively and visually complex.
Related proposal
In many EOWG documents we point to specific Understanding pages, and sometimes techniques. I think that we want to point to the Understanding 2.1 docs. However, someone only doing 2.0 might notice the /WCAG21/ URI and question if what they're looking at applies to 2.0. Therefore, I {Shawn} propose that near the top of each Understanding and Techniques page, it includes either:
- Applies to WCAG 2.0 and 2.1
- Applies to WCAG 2.1
There is also consideration about changing the URI to /WCAG2/ without a version number.