[Accessibleweb] Skip navigation link question; tabbing after going to anchor and jQuery fix

[Kevin Pittman]

My understanding is that you shouldn't need a "skip to content" link if you
have arrange your HTML such that the main content of the page comes before
the navigational links.

I'm not familiar with that jQuery solution so I can't really comment on
that. Good luck!

Kevin

On Jan 30, 2008 12:23 PM, Marcus Duke <mduke at u.washington.edu> wrote:


> In the process of coming more up to speed about web accessibility, I was

> reading about "skip navigation links." My question regards something Pace

> Arko said about arranging CSS divs in order of importance, such that content

> went first. Okay, so if we then put the main navigation links div at the end

> of the file, is the anchor link for skipping navigation links no longer

> necessary?

> Also, for the skip nav link, has anyone used the jQuery solution (

> http://www.ollicle.com/2006/nov/17/jquery_accessibility.html) to deal with

> tabbing vagaries once you've tabbed to an anchor link? If so, any insights

> to offer (e.g., did you encounter undocumented problems)?

>

> Marcus Duke

> Web Editor

> Washington Sea Grant

> mduke at u.washington.edu

> 206-685-0171

>

>

>

> _______________________________________________

> Accessibleweb mailing list

> Accessibleweb at u.washington.edu

> http://mailman1.u.washington.edu/mailman/listinfo/accessibleweb

>

>



-- 
Kevin Pittman, Information Architect
Catalyst Research & Development
Learning & Scholarly Technologies
University of Washington
206.616.8154

http://catalyst.washington.edu
http://solstice.eplt.washington.edu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman1.u.washington.edu/pipermail/accessibleweb/attachments/20080130/143171c0/attachment.htm