Accessibility · Lesson 1 of 8 · 7 minutes

Accessibility: Accessible names

Visible text usually gives a native button its accessible name. Icon-only controls need an equivalent name.

Open the lab Course map

Mastery 0/3Run itExplain itApply it

Current edit

PreviewNo external resources

Your objectives

Hints are always available. Wrong turns never cost XP.

1
Build accessible names
Build this first target: <button> (type="button") containing “Save notes”. Inspect the structure before checking the lesson.
Hint & worked example
Visible text usually gives a native button its accessible name. Icon-only controls need an equivalent name.
The requested elements, attributes, content, and hierarchy exist outside comments.
```
<button type="button">Save notes</button>
```
Common mistake to avoid: A visual appearance alone guarantees the intended HTML meaning.
2
Extend the accessible names example
Extend your file to include: <button> (type="button") containing “Save notes”; <button> (type="button", aria-label="Close panel") containing “×”. Inspect the structure before checking the lesson.
Hint & worked example
Visible text usually gives a native button its accessible name. Icon-only controls need an equivalent name.
The requested elements, attributes, content, and hierarchy exist outside comments.
```
<button type="button">Save notes</button><button type="button" aria-label="Close panel">×</button>
```
Common mistake to avoid: Replacing semantic elements with generic divs automatically improves accessibility.
3
Verify the complete accessible names pattern
Finish the pattern with: <button> (type="button") containing “Save notes”; <button> (type="button", aria-label="Close panel") containing “×”; <p> containing “Controls have meaningful names.”. Inspect the structure before checking the lesson.
Hint & worked example
Visible text usually gives a native button its accessible name. Icon-only controls need an equivalent name.
The requested elements, attributes, content, and hierarchy exist outside comments.
```
<button type="button">Save notes</button><button type="button" aria-label="Close panel">×</button><p>Controls have meaningful names.</p>
```
Common mistake to avoid: A visual appearance alone guarantees the intended HTML meaning.

Understand the pattern

Visible text usually gives a native button its accessible name. Icon-only controls need an equivalent name.

Misconceptions to reject

A visual appearance alone guarantees the intended HTML meaning.
Replacing semantic elements with generic divs automatically improves accessibility.

The preview is a sanitized subset, not a full browser compatibility test.

Worked example and expected result

<button type="button">Save notes</button><button type="button" aria-label="Close panel">×</button><p>Controls have meaningful names.</p>

Visible text usually gives a native button its accessible name. Icon-only controls need an equivalent name.

Try a variation

Adapt the final example to a different project name while retaining its structure and relationships. A different context still needs a real browser and accessibility check.

Explain it

Which statement correctly explains accessible names?Replacing semantic elements with generic divs automatically improves accessibility.Visible text usually gives a native button its accessible name. Icon-only controls need an equivalent name.A visual appearance alone guarantees the intended HTML meaning.

Apply it elsewhere

You reuse accessible names in a different project. What must still be verified?The meaning, relationships, and accessible names in the new document.Nothing; passing a single exercise guarantees every future use.Only whether the source code has the same number of lines.

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Accessibility: Image alternatives Try an incident drill

Anonymous lesson and mastery progress lasts for this session. Sign in to keep synced lesson XP between sessions; mastery stays device-local. No speed bonus, lost lives, or hint penalties.

Keep learning

MDN: HTML structure