Example Scenarios for WCAG Conformance

Conformance Options Subgroup, 25 March 2022

w3.org/WAI/GL/task-forces/silver/wiki/Substantial_Conformance/Example_Scenarios

Purpose

• Describe scenarios in which conforming to WCAG could present challenges
• Help develop a shared understanding of such situations across AGWG/WAI
• Outline potential approaches to help mitigate such situations, including through:
• Technical standards, in particular WCAG 3 (but possibly also ATAG and UAAG)
• Accompanying technical guidance, such as Understanding and Techniques docs
• Policies adopting WCAG (WAI does not develop policies but develops guidance)
• Contribute to the development of current and future AGWG/WAI resources

Attention!

• This is a very early draft, and none of the content is set in stone
• Lots of wording needs scrubbing and does not yet have consensus
• It is not intended to be an exhaustive list of all possible situations
• We are looking for your feedback on the usefulness of this work
• Also, are there situations we have missed? Considerations to add?
• We welcome all comments, suggestions, and active contributions

Bugs and other issues of oversight occur in content

• website with many content authors
• application with high degree of complexity

​

When large volumes of content are accumulating too rapidly to make fully conforming

• content being generated by users
• content being generated automatically

When making large volumes of content fully conform is not achievable immediately

• making content conform after acquisition
• adapting content to changed requirements
• making content conform requires manual intervention
• making content conform requires additional processes

​

Content provider does not own or directly control the content

• website that allows users to create their own websites
• portal that aggregates content from different sources

​

When content provider have dependencies on other services

• service using a payment service
• embedding social media channels
• relying on content management systems (CMS)

​

Current limitations in providing the same level of conformance for live content

• reduced quality of captions in live content

Current limitations in making some types of content fully conform

• technology with limited support for accessibility (e.g. immersive environments)
• sensory experiences cannot be easily translated
• lack of support by assistive technologies

When content is rarely used, if ever

• outdated content that is rarely used
• current content that is rarely used

​

Content is experimental for all users, including people with disabilities

• on-going research and development of accessibility features
• prioritizing speed-to-market over product stability
• product demo with limited functionality and accessibility

Not all accessibility requirements are always applicable to all content

• content provided to a limited group of users only
• content accessed by known set of user technologies

​

Small businesses face unique challenges

• business has limited expertise
• business has limited resources

Thank You

Please get in touch with feedback and questions!

​

w3.org/WAI/GL/task-forces/silver/wiki/Substantial_Conformance/Example_Scenarios

​

Group: Silver Conformance Options Subgroup

Leadership: Janina Sajka and Jeanne Spellman

Lead Editor: Shadi Abou-Zahra