W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > July to September 1999

Re: checkpoint 6.6

From: Jon Gunderson <jongund@staff.uiuc.edu>
Date: Thu, 19 Aug 1999 12:57:23 -0700
Message-Id: <199908191752.MAA25305@staff1.cso.uiuc.edu>
To: thatch@us.ibm.com
Cc: w3c-wai-ua@w3.org
Responses in JRG:

At 09:43 PM 8/18/99 -0500, thatch@us.ibm.com wrote:
>What you have said is there exist assistive technologies that require X.
>Therefore we have made X a priority 1 requirement for user agents. How do you
>determine the quote weight endquote of X before you decide that it is heavy
>enough to have this effect.

JRG: The group discusses the issue (telecons and the list, but mostly
telecons) and determines if the checkpoint is:
1. Critical accessibility: information cannot be accessed or will not be
avialable to the user
2. Important for accessibility: information is available but maybe
difficult to access
3. Useful feature:  a very useful feature that primarily improves usability

>I am trying to look at this from a home page reader perspective; I could not
>care less that some AT uses selection for speaking.

JRG: We spent alot of time on yesterdays telecon talking about conformance
issues.  We had a number of people accept action items, including Rich S.
for HPR, to look at using the current conformance sub-grouping of
checkpoints for mainstream browsers, assistive technology and specialized
browser like HPR to see how well the conformance statement works with
current technology.  

From your response about selection and evaluating HPR there would be
several questions to ask.
1. If HPR doesn't support selection checkpoint 6.6 would not apply to HPR.

2. If HPR does support selecting web content, it maybe that you consider
speech to be the only medium that you are concerned about supporting and
any visual information rendered about selection is not relevent to the
design of your system.  Therefore checkpoints that relate to color and
other visual rendering do not apply.  Although some people in the UA group
may disagree with this statement.

3. If HPR does support selecting web content does it make information
available to other assistive technologies using standard interfaces. For
example somebody who is deaf and blind could use home page reader with
another assistive technology to read WWW pages through a refreshable
Braille Display?

Do these question amke sense?

It would be great if you were will to go through the current checkpoints
and indicate which ones you think would apply to HPR and which ones would


>Jim Thatcher
>IBM Special Needs Systems
>Jon Gunderson <jongund@staff.uiuc.edu> on 08/18/99 10:52:36 AM
>To:   James Thatcher/Austin/IBM@IBMUS, w3c-wai-ua@w3.org
>Subject:  Re: checkpoint 6.6
>Some types of assistive technology, like TextHelp, ZoomText and Aurora,
>use selection to identify information to speak.  This is especially
>important for browsers which do not have a cursor for AT to track.  A user
>could select a section of text using the mouse (or hopefully directly the
>keyboard someday) and use one of these assistive technologies to read the
>selected information.  TextHelp and Aurora speech output features are
>designed for people with learning disabilities and ZoomText is for people
>with visual impairments.
>This why it was given a high priority.
>At 05:20 PM 8/17/99 -0500, thatch@us.ibm.com wrote:
>>Here is 6.6:
>>Allow the user to control selection highlighting (e.g., foreground
>>and background color).
>>Sure that is a nifty idea. It is also another setting, which is complexity.
>>But, since selection is usually reverse video, my question is, has that
>>ever been done before? Has this checkpoint been given adequate
>>If it has never been done before, if no one has seen selectable
>>selection colors, then I think this is an example of a priority one
>>checkpoint that belongs in the priority three bucket, at best.
>>Jim Thatcher
>>IBM Special Needs Systems
>Jon Gunderson, Ph.D., ATP
>Coordinator of Assistive Communication and Information Technology
>Division of Rehabilitation - Education Services
>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
>     http://www.als.uiuc.edu/InfoTechAccess
Jon Gunderson, Ph.D., ATP
Coordinator of Assistive Communication and Information Technology
Division of Rehabilitation - Education Services
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
Received on Thursday, 19 August 1999 13:52:36 UTC

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