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

Re: Proposed requirements for checkpoint 6.4 (Response Required)

From: David Poehlman <poehlman1@comcast.net>
Date: Wed, 31 Jul 2002 15:42:48 -0400
Message-ID: <002e01c238ca$73250370$f00f5acf@DVLDPoehlman>
To: "Jon Gunderson" <jongund@uiuc.edu>, <w3c-wai-ua@w3.org>

looks good to me.

----- Original Message -----
From: "Jon Gunderson" <jongund@uiuc.edu>
To: <w3c-wai-ua@w3.org>
Sent: Wednesday, July 31, 2002 3:40 PM
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 requirements
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..
(P1)

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 information
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
MC-574
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 Wednesday, 31 July 2002 15:42:16 GMT

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