diff options
Diffstat (limited to 'build/skip-to-content')
| -rw-r--r-- | build/skip-to-content/index.html | 20 |
1 files changed, 2 insertions, 18 deletions
diff --git a/build/skip-to-content/index.html b/build/skip-to-content/index.html index 7a72d31..9252e85 100644 --- a/build/skip-to-content/index.html +++ b/build/skip-to-content/index.html @@ -3,11 +3,12 @@ <head> <meta charset="utf-8"> <meta name="viewport" content="width=device-width, initial-scale=1"> + <meta name="color-scheme" content="dark light"> <link rel="icon" href="data:,"> <title>Skip to Content Button</title> <link href="/atom.xml" type="application/atom+xml" rel="alternate" title="Atom feed for blog posts" /> <link href="/rss.xml" type="application/rss+xml" rel="alternate" title="RSS feed for blog posts" /> -<style>*{box-sizing:border-box;}body{font-family:sans-serif;line-height:1.33;margin:0 auto;max-width:650px;padding:1rem;}img{max-width:100%;}pre{border:1px solid;overflow:auto;padding:5px;}table{text-align:left;width:100%;}.footnotes{font-size:90%;}</style> +<style>*{box-sizing:border-box;}body{font-family:sans-serif;line-height:1.33;margin:0 auto;max-width:650px;padding:1rem;}blockquote{background:rgba(0,0,0,0.1);border-left:4px solid;padding-left:5px;}img{max-width:100%;}pre{border:1px solid;overflow:auto;padding:5px;}table{text-align:left;width:100%;}.footnotes{font-size:90%;}</style> </head> <nav> @@ -16,22 +17,15 @@ <main> <h1 id="skip-to-content-button">Skip to Content Button</h1> - <p>2019-03-25</p> - <p>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.</p> - <p>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:</p> - <ul> <li>speeds up user interaction with the content you <strong>want</strong> them to see</li> <li>on subsequent pages the user shouldn’t need to tab through the entire navigation each time</li> </ul> - <h2 id="the-html">The HTML</h2> - <p>For the sake of this demo we will assume that we currently have the following navigation setup in our project:</p> - <pre><code><nav role="navigation"> <a href="/">Home</a> <a href="/about">About</a> @@ -39,9 +33,7 @@ <a href="/atom.xml">RSS</a> </nav> </code></pre> - <p>Now for the easy part - adding our simple content skip link with it’s own custom <code>skip-content</code> class:</p> - <pre><code><nav role="navigation"> <!-- Skip to content button --> <a class="skip-content" href="#main">Skip to Content (Press Enter)</a> @@ -51,11 +43,8 @@ <a href="/atom.xml">RSS</a> </nav> </code></pre> - <h2 id="the-css">The CSS</h2> - <p>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 <code>absolute</code> position style instead of setting the display property to <code>none</code>, since the display property technique will fully remove the element from the DOM (bad accessibility practices).</p> - <pre><code>a.skip-content { background: grey; color: white; @@ -65,18 +54,13 @@ top: 0; } </code></pre> - <h2 id="almost-there">Almost there</h2> - <p>Now we just re-position the element when the user focuses on the link with a keyboard tab:</p> - <pre><code>a.skip-content:focus { left: 1rem; /* Whatever desired position */ } </code></pre> - <h2 id="all-done">All Done</h2> - <p>This is a very basic accessibility win you can implement in your current projects with next to zero effort. Enjoy!</p> <footer role="contentinfo"> <h2>Menu Navigation</h2> |