Document Structure Roles
What you'll learn: How to use ARIA document structure roles to help assistive technologies understand the organization and relationship of content within your web pages.
The Core Idea
While landmark roles (from lesson 1015) help users navigate between major sections, document structure roles describe how content is organized within those sections. They tell screen readers "this is an article," "this is a heading," "this is a list," or "this is a table" — crucial information for users who can't see visual formatting.
Think of it like markup for a printed magazine: headings, article boundaries, lists, and tables are visually obvious, but someone listening to the content needs explicit labels to understand the same structure.
The Four Key Document Structure Roles
role="article"
Marks a self-contained composition (blog post, news story, forum post). Helps screen readers identify complete units of content.
role="heading"
Identifies heading text when you can't use semantic <h1>–<h6>. Requires aria-level to specify hierarchy (1-6).
role="list" and role="listitem"
Recreates list semantics when CSS or custom markup removes default list styling or structure.
role="table", role="row", role="cell"
Provides table semantics for data grids built with <div> elements instead of proper <table> markup.
When to Use These
Best practice: Use semantic HTML first (<article>, <h1>, <ul>, <table>). Only apply these ARIA roles when you must override native semantics or when using non-semantic elements for complex components.
For example, if you build a custom data grid with divs for styling flexibility, role="table" ensures screen readers still announce it as a table structure.
Key Takeaway: Document structure roles like article, heading, list, and table enhance content organization for assistive technologies, but always prefer native semantic HTML elements over ARIA when possible.