81. Accessible web design
Module 17 · About 20 minutes · Lesson 80; review earlier concepts as needed
Open Interactive LessonDiscover
What changes when you use accessible web design, and how can you prove it?
- Explain accessible web design using the example source
- Predict the visual or structural effect of one controlled change
- Repair the supplied fault and verify actual output
Predict
Record the expected structure or visual change before rendering. Name one thing that should remain unchanged.
Understand
Accessibility includes perceivable information, operable controls, understandable content and robust structure. Native HTML often supplies useful behavior and semantics, but quality depends on the entire interaction. A div with a click handler is not equivalent to a button. Automated audits can detect some objective issues; manual keyboard and assistive-technology testing remains essential.
Important source lines
- index.html:1 <h1>Accessible actions</h1><button type="button">Preview report</button><p>Use a real button for an action.</p>
- The highest-level heading for a page topic. Attribute guidance: global attributes.
- styles.css:1 button { padding:.75rem 1rem; } button:focus-visible { outline:3px solid #234f9b; outline-offset:3px; }
- Creates internal space between content and border. Accepted grammar: <'padding-top'>{1,4}. Context: block.
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 web design
The action is a native focusable button with keyboard activation behavior and a visible focus rule.
index.html
<h1>Accessible actions</h1><button type="button">Preview report</button><p>Use a real button for an action.</p>
styles.css
button { padding:.75rem 1rem; } button:focus-visible { outline:3px solid #234f9b; outline-offset:3px; }script.js
Expected: The action is a native focusable button with keyboard activation behavior and a visible focus rule.
Edit and Render This ExampleExample 2: 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 ExampleExample 3: 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 ExampleExample 4: 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 ExampleExample 5: Accessible profile dialog
A native modal dialog places the rest of the document behind a modal boundary. Name the dialog, move focus to a sensible first control, and restore it when the task ends.
index.html
<section data-component aria-label="Accessible profile dialog"> <button id="launch">Edit profile</button> <dialog id="panel" aria-labelledby="heading"> <h2 id="heading">Edit profile</h2> <label>Display name <input id="name" value="Ari"></label> <button id="close">Close dialog</button> </dialog> </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; }
dialog { max-width: min(28rem, calc(100% - 2rem)); border: 1px solid #8296aa; border-radius: .7rem; } dialog::backdrop { background: #142537aa; }script.js
const root=document.querySelector("[data-component]");
const launch = root.querySelector("#launch");
const panel = root.querySelector("#panel");
launch.addEventListener("click", () => {
panel.showModal();
root.querySelector("#name").focus();
});
root.querySelector("#close").addEventListener("click", () => panel.close());
panel.addEventListener("keydown", event => {
if (event.key === "Escape") {
event.preventDefault();
panel.close();
}
});
panel.addEventListener("close", () => launch.focus());Expected: Add a second field, decide where initial focus should go, and verify Escape and Close still return to the trigger.
Edit and Render This ExampleBuild and test
The action is a native focusable button with keyboard activation behavior and a visible focus rule. Repair the current exercise without removing necessary content. Checks inspect the stated structural/computed/stylesheet contract, not exact source text.
Starter index.html
<h1>Accessible actions</h1><div>Preview report</div><p>Use a real button for an action.</p>
Starter styles.css
button { padding:.75rem 1rem; } button:focus-visible { outline:3px solid #234f9b; outline-offset:3px; }Objective contract
[
{
"type": "count",
"selector": "button[type=\"button\"]",
"value": 1,
"label": "Include 1 matching button[type=\"button\"] element(s)"
}
]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 <button type="button">Preview report</button>. The exercise instead uses <div>Preview report</div>. Identify its effect before changing it.
Hint 3
Restore the intended <button type="button">Preview report</button> operation or implement an equivalent structure/style. Run the actual checks and explain why it works.
Complete reference solution
index.html
<h1>Accessible actions</h1><button type="button">Preview report</button><p>Use a real button for an action.</p>
styles.css
button { padding:.75rem 1rem; } button:focus-visible { outline:3px solid #234f9b; 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 action is a native focusable button with keyboard activation behavior and a visible focus rule.
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
- Explain this lesson’s source line by line using the actual objective above.
- Help implement one small extension and define normal, boundary and failure tests.
- Review/debug the source against actual preview observations; verify standards and never claim rendering without evidence.