DiscoveryVIP / HTML & CSS AcademyHelp

25. Accessible document structures

Module 5 · About 20 minutes · Lesson 24; review earlier concepts as needed

Open Interactive Lesson

Discover

What changes when you use accessible document structures, and how can you prove it?

Predict

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

Understand

Good document structure supports navigation by headings and landmarks, meaningful link text and sensible reading order. Visual columns should not require a different DOM sequence to make sense. A skip link needs a real target and visible focus treatment. Automated checks can find missing structure, but a person still needs to judge clarity and keyboard flow.

Important source lines

index.html:1 <a class="skip" href="#main">Skip navigation</a><nav aria-label="Primary"><a href="#main">Workshop guide</a></nav><main id="main" tabindex="-1"><h1>Accessible structure</h1><h2>Start here</h2><p>Follow the reading order.</p></main>
A hyperlink with a meaningful destination and link text. Attribute guidance: href; rel/target when relevant.
styles.css:1 a:focus-visible { outline: 3px solid #2457aa; outline-offset: 3px; }
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: Accessible document structures

The skip link reaches a meaningful main landmark; focus remains visibly indicated.

index.html

<a class="skip" href="#main">Skip navigation</a><nav aria-label="Primary"><a href="#main">Workshop guide</a></nav><main id="main" tabindex="-1"><h1>Accessible structure</h1><h2>Start here</h2><p>Follow the reading order.</p></main>

styles.css

a:focus-visible { outline: 3px solid #2457aa; outline-offset: 3px; }

script.js

Expected: The skip link reaches a meaningful main landmark; focus remains visibly indicated.

Edit and Render This Example
Example 2: Element: a

A hyperlink with a meaningful destination and link text.

index.html

<a href="#destination">Read the destination</a><section id="destination"><h1>Destination</h1></section>

styles.css

body { font:18px/1.6 system-ui; margin:1.5rem; color:#17324d; } img,video,svg { max-width:100%; height:auto; } th,td { padding:.5rem; border:1px solid #a8b8c8; } :focus-visible { outline:3px solid #a44322; outline-offset:3px; }

script.js

Expected: A hyperlink with a meaningful destination and link text. Review its real DOM and native behavior; structural/media-only examples are labeled.

Edit and Render This Example
Example 3: Element: nav

A major navigation region with real destinations.

index.html

<nav aria-label="On this page"><a href="#guide">Guide</a></nav><main id="guide"><h1>Guide</h1></main>

styles.css

body { font:18px/1.6 system-ui; margin:1.5rem; color:#17324d; } img,video,svg { max-width:100%; height:auto; } th,td { padding:.5rem; border:1px solid #a8b8c8; } :focus-visible { outline:3px solid #a44322; outline-offset:3px; }

script.js

Expected: A major navigation region with real destinations. Review its real DOM and native behavior; structural/media-only examples are labeled.

Edit and Render This Example
Example 4: Element: h2

A second-level heading for a major subsection.

index.html

<h1>Handbook</h1><section><h2>Getting started</h2><p>A named section.</p></section>

styles.css

body { font:18px/1.6 system-ui; margin:1.5rem; color:#17324d; } img,video,svg { max-width:100%; height:auto; } th,td { padding:.5rem; border:1px solid #a8b8c8; } :focus-visible { outline:3px solid #a44322; outline-offset:3px; }

script.js

Expected: A second-level heading for a major subsection. Review its real DOM and native behavior; structural/media-only examples are labeled.

Edit and Render This Example
Example 5: Element: h1

The highest-level heading for a page topic.

index.html

<h1>Workshop handbook</h1><p>A principal heading introduces the page.</p>

styles.css

body { font:18px/1.6 system-ui; margin:1.5rem; color:#17324d; } img,video,svg { max-width:100%; height:auto; } th,td { padding:.5rem; border:1px solid #a8b8c8; } :focus-visible { outline:3px solid #a44322; outline-offset:3px; }

script.js

Expected: The highest-level heading for a page topic. Review its real DOM and native behavior; structural/media-only examples are labeled.

Edit and Render This Example

Build and test

The skip link reaches a meaningful main landmark; focus remains visibly indicated. Repair the current exercise without removing necessary content. Checks inspect the stated structural/computed/stylesheet contract, not exact source text.

Starter index.html

<a class="skip" href="#absent">Skip navigation</a><nav aria-label="Primary"><a href="#main">Workshop guide</a></nav><main id="main" tabindex="-1"><h1>Accessible structure</h1><h2>Start here</h2><p>Follow the reading order.</p></main>

Starter styles.css

a:focus-visible { outline: 3px solid #2457aa; outline-offset: 3px; }

Objective contract

[
  {
    "type": "attr",
    "selector": "a.skip",
    "property": "href",
    "value": "#main",
    "label": "a.skip has href=#main"
  }
]
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 href="#main". The exercise instead uses href="#absent". Identify its effect before changing it.

Hint 3

Restore the intended href="#main" operation or implement an equivalent structure/style. Run the actual checks and explain why it works.

Complete reference solution

index.html

<a class="skip" href="#main">Skip navigation</a><nav aria-label="Primary"><a href="#main">Workshop guide</a></nav><main id="main" tabindex="-1"><h1>Accessible structure</h1><h2>Start here</h2><p>Follow the reading order.</p></main>

styles.css

a:focus-visible { outline: 3px solid #2457aa; outline-offset: 3px; }

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. The skip link reaches a meaningful main landmark; focus remains visibly indicated.

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 26: Forms and submissions

Detailed learning and editor help · Standards reference