RE: WCAG resolutions from today's meeting

Excellent!

From: Andi Snow-Weaver [mailto:andisnow@us.ibm.com]
Sent: Thursday, July 12, 2012 5:08 PM
To: public-wcag2ict-tf@w3.org
Subject: WCAG resolutions from today's meeting


Today WCAG accepted the following items from the task force.

1. Proposed guidance for 3.2.4 Consistent Identification

RESOLUTION: Accepted as proposed

2. Edit to 2nd paragraph of 1.3.1 Info and Relationships INTENT

Sighted users perceive structure AND RELATIONSHIPS through various visual cues — headings are often in a larger, bold font separated from paragraphs by blank lines; list items are preceded by a bullet and perhaps indented; paragraphs are separated by a blank line; form fields may be positioned as groups that share text labels; a different background color may be used to indicate that several items are related to each other; words that have special status are indicated by changing the font family and /or bolding, italicizing, or underlining them; ITEMS THAT SHARE A COMMON CHARACTERISTIC ARE ORGANIZED INTO A TABLE WHERE THE RELATIONSHIP OF CELLS SHARING THE SAME ROW OR COLUMN AND THE RELATIONSHIP OF EACH CELL TO ITS ROW AND/OR COLUMN HEADER ARE NECESSARY FOR UNDERSTANDING; and so on. Having THESE structures and relationships programmatically determined or available in text ensures that information important for comprehension will be perceivable by all.

RESOLUTION: Accepted as proposed

3. Keyboard (2.1.1): Change to WCAG WG recommended edit to WCAG2ICT note text

Note: This does not imply that software must directly support a keyboard or "keyboard interface". NOR DOES IT IMPLY THAT SOFTWARE MUST PROVIDE A SOFT KEYBOARD. Underlying platform software may provide device independent input services to applications that enable operation via a keyboard. Software that supports operation via such platform device independent services would be operable by a keyboard and would comply.

RESOLUTION: Accepted as proposed

4. Pause, Stop, Hide (2.2.2): Change to WCAG WG recommended edit to WCAG2ICT note text

Note: While the success criteria uses the term "information", the WCAG 2.0 INTENT section makes it clear that this is to be applied to all content. Any content, whether informative or decorative, that IS UPDATED AUTOMATICALLY, BLINKS OR MOVES MAY CREATE AN ACCESSIBILITY BARRIER.

RESOLUTION: Accepted as proposed