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

Re: Proposed changes to Guideline 9 on orientation

From: Charles McCathieNevile <charles@w3.org>
Date: Fri, 23 Jul 1999 12:08:54 -0400 (EDT)
To: Jon Gunderson <jongund@staff.uiuc.edu>
cc: w3c-wai-ua@w3.org
Message-ID: <Pine.LNX.4.10.9907231207480.7732-100000@tux.w3.org>
I support the proposed changes.

I would suggest that the old checkpoints be reworked into techniques, and I
think in a couple of cases we might want to list required information in
explanatory notes in the checkpoint, but we should look at it first.

Charles McCN

On Thu, 22 Jul 1999, Jon Gunderson wrote:

  Jim Allan and I this moring came up with a proposal to reduce the number of
  checkpoints in Guideline 9 from 25 down to 11.  
  
  1. 22 current checkpoints are consolidated into 4 new more general
  checkpoints that better relect the indent of the original checkpoints
  2. 4 checkpoints remain unchanges
  3. 4 three new checkpoints are proposed for configuration
  4. 1 checkpoint was removed since it seemed to be part of an existing
  navigation checkpoint
  
  The proposed checkpoints have the prefix "Checkpoint".
  
  Four new Checkpoints that consolidate other checkpoints
  Checkpoint: Provide summary information about the current view [Priority 1,
  Both]
  
  Consolidates the following 6 checkpoints in the current draft
  9.1 Provide a mechanism for highlighting and identifying (through a
  standard interface where available) the current view. [Priority 1] 
  9.2 Provide a mechanism for highlighting and identifying (through a
  standard interface where available) the user selection. [Priority 1] 
  9.3 Provide a mechanism for highlighting and identifying (through a
  standard interface where available) the current focus. [Priority 1] 
  9.7 Identify a frame selected by the user. [Priority 2] 
  9.9 Make available the primary language of a document's content. [Priority 3] 
  9.14 Make available what portion of the document has loaded. [Priority 3] 
  
  Checkpoint: Provide information about the attributes of a current element
  [Priority 1, Both]
  
  Consolidates the following 5 checkpoints in the current draft
  9.16 Make available whether a chosen link (target) has already been
  visited. [Priority 3] 
  9.17 Make available whether a chosen link (target) is local to the
  document. [Priority 3] 
  9.18 Make available whether following a link will involve a fee. [Priority 3] 
  9.20 Make available the dimensions of a chosen table. [Priority 3] 
  9.24 Provide the user with access to any label explicitly associated with a
  form control. [Priority 2]
  
  Checkpoint: Provide statistical information on document content [Priority 2]
  
  Consolidates the following 7 checkpoints in the current draft
  9.4 Provide the user with information about the number of viewports.
  [Priority 2]
  9.9 Make available the primary language of a document's content. [Priority 3] 
  9.10 Make available the number of links (to distinct targets) in a
  document. [Priority 3] 
  9.11 Make available the number of visited links (to distinct targets) in a
  document. [Priority 3] 
  9.12 Make available the number of tables in a document. [Priority 3] 
  9.13 Make available the number of form controls in a document. [Priority 3] 
  9.14 Make available what portion of the document has loaded. [Priority 3] 
  
  Checkpoint: Provide relative position information for the current element
  [Priority 2]
  
  Consolidates the following 4 checkpoints in the current draft
  9.15 Identify a link selected by the user. [Priority 3] 
  9.19 Identify a table selected by the user. [Priority 3] 
  9.22 Identify the table containing a table cell selected by the user.
  [Priority 3] 
  9.23 Make available the coordinates in the current table of a selected
  table cell. [Priority 3] 
  
  Four Unchanged Checkpoints:
  Checkpoint: Provide access to header information for a table cell selected
  by the user [Priority 1, DUA]
  
  Checkpoint: Ensure that when the selection changes, it is in the viewport
  after the change. [Priority 2] 
  
  Checkpoint: Ensure that when the focus changes, it is in the viewport after
  the change. [Priority 2] 
  
  Checkpoint: Maintain consistent user agent behavior and default
  configurations between software releases. Consistency is less important
  than accessibility and adoption of system conventions. [Priority 3] 
  
  Three New Checkpoints:
  Checkpoint: Allow the user to configure summary information [Priority 3]
  
  Checkpoint: Allow the user to configuration statistical information
  [Priority 3]
  
  Checkpoint: Allow the user to configure types attribute information
  identified [Priority 3]
  
  Remove Checkpoints
  Checkpoint 9.8 seems to be defined in 8.6 (remove)
  
  Please review and comment on this proposal.
  
  Jon
  
  
  
  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
  

--Charles McCathieNevile            mailto:charles@w3.org
phone: +1 617 258 0992   http://www.w3.org/People/Charles
W3C Web Accessibility Initiative    http://www.w3.org/WAI
MIT/LCS  -  545 Technology sq., Cambridge MA, 02139,  USA
Received on Friday, 23 July 1999 12:08:56 GMT

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