Action 242:


My action 242 was to review WCAG 2.0 for places that talked about "a mechanism is available" to identify any places that our 2.0 update needed to address.  Here are my findings.

WCAG 2.0 - 1.4.2 Audio Control: If any audio on a Web page plays automatically for more than 3 seconds, either a mechanism<> is available to pause or stop the audio, or a mechanism is available to control audio volume independently from the overall system volume level. (Level A)

KF: The stop and start behavior is covered by our 4.9.7 on stop, pause and start of multimedia.

UAAG 2.0 - 4.9.7 Stop/Pause/Resume Multimedia: The user can stop, pause, and resume rendered audio and animation<> content (including video and animated images) that last three or more seconds at their default playback rate. (Level

KF: We cover volume control in 3.7.  We require that volume control be available but do not specifically say this is independent of other system volume.


Note our current 3.7.2 would move to 3.7.3

3.7.2 Local Volume: The user can set the volume of all rendered audio tracks<> (including a "mute" setting) through available operating environment<> mechanisms with settings specific to the user agent such that volume of the user agent is independent from the overall operating system. (Level AA)

 WACG 2.0 - 1.4.8 Visual Presentation: For the visual presentation of blocks of text<>, a mechanism<> is available to achieve the following: (Level AAA)

  1.  Foreground and background colors can be selected by the user.
  2.  Width is no more than 80 characters or glyphs (40 if CJK).
  3.  Text is not justified (aligned to both the left and the right margins).
  4.  Line spacing (leading) is at least space-and-a-half within paragraphs, and paragraph spacing is at least 1.5 times larger than the line spacing.
  5.  Text can be resized without assistive technology up to 200 percent in a way that does not require the user to scroll horizontally to read a line of text on a full-screen window<>.

KF: UAAG 3.6.1 item C addresses the text foreground and background text.  We don't really address the rest of these.  The one that seems possibly interesting for us is the zoom to 200%.

UAAG 2.0 - 3.6.1 Configure Text: The user can globally set the following characteristics of visually rendered text<> content, overriding<> any specified by the author<> or user agent defaults (Level A):
*         (a) text scale (i.e., the general size of text) ,
*         (b) font family, and
*         (c) text color (i.e., foreground and background).

WCAG 2.0 - 2.2.2 Pause, Stop, Hide: For moving, blinking<>, scrolling, or auto-updating information, all of the following are true: (Level A)

  *   Moving, blinking, scrolling: For any moving, blinking or scrolling information that (1) starts automatically, (2) lasts more than five seconds, and (3) is presented in parallel with other content, there is a mechanism for the user to pause<>, stop, or hide it unless the movement, blinking, or scrolling is part of an activity where it is essential<>; and
  *   Auto-updating: For any auto-updating information that (1) starts automatically and (2) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it or to control the frequency of the update unless the auto-updating is part of an activity where it is essential.

KF: The best match we have for this is in our 4.3 and 4.4 guidelines dealing with time independent interaction and helping avoid flashin. 4.3 seems pretty solid with respect to what we'd expect of a UAAG to help here.  4.4 isn't quite as good of a match but I don't think there is more we need to do.

WCAG 2.0 - 2.4.1 Bypass Blocks: A mechanism<> is available to bypass blocks of content that are repeated on multiple Web pages<>. (Level A)

KF: Interesting challenge.  In web content this tends to be done with skip nav and such.  I don't think there's anything we need to require of a user agent for this one.

UAAG 2.0 - 2.4.9 Link Purpose (Link Only): A mechanism<> is available to allow the purpose of each link to be identified from link text alone, except where the purpose of the link would be ambiguous to users in general<>. (Level AAA)

KF: This is talking about avoiding the "click here" links as an example.  I don't think we need to do anything.

WCAG 2.0 - 3.1.3 Unusual Words: A mechanism<> is available for identifying specific definitions of words or phrases used in an unusual or restricted way<>, including idioms<> and jargon<>. (Level AAA)

KF: No action for us.

WCAG 2.0 - 3.1.4 Abbreviations: A mechanism<> for identifying the expanded form or meaning of abbreviations<> is available. (Level AAA)

KF: No action for us.

WCAG 2.0 - 3.1.6 Pronunciation: A mechanism<> is available for identifying specific pronunciation of words where meaning of the words, in context, is ambiguous without knowing the pronunciation. (Level AAA)

KF: No action for us.

WCAG 2.0 - 3.2.5 Change on Request: Changes of context<> are initiated only by user request or a mechanism<> is available to turn off such changes. (Level AAA)

KF: Our 3.10.7 Open on Request and 3.11.10 Only on User Request: kind of addresses this but may need some refinement.

WCAG 2.0 - 3.3.4 Error Prevention (Legal, Financial, Data)
One part of this states:
Confirmed: A mechanism<> is available for reviewing, confirming, and correcting information before finalizing the submission.

KF: We mayneed to add a success criteria here, although I thought we did address this.


Received on Thursday, 11 February 2010 17:49:58 UTC