W3C home > Mailing lists > Public > w3c-wai-au@w3.org > April to June 2013

ATAG2 If clauses causing problems for finding positive implementations

From: Richards, Jan <jrichards@ocadu.ca>
Date: Fri, 17 May 2013 20:00:15 +0000
To: "w3c-wai-au@w3.org" <w3c-wai-au@w3.org>
Message-ID: <0B1EB1C972BCB740B522ACBCD5F48DEB6BEA7476@ocadmail-maildb.ocad.ca>
Hi all,

A while back, in order to be more clear about applicability, we added IF statements to many of ATAG2's SCs. 

This did make applicability more clear, but in some cases the behaviour in question was so obviously "dangerous" from an accessibility (and often usability) perspective (e.g. moving clickable controls) that it was already rare.

This is a challenge now that we are trying to find POSITIVE implementations for CR (i.e. implementations that meet the IF clause). 

One possibility would be to change all of them to include not doing the "dangerous" thing as an implementation option (We already do this for " A.3.1.2 No Keyboard Traps" which says essentially "don't allow keyboard traps" rather than saying "IF you cause a keyboard trap, then do X").

The new wording could be something like...The authoring tool either does not do X or if it does, then it compensates by doing Y.

Here's my list:

A.3.2.1 Auto-Save (Minimum): If the authoring tool includes authoring session time limits, then the authoring tool can be set to automatically save web content edits made using the authoring tool before the session time limits are reached. (Level A)

A.3.2.2 Timing Adjustable: If a time limit is set by the authoring tool, then at least one of the following is true: (Level A)
(a) Turn Off: Authors are allowed to turn off the time limit before encountering it; or
(b) Adjust: Authors are allowed to adjust the time limit before encountering it over a wide range that is at least ten times the length of the default setting; or
(c) Extend: Authors are warned before time expires and given at least 20 seconds to extend the time limit with a simple action (e.g., "press the space bar"), and authors are allowed to extend the time limit at least ten times; or
(d) Real-time Exception: The time limit is a required part of a real-time event (e.g., a collaborative authoring system), and no alternative to the time limit is possible; or
(e) Essential Exception: The time limit is essential and extending it would invalidate the activity; or
(f) 20 Hour Exception: The time limit is longer than 20 hours.

A.3.2.3 Static Input Components: If authoring tool user interface components accept input and move, then authors can pause the movement. (Level A)

A.3.3.1 Static View Option: If the authoring tool contains editing-views that render and play visual time-based content automatically, then those editing-views can be paused and can be set to not play automatically. (Level A)

B.1.1.1 Content Auto-Generation After Authoring Sessions (WCAG): If the authoring tool provides the functionality for automatically generating web content after the end of an authoring session, authors can specify that the content be accessible web content (WCAG). (Level A to meet WCAG 2.0 Level A success criteria; Level AA to meet WCAG 2.0 Level A and AA success criteria; Level AAA to meet all WCAG 2.0 success criteria)
- Note: This success criterion applies only to automatic processes specified by the authoring tool developer. It does not apply when author actions prevent generation of accessible web content (WCAG).

B.2.1.1 Accessible Content Possible (WCAG): If the authoring tool places restrictions on the web content that authors can specify, then those restrictions do not prevent WCAG 2.0 success criteria from being met. (Level A to meet WCAG 2.0 Level A success criteria; Level AA to meet WCAG 2.0 Level A and AA success criteria; Level AAA to meet all WCAG 2.0 success criteria)

B.2.3.2 Repair of Text Alternatives During Authoring Sessions: If the authoring tool attempts to automatically or semi-automatically repair text alternatives for non-text content ("repair strings") during an authoring session, then the following are both true: (Level A)
    (a) No Generic or Irrelevant Strings: Generic strings (e.g. "image") and irrelevant strings (e.g., the file name, file format) are not offered as repair strings; and
    (b) Author Control: Authors have the opportunity to accept, modify, or reject the repair strings prior to insertion in the content.

B.2.3.3 Repair of Text Alternatives After Authoring Sessions: If the authoring tool attempts to automatically repair text alternatives for non-text content after an authoring session has ended, then the following are both true: (Level A)
    (a) No Generic or Irrelevant Strings: Generic strings (e.g. "image") and irrelevant strings (e.g., the file name, file format) are not used as repair strings; and
    (b) Author Control: In the subsequent authoring session (if any), auto-generated text alternatives are indicated and authors have the opportunity to accept, modify, or reject the text alternatives.

B.4.1.2 Option to Reactivate Features: If authors can turn off an accessible content support feature, then they can turn the feature back on. (Level A)

B.4.1.3 Feature Deactivation Warning: If authors turn off an accessible content support feature, then the authoring tool informs them that this may increase the risk of content accessibility problems (WCAG). (Level AA)

Cheers,
Jan




(MR) JAN RICHARDS
PROJECT MANAGER
INCLUSIVE DESIGN RESEARCH CENTRE (IDRC)
OCAD UNIVERSITY

T 416 977 6000 x3957
F 416 977 9844
E jrichards@ocadu.ca
Received on Friday, 17 May 2013 20:00:42 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:40:05 UTC