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

Re: (Action) Issue 370: Proposed rewording for checkpoint 7.6 (and Note)

From: Charles McCathieNevile <charles@w3.org>
Date: Sat, 6 Jan 2001 14:19:25 -0500 (EST)
To: Ian Jacobs <ij@w3.org>
cc: <w3c-wai-ua@w3.org>
Message-ID: <Pine.LNX.4.30.0101061418560.6421-100000@tux.w3.org>
Yep. I agree that it is editorial - well done editorial folks!

Chaals

On Fri, 5 Jan 2001, Ian Jacobs wrote:

  Hello,

  At the AOL ftf meeting, Al and I got an action item for issue
  370 [1] to propose new wording for checkpoint 7.6 to clarify
  that we are not asking authors to mark up "important elements"
  specially, and that which elements are important is part of
  the format itself. Please consider the following proposal
  (which I believe is editorial). Here is the relevant
  excerpt from the 29 December draft [2]:

  <OLD>
  7.6 Allow the user to navigate efficiently to and among
  important structural elements identified by the author.
  Allow forward and backward sequential navigation to important
  structural elements.
     Note: This specification intentionally does not
     identify the set of "important elements" that must be
     navigable; refer to the Techniques document [UAAG10-TECHS]
     for information about identifying important elements
  </OLD>

  For some previous discussion on identification of
  "important elements", refer to this 28 August 2000 email
  from Al [3]. In that email, Al expressed opposition to
  relying on element type alone as the determining factor
  for establishing an element as important. The following
  checkpoint is simpler, but the Note more complete. It
  draws on some of the points raised by Al in his email.

  <NEW>
  7.6 Allow the user to navigate efficiently to and among
  important structural elements
     Note: This specification intentionally does not
     identify which "important elements" must be
     navigable as this will vary according to markup
     language. What constitutes "efficient navigation"
     may depend on a number of factors as well, including
     the "shape" of content (e.g., serial navigation
     of long lists is not efficient) and desired granularity
     (e.g., among tables, then among the cells of a given
     table). Refer to the Techniques document [UAAG10-TECHS]
     for information about identifying and navigating
     important elements.
  </NEW>

   - Ian

  [1] http://www.w3.org/WAI/UA/2000/11/minutes-20001116#issue-370
  [2] http://www.w3.org/WAI/UA/WD-UAAG10-20001229/
  [3] http://lists.w3.org/Archives/Public/w3c-wai-ua/2000JulSep/0312.html


-- 
Charles McCathieNevile    mailto:charles@w3.org    phone: +61 (0) 409 134 136
W3C Web Accessibility Initiative                      http://www.w3.org/WAI
Location: I-cubed, 110 Victoria Street, Carlton VIC 3053, Australia
until 6 January 2001 at:
W3C INRIA, 2004 Route des Lucioles, BP 93, 06902 Sophia Antipolis Cedex, France
Received on Saturday, 6 January 2001 14:19:25 GMT

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