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

re JA will go through UAAG2 and look at places concerned with revealing alternates

From: Jim Allan <jimallan@tsbvi.edu>
Date: Tue, 3 Jun 2008 17:42:31 -0500
To: <w3c-wai-ua@w3.org>
Message-ID: <00ed01c8c5cb$1c32bfa0$54983ee0$@edu>

Action: JA will go through UAAG2 and look at places concerned with revealing
alternates [recorded in
http://www.w3.org/2008/05/29-ua-minutes.html#action03] 

The following Success Criteria relate to rendering any and all alternative
content for an element and alerting the user to the existence of multiple
types of alternative content for an element.   

Level A Success Criteria for Guideline 1.2
1.2.1 Accessibility Features: The accessibility features listed in the
"technology accessibility features benchmark" @@Ed: Definition of this term
will likely let claimant specify these in the conformance claim@@ are
implemented for all technologies listed in the conformance profile.@@8.1 in
UAAG10@@ 

Level A Success Criteria for Guideline 1.3
1.3.1 Follow Specifications: Render content according to the technology
specification. This includes any accessibility features of the technology
(see Guideline 1.2) . @@2.1 in UAAG10@@ 

Level A Success Criteria for Guideline 3.2
3.2.1 Alert to Non-Rendered: The user has the option to be alerted to the
presence of non-rendered alternative content (e.g., short text alternatives,
long descriptions, captions, audio descriptions) for any given piece of
rendered content. (Note: The rendered content and its non-rendered
alternatives constitute the alternative content stack). @@Implied in 2.3 in
UAAG10@@

3.2.2 Browse and Render: The user can browse the alternative content stack
and render its items according to the following:
          o (a) synchronized alternatives for synchronized media (e.g.,
captions, audio descriptions, sign language) can be rendered at the same
time as their associated audio tracks and visual tracks, and @@Implied in
2.3 in UAAG10@@
          o (b) non-synchronized alternatives (e.g., short text
alternatives, long descriptions) can be rendered as replacements for the
original rendered content. If the new item has different dimensions, then a
user option controls whether the dimensions of the original content are used
or the dimensions of the new content, which will cause the document to
reflow accordingly.@@Implied in 2.3 in UAAG10@@

3.2.3 Available Programmatically: If an item in the alternative content
stack is plain text (e.g., short text alternative), then it is available
programmatically, even when not rendered. @@Implied in 2.3 in UAAG10@@

Level AA Success Criteria for Guideline 3.2

3.2.4 Simultaneous Rendering: The user has the option to simultaneously
render any and all items from the alternative content stack (which will
cause the document to reflow accordingly) unless the user agent can
recognize a mutual exclusion (e.g. conflicting soundtracks).@@NEW@@
3.2.5 Configurable Default Rendering: The user has the option to set
preferences for which items in an alternative content stack will be rendered
by default. @@2.9 in UAAG10@@

Level A Success Criteria for Guideline 3.5
3.5.1 Repair Missing Alternatives: The user has the option of receiving
generated repair text when the user agent recognizes that the author has not
provided alternative content required by the technology specification (e.g.,
short text alternative for an image).@@2.7 in UAAG10@@

Level AAA Success Criteria for Guideline 3.5
3.5.2 Repair Empty Alternatives: The user has the option of receiving
generated repair text when the user agent recognizes that the author has
provided empty alternative content for an enabled element. @@2.8 in UAAG10@@

Jim Allan, Webmaster & Statewide Technical Support Specialist
Texas School for the Blind and Visually Impaired
1100 W. 45th St., Austin, Texas 78756
voice 512.206.9315    fax: 512.206.9264  http://www.tsbvi.edu/
"We shape our tools and thereafter our tools shape us." McLuhan, 1964
Received on Tuesday, 3 June 2008 22:46:40 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 October 2009 06:51:57 GMT