The Task Force had previously reached agreement and implemented changes to address the public comment in Issue 77 - Including WCAG supplements and Making Content Usable for People with Cognitive and Learning Disabilities. However, two further comments from the issue author indicate a desire for us to adjust what we included in WCAG2ICT.

Review pull request 309 and see the adjusted content in-context in the document section Guidance in this Document starting the 2nd paragraph after Note 1. Note that this proposal intends to move the references to these documents from the Document Overview section to the Guidance in this Document section, and it adds a resource I recently learned about for mobile (which is beginning the process of being updated for WCAG 2.2).

Also review the following additional proposed TF answer for Issue 77:

Further adjustments have been made to the language and location of documents that are referred to by WCAG2ICT, including "Making Content Usable..." that will hopefully address your concerns in the additional comments (above) in this issue. Note that the WCAG2ICT Task Force needs to remain mindful that this document is not meant to provide techniques for meeting or going beyond WCAG. Its content is limited to interpreting WCAG criteria in a non-web context. Any guidance beyond that should instead be included in or referenced by other documents specifically focused on implementing accessibility requirements in non-web technologies. We will continue to mention this resource, but in the context we feel is appropriate for our scope of work.

Here is the exact language that the WCAG2ICT Task Force agreed on which can be found in the section titled Guidance in this Document starting the 2nd paragraph after Note 1.

@@insert final text here@@

Indicate whether the proposed change and answer is sufficient and note any potential edits or alternate proposals. Also note whether you agree with the location where these references were moved or whether you think they should be located somewhere else in the document, and where they should go.

Summary

Details

This is more of a poll, rather than a review of proposed content. Read and understand Add info/content on the WCAG exemptions in regulatory work. This was opened due to the discussion linked in the issue. I'd like for the TF to think about and discuss whether document changes should be made to address this issue, or we simply avoid this topic in the document.

Do you think we should add content into WCAG2CIT to explain that there are excepted criteria in 508 and the EN 301 549 for non-web documents and software (due to the way WCAG2ICT applied/interpreted "sets of web pages" to be "sets of documents or software programs"? Explain the reasoning you have for your answer. If you think there should be content, where in the document should this go? (e.g. in the individual criteria, in another existing section, or in a new section)

If there is consensus that content is needed in WCAG2ICT, indicate whether you are willing to draft (or help draft) the content.

Summary

Details

This survey question is also a poll, rather than a review of proposed content. Read and understand Issue 243 - Revisit TF decision on inclusion of WCAG intent sections. This was opened as we received feedback from the AG WG that including the intent added a lot of content to WCAG2ICT making it more difficult to read and review. Do you think this should be removed from the document? Provide your reasoning as to why or why not. Note that the answers indicate if that should be done now (prior to the release of the next public draft) or whether we wait until the final WCAG2ICT note is published.

Summary

Details