AG WG Review: WCAG2ICT Guidance for Products with Closed Functionality

maryjom commented 4 months ago

Summary

The Task Force has updated and refreshed all of the guidance regarding products with closed functionality with more details about applying WCAG to non-web software where the system is closed to assistive technology or has more limited platform capabilities. We have defined two new key terms, updated the general guidance on closed functionality, as well as updated the section SC Problematic for Closed Functionality. All of the success criteria in WCAG 2.2 were analyzed to produce this content.

Maturity Level

Refining

Action Needed

Review content (See Content for Review section below for details.)
Use the thumbs up and thumbs down icons to indicate agreement or disagreement with various comments. Do not add comments to simply support other comments.
Note any suggested edits for improvement and/or reasoning either in a comment on this issue or by creating a PR on the WCAG2ICT document.
- The Key terms "closed functionality" and "menu-driven interface" are found in the file: key-terms.md
- Comments on Closed Functionality is found in the file: closed-functionality.md
- Success Criteria Problematic for Closed Functionality is found in the file: success-criteria-problematic-for-closed-functionality.md

Background information

Once finalized, this new WCAG2ICT Note will replace the 2013 Note, and it covers all three WCAG versions (2.0, 2.1, or 2.2). This is important as different jurisdictions are using different versions of WCAG for the accessibility of information and communication technology.

Content for Review

Definition of closed functionality.
Definition of menu-driven interface
Comments on Closed Functionality
Success Criteria Problematic for Closed Functionality

Reference Material

None

detlevhfischer commented 4 months ago

@maryjom Under "action needed", it would help to include a link to the content to be reviewed.

maryjom commented 4 months ago

@maryjom Under "action needed", it would help to include a link to the content to be reviewed.

I am following the AG WG template which has the links to the content to be reviewed listed under the "Content for Review" part (2 sections below "action needed").

alastc commented 4 months ago

Question that I'm not sure about regarding menu-driven interfaces: Does / should that include voice input? E.g. a telephone menu over audio where you say "two" instead of pressing the button.

maryjom commented 4 months ago

Question that I'm not sure about regarding menu-driven interfaces: Does / should that include voice input? E.g. a telephone menu over audio where you say "two" instead of pressing the button.

I guess it could potentially include Interactive Voice Response (IVR) systems. However, the only place WCAG2ICT uses the term is with regard to 2.4.2 Page Titled - to indicate that if the ICT has a menu-driven interface there is no need for a page title.

Oops...didn't mean to close the issue when posting this comment...reopened it.

maryjom commented 3 months ago

Closing this issue, since the AG WG review is done. WCAG2ICT document is now in CfC to publish that ends on 1 July.

w3c / wcag2ict