Re: IMPORTANT: Adopt proposed revision of checkpoint 7.6 (response requested)

The addition is large enough so that perhaps it should be included in the
techniques and as a minimal requirement.

7.6 Allow the user to navigate efficiently to and among important
structural elements identified by the author. [Priority 2]

Note after checkpoint: Structured navigation of frames, headings, tables,
forms,
lists, etc. is most effective when available in conjunction with a
configurable view (checkpoint 8.4 and checkpoint 8.5). Users should be able
to navigate to  important pieces of content within a configurable view,
identify the type of object they have navigated to, interact with that
object easily (if its an active element), and recall the surrounding
context (orient themselves). Use operating system conventions to indicate
navigation progress (e.g., selection or content focus).
</PROPOSED>

Comments:

I don't think that identifying the element navigated to should be in this
checkpoint. I believe this is handled by another checkpoint.

Also, navigation to these elements should be along the DOM Tree path
following a depth-first order where the first node is the leftmost leaf.
This is the same as a postorder traversal.



Rich Schwerdtfeger
Lead Architect, IBM Special Needs Systems
EMail/web: schwer@us.ibm.com http://www.austin.ibm.com/sns/rich.htm

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


Jon Gunderson <jongund@ux1.cso.uiuc.edu>@w3.org on 05/10/2000 09:27:06 AM

Sent by:  w3c-wai-ua-request@w3.org


To:   w3c-wai-ua@w3.org
cc:
Subject:  IMPORTANT: Adopt proposed revision of checkpoint 7.6 (response
      requested)



I would like to try to use our teleconference time more efficiently so I
would like to try to resolve some issues using the list.

Ian has proposed rewording for checkpoint 7.6 [1] to resolve proposed
recommendation issue 233 [2] and included the proposal in the 7 May working
draft[3].  The following is his proposal:

<PROPOSED>
7.6 Allow the user to navigate efficiently to and among important
structural elements identified by the author. [Priority 2]

Note after checkpoint: Structured navigation of headings, tables, forms,
lists, etc. is most effective when available in conjunction with a
configurable view (checkpoint 8.4 and checkpoint 8.5). Users should be able
to navigate to  important pieces of content within a configurable view,
identify the type of object they have navigated to, interact with that
object easily (if its an active element), and recall the surrounding
context (orient themselves). Use operating system conventions to indicate
navigation progress (e.g., selection or content focus).
</PROPOSED>

Please respond to this e-mail as soon as possible if you think that we need
further discussion of the wording of this checkpoint. If there are no
responses I will assume that people are satisfied with the rewording of
this checkpoint and I will remove the issue from the issue list.  If there
is a request for further discussion I will add discussion of the proposal
to the next available telecon.

Thanks,
Jon

[1] http://lists.w3.org/Archives/Public/w3c-wai-ua/2000AprJun/0287.html
[2] http://cmos-eng.rehab.uiuc.edu/ua-issues/issues-linear.html#233
[3] http://www.w3.org/WAI/UA/WD-UAAG10-20000507/
Jon Gunderson, Ph.D., ATP
Coordinator of Assistive Communication and Information Technology
Chair, W3C WAI User Agent Working Group
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

Received on Wednesday, 10 May 2000 11:56:19 UTC