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 #9

Tabular Data: Making Tables Comprehensible

Tables are intended for relational tabular data, never for page layout.

When a screen reader traverses a well-structured data table, it continuously announces the column and row headers corresponding to the current cell:

<table>
  <caption>Employee Quarterly Sales Performance (2026)</caption>
  <thead>
    <tr>
      <th scope="col">Employee</th>
      <th scope="col">Region</th>
      <th scope="col">Revenue</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <th scope="row">Elena Rostova</th>
      <td>Northern Europe</td>
      <td>$142,000</td>
    </tr>
  </tbody>
</table>

Key Elements:

  • <caption>: The title of the table announced upon entry.
  • <th scope="col"> and <th scope="row">: Explicitly ties data cells to their parent headers.

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