Skip links: the saga continues
19th October 2005
Some recent user testing of ours has suggested some ways to further improve the way we implement skip links.
Unlike many others, our recommended method of implementing skip links ensures that all keyboard users ’see’ the skip link, as it appears visually on screen when a user tabs to it, and is of course read out by screen readers. The problem is this — although they find it, many web users simply do not understand what a skip link does, let alone how to use one.
Our user testing suggests that (as ever) clearer instruction is the way forward, at least until users get more familiar with skip links.
Example: Instead of the text of the link reading Skip to Main Content, have it read Skip to Main Content — press enter to activate.
Having enticed the user into pressing enter and trying the skip link out, the next step is to ensure that the user knows what has happened to their keyboard focus. A previous suggestion of using the text Bookmark: Main Content can cause some confusion, with users thinking that pressing enter would bookmark the page. So, at the risk of incurring the wrath of those that like everything short and sweet, try this:
Example: Instead of using the word Bookmark, have the target of the skip link read Start of main content: read on from here or press tab to access the next link.
Now, I can already hear sharp intakes of breath: “That text is far too long! Surely users prefer something short and neat, it looks so much better on the screen and what about those poor screenreader users who have to listen to it on every page”. Well, the fact is that without clear instruction users will not use the link at all (no, before you ask, they hardly ever read that accessibility page you carefully drafted, and when they do they probably do not understand it, but that is a story for another post…). Let’s take these points one at a time:
- as the skip link and its target are only on screen when in use they do not take up precious screen real estate;
- once a user has figured out how the skip link works they will often not read what the link text says. Instead, they will just see/hear the start of the link, activate it and be on their way. Our testing suggests this is equally as true of screen reader users as it is fully-sighted keyboard users.
We will be trying this out over the next few months and let you know any feedback we get, in the meantime any comments are welcome!