WCAG 3: The True Story! CSUN 2025 Slides are
Description: WCAG 3: The True Story! CSUN 2025 Slides are available to download at: https:www.w3.org2025TalksCSUN2025-CSUN-wcag3-update.pptx Session description Work continues on the W3C Content Accessibility Guidelines (WCAG) 3. The Accessibility
Related Topics
Download Presentation
"WCAG 3: The True Story! CSUN 2025 Slides are" is the property of its rightful owner. Permission is granted to download and print the materials on this website for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
Presentation Transcript
slide1. WCAG 3: The True Story! CSUN 2025 Slides are available to download at: https://www.w3.org/2025/Talks/CSUN/2025-CSUN-wcag3-update.pptx<br>
slide2. Session description Work continues on the W3C Content Accessibility Guidelines (WCAG) 3.
The Accessibility Guidelines Working Group Chairs and Team Contact will give you the low down on the pit falls and progress on the latest update to the internationally recognized WCAG 3.<br>
slide3. Agenda Introductions
Feedback and questions
Maturity levels
Achievements and planning
Current status
Research
Contributing to the work
Questions<br>
slide4. Introductions<br>
slide5. Feedback and questions We encourage questions
There will be time at the end
Raise hand or use QR code to Slido to ask questions there
Visit sli.do, code: 3873734<br>
slide6. Maturity levels<br>
slide7. Maturity levels - overview Content in WCAG 3.0 will evolve over time
At each step, the content becomes increasingly detailed and definite
Maturity levels are used to indicate at what stage any piece of content is at
The level of maturity indicates:
Where in the development process the content is,
Whether the content is ready for experimental adoption
What kind of feedback we are looking for 7<br>
slide8. Maturity levels - Placeholder Identifies needs and possible directions
Likelihood to change: Definite
Feedback Needed: Not included in drafts, and no feedback is needed on placeholder content 8<br>
slide9. Maturity levels - Exploratory Exploring what direction to take with this content
Likelihood to change: Very likely, lacks details
Feedback Needed: About the proposed direction 9<br>
slide10. Maturity levels - Developing Working out details and address open questions
Likelihood to change: Details likely to change, overall direction unlikely to change
Feedback Needed: Focused on ensuring the sections are usable and reasonable in a broad sense 10<br>
slide11. Maturity levels - Refining Consensus reached and entering broad public review and experimental adoption
Likelihood to change: Details may change, overall direction unlikely to change
Feedback Needed: Focused on the feasibility of testing and implementing 11<br>
slide12. Maturity levels - Mature Ready for final standard
Likelihood to change: Unlikely to change
Feedback Needed: Focused on edge case scenarios the working group may not have anticipated 12<br>
slide13. Maturity levels - examples 13<br>
slide14. Achievements and planning<br>
slide15. 2024 Achievements Created a list of exploratory guidelines
Selected 2 guidelines to work through to maturing
Narrowed down the conformance approach
Created an approach to accessibility supported<br>
slide16. Plan for 2025 (1 of 4) Quarter 1: January - March
Continue maturing 2 select guidelines
Continue developing all guidelines
Continue discussion of core issues
Begin review and address of public comments
Retrospective (CSUN) 16<br>
slide17. Plan for 2025 (2 of 4) Quarter 2: April - June
Continue work on guidelines
Continue discussion of core issues
Continue review and address of public comments
Publish initial developmental list of outcomes (at end) 17<br>
slide18. Plan for 2025 (3 of 4) Continue subgroup work on 2 maturing guidelines
Finalize conformance model proposal
Select guidance for WCAG 3.0 (evidence based)
Explore what can be reused from WCAG 2
Map WCAG 2 to WCAG 3
Develop schedule
Continue review and address of public comments 18<br>
slide19. Plan for 2025 (4 of 4) Quarter 4: October - December
Recharter
Publish developing conformance model(s)
Publish updated WCAG 3 Explainer
Update the wiki with a data driven schedule for WCAG 3 19<br>
slide20. Current status<br>
slide21. Structure Guidelines written as plain language outcome statements (normative)
Foundational Requirements (normative)
How to Documents (informative)
Methods (informative)
Supplemental Requirements (normative)
How to Documents (informative)
Methods (informative)
Best Practices (informative)
Assertions (normative)
How to Documents (informative) 21<br>
slide22. Example guideline Guideline: Users have equivalent alternatives for images.
Foundational requirements:
Decorative images are programmatically hidden.
Equivalent text alternative is available for each image that conveys content.
Supplemental requirements:
The role and importance of the image is programmatically indicated
Assertions:
Text alternatives follow an organizational style guide. 22<br>
slide23. Applicability "tree" (not settled) Make it clear which foundational requirement(s) apply to a given scenario.
Allow for user-agents to fulfil requirements.
Allow for different technologies to have different requirements.
Example, for each image:
Decorative – requirement 1
Content image described by the user-agent - requirement 2
Content image described by the author - requirement 2 23<br>
slide24. Example applicability tree (drafty) For each image:
1. Would removing the image impact how people understand the page?
No. The decorative image is programmatically hidden. Pass.
Yes, continue.
2. Is the image presented in a way that is available to user agents and assistive technology?
Yes, image must meet Image is programmatically determinable AND the accessibility support set meets Equivalent text alternative is available for image that conveys content. Pass.
No, continue.
3. Is an equivalent text alternative available for the image?
Yes, image must meet Equivalent text alternative is available for image that conveys content. Pass.
No, fail. 24<br>
slide25. Conformance Conformance will be based on a combination of:
All of the Foundational Requirements
Some subset of:
Supplemental Requirements
Assertions
Options for selecting the subset:
Sets of Supplemental Requirements and Assertions - (When content affects health, then…)
Number of Points
% of Supplemental Requirements and Assertions 25<br>
slide26. Example of conformance – Not settled All foundational requirements and some proportion of supplemental & assertions to reach minimum and higher conformance levels. Foundational Requirements Supplemental Requirements and Assertions Bronze Silver Gold 26<br>
slide27. Accessibility supported Similar concept to the WCAG 2 Accessibility Supported
How does an author know that a technique will work in practice?
“Accessibility support set”: A defined set of user-agents / AT / plugins.
WCAG3 will have an (informatively defined) “accessibility support set” for testing our own methods.
At foundational level: You can rely on the provided methods/techniques.
At higher conformance levels: You may need to define your own set.
Region specific
Context specific 27<br>
slide28. Research<br>
slide29. Research As we write guidance, we find areas that we have some but not enough evidence to support a standard.
We are creating research statements for these and would like to coordinate with researchers to get answers. 29<br>
slide30. Examples of research gaps Evaluating the color contrast algorithm
Needs beyond existing standards to support people who use voice input
Information about the effects of spacing on reading in non-Roman alphabets 30<br>
slide31. Supporting research We need your help
Not just academic research
Find out more about the research needed at: https://github.com/w3c/wcag3/wiki/Evidence-and-Research-Needed-WCAG-3
If interested, please contact the chairs at group-ag-chairs@w3.org 31<br>
slide32. Contributing to the work<br>
slide33. Feedback on WCAG 3 - Github File an issue
https://github.com/w3c/wcag3/issues/new
Participate in discussions
https://github.com/w3c/wcag3/discussions
Send email to public-agwg-comments@w3.orgÂ
Please file one issue per change 33<br>
slide34. Feedback on WCAG 3 - email Send email to public-agwg-comments@w3.orgÂ
Please send one email per change 34<br>
slide35. Writing the standard WCAG 3 is created by members of the Accessibility Guidelines Working Group in the W3C
W3C Member organizations can simply join the group and start contributing
Invited Experts are individuals who are not employed by member organizations who contribute their expertise and time to the work
Find out more at w3.org/membership 35<br>
slide36. Questions Visit sli.do, code: 3873734<br>
slide37. Thank you Slides are available to download at: https://www.w3.org/2025/Talks/CSUN/2025-CSUN-wcag3-update.pptx<br>
slide38. [Bonus content] Differences with WCAG 2 More Requirements than Success Criteria BUT Requirements are more granular and understandable
Conditional Methods - Requirements may apply differently based on defined situations such as language or alphabet<br>
slide2. Session description Work continues on the W3C Content Accessibility Guidelines (WCAG) 3.
The Accessibility Guidelines Working Group Chairs and Team Contact will give you the low down on the pit falls and progress on the latest update to the internationally recognized WCAG 3.<br>
slide3. Agenda Introductions
Feedback and questions
Maturity levels
Achievements and planning
Current status
Research
Contributing to the work
Questions<br>
slide4. Introductions<br>
slide5. Feedback and questions We encourage questions
There will be time at the end
Raise hand or use QR code to Slido to ask questions there
Visit sli.do, code: 3873734<br>
slide6. Maturity levels<br>
slide7. Maturity levels - overview Content in WCAG 3.0 will evolve over time
At each step, the content becomes increasingly detailed and definite
Maturity levels are used to indicate at what stage any piece of content is at
The level of maturity indicates:
Where in the development process the content is,
Whether the content is ready for experimental adoption
What kind of feedback we are looking for 7<br>
slide8. Maturity levels - Placeholder Identifies needs and possible directions
Likelihood to change: Definite
Feedback Needed: Not included in drafts, and no feedback is needed on placeholder content 8<br>
slide9. Maturity levels - Exploratory Exploring what direction to take with this content
Likelihood to change: Very likely, lacks details
Feedback Needed: About the proposed direction 9<br>
slide10. Maturity levels - Developing Working out details and address open questions
Likelihood to change: Details likely to change, overall direction unlikely to change
Feedback Needed: Focused on ensuring the sections are usable and reasonable in a broad sense 10<br>
slide11. Maturity levels - Refining Consensus reached and entering broad public review and experimental adoption
Likelihood to change: Details may change, overall direction unlikely to change
Feedback Needed: Focused on the feasibility of testing and implementing 11<br>
slide12. Maturity levels - Mature Ready for final standard
Likelihood to change: Unlikely to change
Feedback Needed: Focused on edge case scenarios the working group may not have anticipated 12<br>
slide13. Maturity levels - examples 13<br>
slide14. Achievements and planning<br>
slide15. 2024 Achievements Created a list of exploratory guidelines
Selected 2 guidelines to work through to maturing
Narrowed down the conformance approach
Created an approach to accessibility supported<br>
slide16. Plan for 2025 (1 of 4) Quarter 1: January - March
Continue maturing 2 select guidelines
Continue developing all guidelines
Continue discussion of core issues
Begin review and address of public comments
Retrospective (CSUN) 16<br>
slide17. Plan for 2025 (2 of 4) Quarter 2: April - June
Continue work on guidelines
Continue discussion of core issues
Continue review and address of public comments
Publish initial developmental list of outcomes (at end) 17<br>
slide18. Plan for 2025 (3 of 4) Continue subgroup work on 2 maturing guidelines
Finalize conformance model proposal
Select guidance for WCAG 3.0 (evidence based)
Explore what can be reused from WCAG 2
Map WCAG 2 to WCAG 3
Develop schedule
Continue review and address of public comments 18<br>
slide19. Plan for 2025 (4 of 4) Quarter 4: October - December
Recharter
Publish developing conformance model(s)
Publish updated WCAG 3 Explainer
Update the wiki with a data driven schedule for WCAG 3 19<br>
slide20. Current status<br>
slide21. Structure Guidelines written as plain language outcome statements (normative)
Foundational Requirements (normative)
How to Documents (informative)
Methods (informative)
Supplemental Requirements (normative)
How to Documents (informative)
Methods (informative)
Best Practices (informative)
Assertions (normative)
How to Documents (informative) 21<br>
slide22. Example guideline Guideline: Users have equivalent alternatives for images.
Foundational requirements:
Decorative images are programmatically hidden.
Equivalent text alternative is available for each image that conveys content.
Supplemental requirements:
The role and importance of the image is programmatically indicated
Assertions:
Text alternatives follow an organizational style guide. 22<br>
slide23. Applicability "tree" (not settled) Make it clear which foundational requirement(s) apply to a given scenario.
Allow for user-agents to fulfil requirements.
Allow for different technologies to have different requirements.
Example, for each image:
Decorative – requirement 1
Content image described by the user-agent - requirement 2
Content image described by the author - requirement 2 23<br>
slide24. Example applicability tree (drafty) For each image:
1. Would removing the image impact how people understand the page?
No. The decorative image is programmatically hidden. Pass.
Yes, continue.
2. Is the image presented in a way that is available to user agents and assistive technology?
Yes, image must meet Image is programmatically determinable AND the accessibility support set meets Equivalent text alternative is available for image that conveys content. Pass.
No, continue.
3. Is an equivalent text alternative available for the image?
Yes, image must meet Equivalent text alternative is available for image that conveys content. Pass.
No, fail. 24<br>
slide25. Conformance Conformance will be based on a combination of:
All of the Foundational Requirements
Some subset of:
Supplemental Requirements
Assertions
Options for selecting the subset:
Sets of Supplemental Requirements and Assertions - (When content affects health, then…)
Number of Points
% of Supplemental Requirements and Assertions 25<br>
slide26. Example of conformance – Not settled All foundational requirements and some proportion of supplemental & assertions to reach minimum and higher conformance levels. Foundational Requirements Supplemental Requirements and Assertions Bronze Silver Gold 26<br>
slide27. Accessibility supported Similar concept to the WCAG 2 Accessibility Supported
How does an author know that a technique will work in practice?
“Accessibility support set”: A defined set of user-agents / AT / plugins.
WCAG3 will have an (informatively defined) “accessibility support set” for testing our own methods.
At foundational level: You can rely on the provided methods/techniques.
At higher conformance levels: You may need to define your own set.
Region specific
Context specific 27<br>
slide28. Research<br>
slide29. Research As we write guidance, we find areas that we have some but not enough evidence to support a standard.
We are creating research statements for these and would like to coordinate with researchers to get answers. 29<br>
slide30. Examples of research gaps Evaluating the color contrast algorithm
Needs beyond existing standards to support people who use voice input
Information about the effects of spacing on reading in non-Roman alphabets 30<br>
slide31. Supporting research We need your help
Not just academic research
Find out more about the research needed at: https://github.com/w3c/wcag3/wiki/Evidence-and-Research-Needed-WCAG-3
If interested, please contact the chairs at group-ag-chairs@w3.org 31<br>
slide32. Contributing to the work<br>
slide33. Feedback on WCAG 3 - Github File an issue
https://github.com/w3c/wcag3/issues/new
Participate in discussions
https://github.com/w3c/wcag3/discussions
Send email to public-agwg-comments@w3.orgÂ
Please file one issue per change 33<br>
slide34. Feedback on WCAG 3 - email Send email to public-agwg-comments@w3.orgÂ
Please send one email per change 34<br>
slide35. Writing the standard WCAG 3 is created by members of the Accessibility Guidelines Working Group in the W3C
W3C Member organizations can simply join the group and start contributing
Invited Experts are individuals who are not employed by member organizations who contribute their expertise and time to the work
Find out more at w3.org/membership 35<br>
slide36. Questions Visit sli.do, code: 3873734<br>
slide37. Thank you Slides are available to download at: https://www.w3.org/2025/Talks/CSUN/2025-CSUN-wcag3-update.pptx<br>
slide38. [Bonus content] Differences with WCAG 2 More Requirements than Success Criteria BUT Requirements are more granular and understandable
Conditional Methods - Requirements may apply differently based on defined situations such as language or alphabet<br>