Thread Subject: Re: Group D: 22(o) skip navigation

Note

This archival content is maintained by WebAIM and NCDAE on behalf of TEITAC and the U.S. Access Board . Additional details on the updates to section 508 and section 255 can be found at the Access Board web site.

From: Hoffman, Allen
Date: Tue, Feb 27 2007 7:50 AM

Andi wrote:
"Sorry I didn't document this more clearly. When we discussed this, we
favored something like what WCAG 2.0 has that requires structure in the
content which would enable user agents and assistive technologies to
provide efficient navigation to important content on the page. I will be
putting forward a more concrete proposal on this soon for our report to
the TEITAC."

Does anyone feel this is something which is possible to reduce to an
automated testable condition? If so, it will need a hard scoping.

For example:

When a web page contains content that is logically separated, a
navigation method shall be provided that allows navigation to be
executed from the keyboard or alternate pointing device via use of
mark-up.

To be honest, I'd like to require that pages that have logical
separators and navigation features, include semantic information, or
meta-data defining the logical structure. is that possible?

Maybe a requirement that when pages include logical content separators,
that some indicator exists on the page. This would make this far more
testable. Once we start down the "efficient navigation " path we are
digging subjective dirt in my opinion.


This wouldn't mirror W3C and would be a plunge.
Just a thought.




Allen Hoffman -- 202-447-0303
DHS Office on Accessible Systems & Technology

-----Original Message-----
From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Andi
Snow-Weaver
Sent: Monday, February 26, 2007 3:26 PM
To: TEITAC Web/Software Subcommittee
Subject: Re: [teitac-websoftware] Group D: 22(o) skip navigation

Jamie wrote:

I've been looking through the wiki and couldn't tell if the discuss
regarding the current requirement of skip navigation ended up including
some type of structured navigation included in the draft.

<end of Jamie's comment>

Sorry I didn't document this more clearly. When we discussed this, we
favored something like what WCAG 2.0 has that requires structure in the
content which would enable user agents and assistive technologies to
provide efficient navigation to important content on the page. I will be
putting forward a more concrete proposal on this soon for our report to
the TEITAC.

Andi

WebAIM is an initiative of:
Center for Persons with Disabilities (CPD) Utah State University