blob: 1d722ccb0251c91191b72be0de2c82144e9bdf4c (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
|
---
layout: post
title: "Skip to Content Button"
date: 2019-03-25
---
One of the golden rules for testing your website's accessibility is the "keyboard-only" audit. This is where you test navigating through your entire site without the use of a mouse, but instead rely solely on tabbing through your content.
Unfortunately, one item is normally overlooked during this audit - a "skip to content" context button. Including a "skip to content" navigation item in your project is extremely useful because:
- speeds up user interaction with the content you **want** them to see
- on subsequent pages the user shouldn't need to tab through the entire navigation each time
## The HTML
For the sake of this demo we will assume that we currently have the following navigation setup in our project:
<nav role="navigation">
<a href="/">Home</a>
<a href="/about">About</a>
<a href="/archive">Archive</a>
<a href="/atom.xml">RSS</a>
</nav>
Now for the easy part - adding our simple content skip link with it's own custom `skip-content` class:
<nav role="navigation">
<!-- Skip to content button -->
<a class="skip-content" href="#main">Skip to Content (Press Enter)</a>
<a href="/">Home</a>
<a href="/about">About</a>
<a href="/archive">Archive</a>
<a href="/atom.xml">RSS</a>
</nav>
<div class="message">
<strong>Sidenote:</strong> in this demo we are making the assumption that the main content block has an <code>id</code> of "main" associated with it. Hence the skip content button linking to <code>#main</code>.
</div>
## The CSS
Our first task is to make sure this new link isn't visible or interactive by default unless the user explicitly tabs through the navigation. We do so by positioning the link outside of the main content view. It is important to use this `absolute` position style instead of setting the display property to `none`, since the display property technique will fully remove the element from the DOM (bad accessibility practices).
a.skip-content {
background: grey;
color: white;
left: -9999px;
padding: 0.5rem;
position: absolute;
top: 0;
}
## Almost there
Now we just re-position the element when the user focuses on the link with a keyboard tab:
a.skip-content:focus {
left: 1rem; /* Whatever desired position */
}
## All Done
This is a very basic accessibility win you can implement in your current projects with next to zero effort. Enjoy!
|
