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

Re: Proposed requirements for checkpoint 6.4 (Response Required)

From: Richard Schwerdtfeger <schwer@us.ibm.com>
Date: Thu, 1 Aug 2002 15:38:14 -0500
To: "Ian B. Jacobs" <ij@w3.org>
Cc: "Hansen, Eric" <ehansen@ets.org>, "'Jon Gunderson'" <jongund@uiuc.edu>, w3c-wai-ua@w3.org, w3c-wai-ua-request@w3.org
Message-ID: <OF226C1789.F3766BC4-ON86256C08.00765173@boulder.ibm.com>


If you get the event notification you will still want to get the bounding
rectangle of the element within the image map according to this ceckpoint.
Screen coordinates are different than coordinates relative to a parent
window. You need to be careful to get the correct information.


Rich Schwerdtfeger
Senior Technical Staff Member
IBM Accessibility Center
Research Division
EMail/web: schwer@us.ibm.com

"Two roads diverged in a wood, and I -
I took the one less traveled by, and that has made all the difference.",

                      "Ian B. Jacobs"                                                                                                  
                      <ij@w3.org>              To:       Richard Schwerdtfeger/Austin/IBM@IBMUS                                        
                                               cc:       "Hansen, Eric" <ehansen@ets.org>, "'Jon Gunderson'" <jongund@uiuc.edu>,       
                      07/31/2002 03:59          w3c-wai-ua@w3.org, w3c-wai-ua-request@w3.org                                           
                      PM                       Subject:  Re: Proposed requirements for checkpoint 6.4 (Response Required)              

Richard Schwerdtfeger wrote:
> We need to have information about:
> object 's bounding rectangle in screen coordinates

That's covered by the proposal ("bounding dimensions" just
in case it's not a rectangle).

> bounding rectangle of active elements withing an image map in screen
> coordinates
> These would assist magnification software in knowing where to focus on
> elements.

Checkpoint 6.6 requires notification of changes, including changes
to focus. So through 6.6, a screen magnifier should know which
element has focus.

Checkpoints 6.5 and 6.6 do not say explicitly: You must be able to
find out which element has focus. However, the definition of
"user agent user interface" includes selection and focus explicitly.
I think no change is required to accomplish Rich's goal. However,
if people feel it would be clearer to say in 6.5 "including
selection, content focus, and user interface focus", that's fine
with me. Furthermore, it would make 6.5 and 6.6 almost identical.

  - Ian

>>-----Original Message-----
>>From: Jon Gunderson [mailto:jongund@uiuc.edu]
>>Sent: Wednesday, July 31, 2002 3:40 PM
>>To: w3c-wai-ua@w3.org
>>Subject: Proposed requirements for checkpoint 6.4 (Response Required)
>>Ian and I have been discussing the lack of requirements in Checkpoint
>>6.4.  This kind of sticks out in a document that has specific
>>for almost all of the other checkpoints.  The checkpoint
>>point would have a
>>total of 3 required provisions (2 more than now) and 2 optional
>>provisions.  The changes were based on information gathered from AT
>>developers and the working group.
>>Please RESPOND as soon as possible to this e-mail on whether
>>you agree or
>>disagree with the changes.
>>I would like to proposed the following change to checkpoint 6.4:
>>Checkpoint 6.4 Programmatic access to information about
>>rendered content..
>>Provision 1: Make available bounding dimensions and location
>>of rendered
>>graphical objects
>>Provision 2: Provide access to the following information
>>about each piece
>>of rendered text:
>>a. font-family
>>b. font-weight (e.g. bold)
>>c. font-style (e.g. italic)
>>d. font-size
>>e. text decorations (e.g. underline, strike through)
>>g. foreground color
>>h. background color
>>Provision 3: As part of satisfying the provisions of this checkpoint,
>>implement at least one API according to the API cascade described in
>>provision two of checkpoint 6.3.
>>Note(1): The API used to provide access to visually rendered
>>should provide access to both structured information and pixel-level
>>information. User agents should also provide information about the
>>correspondence (in both directions) between locations in content and
>>related locations in the rendering structure."
>>Note(2): The user agent should also provide access to
>>information about
>>each graphical object, such as its role, a text description and other
>>useful information in describing the state and content of the object.
>>Jon Gunderson, Ph.D., ATP
>>Coordinator of Assistive Communication and Information Technology
>>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
> This e-mail and any files transmitted with it may contain privileged or
> confidential information. It is solely for use by the individual for whom
> it is intended, even if addressed incorrectly. If you received this
> in error, please notify the sender; do not disclose, copy, distribute, or
> take any action in reliance on the contents of this information; and
> it from your system. Any other use of this e-mail is prohibited. Thank
> for your compliance.

Ian Jacobs (ij@w3.org)   http://www.w3.org/People/Jacobs
Tel:                     +1 718 260-9447
Received on Thursday, 1 August 2002 16:39:12 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:49:32 UTC