Thread Subject: Re: Group D: 22(o) Skip navigation
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: Jonathan Avila
Date: Tue, Dec 05 2006 11:30 AM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: Andi Snow-Weaver: "Re: Group D: 22(o) Skip navigation"
- Previous message in thread: David Poehlman: "Re: Group D: 22(o) Skip navigation"
- Messages sorted by: Author | Thread | Date
<blockquote> What constitutes a "method" or "mechanism"?
Does it need to be in the HTML document such as the 'skip nav' links often
used today? Or does providing structure such as list elements to group
blocks of links, and headings to denote the start of new sections enough
considering many (but not all) user agents--in particular screen
readers--have navigation methods in place to move amongst the elements,
e.g., move to the next heading?
At this time it seems screen reader users have the most user agent solutions
using the AT. But keyboard-only, non-screen reader users are less fortunate.
Frames are considered a method and are accessible to keyboard users.
- Next message in Thread: Andi Snow-Weaver: "Re: Group D: 22(o) Skip navigation"
- Previous message in Thread: David Poehlman: "Re: Group D: 22(o) Skip navigation"