WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: "Skip to content" links, vissibility and keyboard users without screen readers, to hide or not to hide?

for

From: Jared Smith
Date: Sep 15, 2011 3:21PM

On Thu, Sep 15, 2011 at 2:32 PM, David Ashleydale < <EMAIL REMOVED> > wrote:
> This is really nice, but in both Chrome 13 and IE 8 on a PC (XP), when I
> pressed Enter on the skip link it took me to the main content, but then
> hitting Tab again took me back up to the top of the page instead of the "I
> am another link.", which I think is where it should go.

As I noted, Chrome and Safari do not properly support in-page links.
It visually scrolls the page to the target element, but keyboard tab
focus remains on the "skip" link. Hitting Tab again reverts you back
to the top of the page. Hopefully these long-standing issues will be
resolved soon.

For IE8, this fits into my "*mostly* been addressed" disclaimer. IE8
still has cases where it does not change the keyboard tab focus for
in-page links. This can usually be resolved by using a named anchor
(<a id="maincontent" name="maincontent">), placing the target for the
link in an element that triggers hasLayout (a small book couldn't
adequately explain this, so suffice this to mean a table or certain
elements with a defined height), or by adding tabindex="-1" to the
target element.

I have updated the example to add tabindex="-1" to the target <div>
element so that it will work in that silly thing called IE8. Also of
note is that IE8 doesn't fully support the CSS3 stuff, but it is still
fully functional, just without the nifty animations, rounded corners,
etc.

Jared