W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > January to March 2000

Re: Proposed clarification of Checkpoint 1.5

From: Jon Gunderson <jongund@ux1.cso.uiuc.edu>
Date: Tue, 29 Feb 2000 08:46:03 -0600
Message-Id: <4.1.20000229084521.00a53390@staff.uiuc.edu>
To: w3c-wai-ua@w3.org
Responses in JRG:

>1) We are expressing a user-interface requirement, not a programmatic
>   access requirement. Checkpoint 5.2 already requires programmatic
>   access to user interface controls.
>2) I don't think 1.5 is meant to require a text equivalent for each
>   message to the user. I think that text is a useful technique that
>   enables different output modalities. Note that programmatic access 
>   to UI controls is covered by checkpoint 5.2

JRG: I think this was the practical meaning of the original checkpoint.  
Even though 5.2 talks about programmatic access, if the original information 
is a graphic or a sound, the AT will only get the graphic or sound 
reference.  So a message dialog box in screen reader sounf like graphic, 
graphic and OK button.  If the graphics were images conveying the message.  
Without some type of text equivalent the screen reader my have programmatic 
access, but the programmatic information will not have the information in a 
form it can translate to speech.  I think that Checkpoint 1.5 is really the 
analog of WCGL requirements for alternative equivalents, except that here we 
want alternative redundency.

>3) I don't think that the requirement is for a user agent to provide
>   a user interface controls, say, both graphically and through audio
>   (but not speech if speech is not supported).
>So what is this requirement supposed to say? A previous incarnation
>of the checkpoint (from the Last Call draft
>http://www.w3.org/TR/1999/WD-WAI-USERAGENT-19991105/) suggests that
>it's really about messages through the UI:
>      1.5 Ensure that user agent-initiated messages to the user 
>         (e.g., informational messages, warnings, error messages, etc.) 
>         are available through all output channels supported by the user 
>         interface.

JRG: This seems to contradict item 3 of your requirements.  This seems to 
say if you use any sounds, then all messages must use sound.

Jon Gunderson, Ph.D., ATP
Coordinator of Assistive Communication and Information Technology
Chair, W3C WAI User Agent Working Group
Division of Rehabilitation - Education Services
College of Applied Life Studies
University of Illinois at Urbana/Champaign
1207 S. Oak Street, Champaign, IL  61820

Voice: (217) 244-5870
Fax: (217) 333-0248

E-mail: jongund@uiuc.edu

WWW: http://www.staff.uiuc.edu/~jongund
WWW: http://www.w3.org/wai/ua
Received on Tuesday, 29 February 2000 09:48:33 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:38:25 UTC