W3C home > Mailing lists > Public > public-wcag2ict-tf@w3.org > September 2012

ACTION 65: Gather incoming comments to M376 team wrt closed functionality in the WCAG2ICT domain

From: Michael Pluke <Mike.Pluke@castle-consult.com>
Date: Wed, 26 Sep 2012 11:49:11 -0400
To: "public-wcag2ict-tf@w3.org" <public-wcag2ict-tf@w3.org>
Message-ID: <5735ED0D92A3E6469F161EB41E7C28A81D5F84AAA2@MAILR001.mail.lan>
Here is the very rough cut-and-paste of the incoming comments to M376 from various sources regarding the proposed closed functionality exceptions for WCAG 2.0 applied to software. This is unsorted and repetitious - so apologies for the presentation.

Add the following text to this provision Or incorporated into the table.

For the following specified types of closed functionality, ICT shall conform to 5.1 provisions specified below instead of  the following WCAG 2.0

1)  Where ICT is closed to enlargement features, WCAG 2.0 Provisions 1.4.4 (Resize text)  is replaced by 5.1.5 (Functionality Closed to Text Enlargement).

2)  Where ICT is closed to keyboards and keyboard interfaces, WCAG 2.0 provision 2.1.1 Keyboard is replaced by  XXX@@@@   Tactilely Locatable Controls.  (8.4.1 operable part identification)

3) Where ICT provides its own speech output for non-visual access, WCAG 2.0 success criteria 3.1.1 {Language of Page) and 3.1.2 (Language of Parts)  are replaced by Correct Pronunciation.

5) WCAG 2.0 Provision 4.1.1 Parsing is replaced by compatibility of the content with the provisions of 5.1 (Closed Functionality) taken together.

Add the following exceptions to table 5:

1.1.1. Where ICT is closed to screen reading, addresses the same needs.

1.3.1. There is a need to add a new requirement in 5.1.x that requires non-visual access to Information, structure, and relationships conveyed through presentation.

1.3.2. This SC does not need a replacement in closed functionality as it is the closed ICT who provides the reading order...

3.1.2. Where ICT provides its own speech output: "Spoken languages" addresses the same needs.

4.1.1. This SC does not need a replacement in closed functionality.

4.1.2 This SC does not need a replacement in closed functionality.


Add the following checkpoints to the table:
1.3.1, 1.3.2, 1.4.2, 3.1.2, 4.1.1, 4.1.2 because there's no AT to use the programmatic information.
Add the following checkpoints to the table, and add notes for why or when these don't apply.
2.4.1, 2.4.2, 2.1.1, 2.1.2
Please specify that closed functionality of ICT do not need to programmatically expose the text alternative per the definition of WCAG 2.0.  The corresponding non-text content should be exposed to users in alternate format instead.
Please exclude WCAG 2.0 1.3.1.

Please exclude WCAG 2.0 1.3.2

Please exclude WCAG 2.0 1.4.2.
Please exclude 2.1.1 and 2.1.2 in case of closed functionality of ICT without keyboard.

Please exclude 2.4.2 for closed functionality of ICT where multitasking is not permitted.

Please exclude 2.4.7 in cases where keyboard is not used for navigational purposes.

Please exclude WCAG 2.0 3.1.2.

Please exclude WCAG 2.0 4.1.1 & 4.1.2
Received on Wednesday, 26 September 2012 15:50:20 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:17:46 UTC