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

RE: UAAG Priority 1 checkpoint analysis summary

From: John M Slatin <john_slatin@austin.utexas.edu>
Date: Sat, 23 Apr 2005 15:34:43 -0500
Message-ID: <6EED8F7006A883459D4818686BCE3B3B01179B44@MAIL01.austin.utexas.edu>
To: "Loretta Guarino Reid" <lguarino@adobe.com>, <w3c-wai-gl@w3.org>

Thanks for the analysis!

Several questions are raised at the end of the analysis:
(UAAG) 2.3 Render conditional content
         Do we need a requirement to expose conditional content 
programmatically?
Js: Interesting problem, probably best exemplified by 1.1 L1 SC requring
explicit association of text alternatives with non-text content and the
ongoing discussion about how to provide alternatives for the <object>
element. Another example would come up in trying to create an
explicit/programmatic association between complex text content and a
*non-text alternative* for that text.  We can associate a block of text
with an <img> using longdesc; but there's no counterpart when the
relationship goes the other way-- there's no such construct as <p
alt="figure4.gif">Some complex analysis here.</p>

3.1 Toggle background images
         WCAG 1.4 requires making it easy to distinguish foreground 
information from background information. However, we may need a
requirement 
that the background image can be identified programmatically 
Js: An image presenting words against a background would satisfy 1.4 (as
it stands now) as long as the words are legible. But if we add an SC as
suggested, that might disallow such images and would have to go at L2 or
3.


3.2 Toggle audio, video, animated images
         We think audio and video will always be identifiable 
programmatically, but we may need to add a requirement for animated
images 3.3 Toggle animated or blinking text
         Do we need a requirement to identify animated or blinking text 
programmatically? Does WCAG 2.3 cover this sufficiently?
Js: This was discussed extensively at the tech plenary, and if I
remember right the conclusion was that 2.3 *does* address this.

3.5 Toggle automatic content retrieval
         Do we need a requirement to be able to identify automatic
content 
retrieval programmatically?
Js: not sure I understand what this means...

</blockquote>

"Good design is accessible design."

Dr. John M. Slatin, Director 
Accessibility Institute
University of Texas at Austin 
FAC 248C 
1 University Station G9600 
Austin, TX 78712 
ph 512-495-4288, fax 512-495-4524 
email jslatin@mail.utexas.edu 
Web http://www.utexas.edu/research/accessibility 



-----Original Message-----
From: w3c-wai-gl-request@w3.org [mailto:w3c-wai-gl-request@w3.org] On
Behalf Of Loretta Guarino Reid
Sent: Tuesday, April 19, 2005 5:40 PM
To: w3c-wai-gl@w3.org
Subject: UAAG Priority 1 checkpoint analysis summary



UAAG checkpoints currently covered by WCAG guidelines:

1.1 Full keyboard access
         WCAG 2.1 requires keyboard access to all functionality 1.2
Activate event handlers
         WCAG 2.1 requires keyboard access to all functionality 1.3
Provide text messages
         WCAG 1.1 requires text equivalents
2.1 Render content according to specification
         WCAG 4.1 requires writing to spec (but at level 3)
2.4 Allow time-independent interaction
         WCAG 2.2 requires that users be able to control time limits on 
their reading or interaction
2.5 Make captions, transcripts, audio descriptions available
         WCAG 1.2 requires synchronized alternatives to multi-media;
WCAG 
1.1 requires test alternatives
4.14 Choose style sheets
         WCAG 1.3 capture the author requirements
10.1 Associate table cells and headers
         WCAG 1.3/2.4 covers table structure

UAAG checkpoints that are user agent issues:

2.2 Provide text view
2.6 Respect synchronization cues
3.4 Toggle scripts
4.1 Configure text scale
4.2 Configure font family
4.3 Configure text colors
4.4 Slow multimedia
4.5 Start, stop, pause, and navigate multimedia
4.6 Do not obscure captions
4.7 Global volume control
4.8 Independent volume control
4.9 Configure synthesized speech rate
4.10 Configure synthesized speech volume
4.11 Configure synthesized speech characteristics
6.7 Conventional keyboard APIs
6.8 API character encodings
7.1 Respect focus and selection conventions
7.2 Respect input configuration conventions
8.1 Implement accessibility features
10.2 Highlight selection, content focus, enabled elements, visited links
10.6 Highlight current viewport 11.1 Current user input configuration
12.1 Provide accessible documentation 12.2 Provide documentation of
accessibility features 12.3 Provide documentation of default bindings

UAAG checkpoints that may need additional coverage in WCAG:

2.3 Render conditional content
         Do we need a requirement to expose conditional content 
programmatically?
3.1 Toggle background images
         WCAG 1.4 requires making it easy to distinguish foreground 
information from background information. However, we may need a
requirement 
that the background image can be identified programmatically 3.2 Toggle
audio, video, animated images
         We think audio and video will always be identifiable 
programmatically, but we may need to add a requirement for animated
images 3.3 Toggle animated or blinking text
         Do we need a requirement to identify animated or blinking text 
programmatically? Does WCAG 2.3 cover this sufficiently?
3.5 Toggle automatic content retrieval
         Do we need a requirement to be able to identify automatic
content 
retrieval programmatically?

Guideline 6: Implement interoperable application programming interfaces:

See Wendy's analysis
         6.1 Programmatic access to HTML/XML infoset
         6.2 DOM access to HTML/XML content
         6.3 Programmatic access to non-HTML/XML content
         6.5 Programmatic operation of user agent user interface

Guildeline 9: Provide navigation mechanisms: See Loretta's analysis
         9.1 Provide content focus
         9.2 Provide user interface focus
         9.3 Move content focus
         9.4 Restore viewport state history
          
Received on Saturday, 23 April 2005 20:34:51 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 5 February 2014 23:39:37 UTC