Thread Subject: Re: Bypassing content.
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: Andrew Kirkpatrick
Date: Tue, Jun 12 2007 2:50 PM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: Sailesh Panchang: "Re: Bypassing content."
- Previous message in thread: Sailesh Panchang: "Re: Bypassing content."
- Messages sorted by: Author | Thread | Date
And I don't have any problem with a developer using a skip link as a way
to address this standard. What I'd like to avoid is the requirement
that to meet this technique the feature that allows you to skip around
be visible, since for some success techniques that are in current use
would then fail.
AWK
> -----Original Message-----
> From: = EMAIL ADDRESS REMOVED =
> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf
> Of Sailesh Panchang
> Sent: Tuesday, June 12, 2007 4:34 PM
> To: 'TEITAC Web/Software Subcommittee'
> Subject: Re: [teitac-websoftware] Bypassing content.
>
> >The skip nav link offers very poor control - you get one option and
> >that is to move focus to where the link is and nowhere else.
> Well that is what all links do- move focus to a particular
> target. The skip nav link moves focus to after end of group
> of links or repetitive block of content if one prefers that.
> It never purported to do anything else and is an effective
> vehicle for that. It is but one option when other structural
> markup is absent.
>
> Sailesh Panchang
> Senior Accessibility Engineer
> Deque Systems Inc. (www.deque.com)
> 11130 Sunrise Valley Drive, Suite #140,
> Reston VA 20191
> Phone: 703-225-0380 (ext 105)
> E-mail: = EMAIL ADDRESS REMOVED =
>
>
- Next message in Thread: Sailesh Panchang: "Re: Bypassing content."
- Previous message in Thread: Sailesh Panchang: "Re: Bypassing content."
WebAIM is an initiative of:
