DiscoveryVIP / HTML & CSS AcademyHelp

83. Keyboard-accessible navigation

Module 17 · About 20 minutes · Lesson 82; review earlier concepts as needed

Open Interactive Lesson

Discover

What changes when you use keyboard-accessible navigation, and how can you prove it?

Predict

Record the expected structure or visual change before rendering. Name one thing that should remain unchanged.

Understand

Links and buttons participate in native keyboard interaction. Preserve a sensible DOM order, visible focus and reachable destinations. Do not add positive tabindex values to patch a confusing source order. A collapsed custom navigation needs actual toggle behavior and state, not only a menu-shaped icon. The native disclosure examples provide a complete keyboard-capable starting point.

Important source lines

index.html:1 <nav aria-label="Sections"><a href="#intro">Introduction</a><a href="#practice">Practice</a></nav><main><section id="intro"><h1>Keyboard path</h1></section><section id="practice"><h2>Practice</h2></section></main>
A major navigation region with real destinations. Attribute guidance: aria-label when distinguishing multiple regions.
styles.css:1 a:focus-visible { outline:3px solid #234f9b; outline-offset:4px; }
This line groups or completes the surrounding structure. Inspect its actual parent/child relationship and compare with the lesson explanation.

The first example teaches this lesson’s primary contract. Additional examples are optional related references or applications, each with its own purpose and source; an example without an authored check requires the stated visual/manual review.

Example 1: Keyboard-accessible navigation

Keyboard focus remains visible on each native link, and destinations exist in source order.

index.html

<nav aria-label="Sections"><a href="#intro">Introduction</a><a href="#practice">Practice</a></nav><main><section id="intro"><h1>Keyboard path</h1></section><section id="practice"><h2>Practice</h2></section></main>

styles.css

a:focus-visible { outline:3px solid #234f9b; outline-offset:4px; }

script.js

Expected: Keyboard focus remains visible on each native link, and destinations exist in source order.

Edit and Render This Example
Example 2: Property: outline

Draws an outline without consuming normal box-model space.

index.html

<section class="stage"><article class="sample"><h2>Readable content</h2><p>Longer sample text demonstrates wrapping, spacing and typography. Change a value, inspect its computed style and compare the resulting box.</p><a href="#details">Read the details</a></article><article class="peer">A second item</article></section><section id="details"><h2>Details</h2></section>

styles.css

body { font:18px/1.5 system-ui; color:#17324d; margin:1rem; }
.stage { padding:1rem; border:1px dashed #9caec0; } .sample { padding:1rem; border:2px solid #849ab1; max-width:30rem; }
.sample { outline: 3px solid #a44322; }

script.js

Expected: Inspect .sample in the block context. Draws an outline without consuming normal box-model space. The browser’s CSS.supports and computed-style report are the authority for this installed browser; a declaration can be valid but depend on additional layout or font conditions.

Edit and Render This Example
Example 3: Property: outline-offset

Separates an outline from the element’s edge.

index.html

<section class="stage"><article class="sample"><h2>Readable content</h2><p>Longer sample text demonstrates wrapping, spacing and typography. Change a value, inspect its computed style and compare the resulting box.</p><a href="#details">Read the details</a></article><article class="peer">A second item</article></section><section id="details"><h2>Details</h2></section>

styles.css

body { font:18px/1.5 system-ui; color:#17324d; margin:1rem; }
.stage { padding:1rem; border:1px dashed #9caec0; } .sample { padding:1rem; border:2px solid #849ab1; max-width:30rem; }
.sample { outline-offset: 5px; }

script.js

Expected: Inspect .sample in the block context. Separates an outline from the element’s edge. The browser’s CSS.supports and computed-style report are the authority for this installed browser; a declaration can be valid but depend on additional layout or font conditions.

Edit and Render This Example
Example 4: Article card

Use a heading and explicit action inside an article. This keeps interactive controls independent.

index.html

<section data-component aria-label="Article card">
<article><h2>Canvas basics</h2><p>Draw a shape and test its bounds.</p><button id="save">Save guide</button><p id="saved" role="status"></p></article>
</section>

styles.css

* { box-sizing: border-box; }
body { margin: 0; color: #142537; background: #eef4fa; font: 16px/1.5 system-ui, sans-serif; }
[data-component] { max-width: 44rem; margin: 1rem auto; padding: 1rem; border: 1px solid #a1b2c4; border-radius: .75rem; background: white; }
button, input, select, textarea { font: inherit; padding: .4rem .65rem; margin: .2rem; }
button { cursor: pointer; } :focus-visible { outline: 3px solid #a33e0c; outline-offset: 3px; }
label { display: block; } [hidden] { display: none !important; }
table { border-collapse: collapse; } th, td { padding: .4rem; border-bottom: 1px solid #a1b2c4; }

script.js

const root=document.querySelector("[data-component]");
root.querySelector('#save').onclick=()=>{root.querySelector('#saved').textContent='Guide saved';};

Expected: Add a second independent action with a distinct name.

Edit and Render This Example
Example 5: Property: padding

Creates internal space between content and border.

index.html

<section class="stage"><article class="sample"><h2>Readable content</h2><p>Longer sample text demonstrates wrapping, spacing and typography. Change a value, inspect its computed style and compare the resulting box.</p><a href="#details">Read the details</a></article><article class="peer">A second item</article></section><section id="details"><h2>Details</h2></section>

styles.css

body { font:18px/1.5 system-ui; color:#17324d; margin:1rem; }
.stage { padding:1rem; border:1px dashed #9caec0; } .sample { padding:1rem; border:2px solid #849ab1; max-width:30rem; }
.sample { padding: 24px; }

script.js

Expected: Inspect .sample in the block context. Creates internal space between content and border. The browser’s CSS.supports and computed-style report are the authority for this installed browser; a declaration can be valid but depend on additional layout or font conditions.

Edit and Render This Example

Build and test

Keyboard focus remains visible on each native link, and destinations exist in source order. Repair the current exercise without removing necessary content. Checks inspect the stated structural/computed/stylesheet contract, not exact source text.

Starter index.html

<nav aria-label="Sections"><a href="#intro">Introduction</a><a href="#practice">Practice</a></nav><main><section id="intro"><h1>Keyboard path</h1></section><section id="practice"><h2>Practice</h2></section></main>

Starter styles.css

a:focus-visible { outline:none; outline-offset:4px; }

Objective contract

[
  {
    "type": "rule",
    "selector": "a:focus-visible",
    "property": "outline",
    "value": "3px solid #234f9b",
    "label": "a:focus-visible declares outline: 3px solid #234f9b"
  }
]
Hint 1

Locate the first difference between the intended result and the real preview. Inspect matching elements and computed styles.

Hint 2

The relevant source uses outline:3px solid #234f9b. The exercise instead uses outline:none. Identify its effect before changing it.

Hint 3

Restore the intended outline:3px solid #234f9b operation or implement an equivalent structure/style. Run the actual checks and explain why it works.

Complete reference solution

index.html

<nav aria-label="Sections"><a href="#intro">Introduction</a><a href="#practice">Practice</a></nav><main><section id="intro"><h1>Keyboard path</h1></section><section id="practice"><h2>Practice</h2></section></main>

styles.css

a:focus-visible { outline:3px solid #234f9b; outline-offset:4px; }

Explain, reflect and extend

Which part of the actual preview or inspector proves this result? Explain one boundary case and name what automated checks do not verify.

Apply this concept to a different realistic piece of content. Predict its structure or visual behavior, test narrow and wide widths where relevant, then record one invalid case and its repair.

Troubleshooting and professional practice

If nothing changes, confirm that you edited the active file and ran Run Preview, or enabled Auto Preview. Inspect the actual DOM because the browser may repair invalid nesting. For CSS, check selector matches, valid declarations, active queries and computed values. Preserve local asset paths and inspect warnings. Keyboard focus remains visible on each native link, and destinations exist in source order.

Knowledge check

Explain why the stated result follows from the source. Predict a second input or width and test it independently. Automated contracts and written explanations are reviewed separately.

Optional AI prompts

  1. Explain this lesson’s source line by line using the actual objective above.
  2. Help implement one small extension and define normal, boundary and failure tests.
  3. Review/debug the source against actual preview observations; verify standards and never claim rendering without evidence.

Continue to Lesson 84: Accessible forms and controls

Detailed learning and editor help · Standards reference