Home
Bookmarks
Leagues
LEARN
Courses
Career Paths
Assessments
Tutorials
Arcade
Glossary
GROW
Certifications
Log in
Glossary
Log inSign up
Courses/Accessible Interface Foundations/Meaning before appearance/
Exercise #7

Lists as Navigation & Content Containers

Why do accessibility guidelines mandate that navigation menus, search result feeds, and bulleted features use semantic list tags (<ul>, <ol>, <li>) rather than stacks of <div> tags?

The Assistive Technology Experience: When a screen reader encounters a <ul> containing 6 <li> elements, it announces:

'List with 6 items. Item 1 of 6: Overview... Item 2 of 6: Analytics...'

This critical metadata tells the user:

  • Exactly how many choices exist in this collection.
  • Where they currently are within the group.
  • How to skip past the entire list with a single keystroke if they aren't interested in this menu.

Topics

Structure Carries Meaning: The Accessibility Tree
The Non-Negotiable Rule: Buttons vs Links
Document Outline: The Sacred Heading Hierarchy
Landmark Regions: Navigating Page Architecture
Form Labels: Why Placeholders Are Not Labels
The Alt Text Decision Tree: Informative vs Decorative
Lists as Navigation & Content Containers
The First Rule of ARIA: Do Not Use ARIA
Tabular Data: Making Tables Comprehensible
Master Challenge: Refactoring a 'Div-Soup' Component

From lesson

1

Meaning before appearance

Level 1 · Accessible interaction basics

Top contributors

Community contribution details will appear here once real learner activity is available.

Share