[WSG] Heads up re: skipNav and other jump links
Hi all, I've noticed that many of you are using a container ID as a named anchor (to create a skip nav for example), but I'm not sure if you're all aware that this creates an accessibility issue: the user can jump to the location, but is unable to tab past it. Also, I've found that most of the techniques work when it comes to the jumping part, but making sure tabbing navigation is not disturbed is not that simple. For example it appears that a name=content/a is not bullet proof while a href=# name=content/a is. I've also noticed that if one uses display:none to style a named anchor, MSIE can't find its location (FF seems to be OK with it). One last thing: for the UA, case is not an issue, so a jump link (#content) would work, but tabbing navigation would fail if the anchor named content is contained in a DIV named CONTENT. Anybody knows why empty anchors are not 100% reliable when it comes to tabbing navigation? I just can't figure it out... Regards, Thierry | http://www.TJKDesign.com ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
RE: [WSG] Heads up re: skipNav and other jump links
I've been replacing my a name=deepcontent/a with h3 id=deepcontent Or something similar. Isn't that the most appropriate way of going? Are you saying this would cause accessibility issues with tabbing? I thought name was deprecated. Ted -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Thierry Koblentz Sent: Thursday, April 21, 2005 3:31 PM To: wsg@webstandardsgroup.org Subject: [WSG] Heads up re: skipNav and other jump links Also, I've found that most of the techniques work when it comes to the jumping part, but making sure tabbing navigation is not disturbed is not that simple. For example it appears that a name=content/a is not bullet proof while a href=# name=content/a is. ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] Heads up re: skipNav and other jump links
Drake, Ted C. wrote: I've been replacing my a name=deepcontent/a with h3 id=deepcontent Or something similar. Isn't that the most appropriate way of going? Hi Ted, Try the 2 methods and you'll see how the latter solution disturbs tabbing navigation. Using the former allows UAs to jump to that location, but once there, the user cannot tab *from there*. On her next tab, she is brought back to where she comes from, or even farther up. Thierry | http://www.TJKDesign.com ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
