WAI-ARIA APG: Grid Pattern
Defines grid as an interactive composite widget with one item in the page tab sequence, managed focus movement, data-grid versus layout-grid distinctions, arrow/Home/End/Page navigation, selection shortcuts, editing entry and exit conventions, grid roles, aria-sort, aria-selected, aria-readonly, and row or column count and index properties.
What this source can teach
Use this source to check a technical or accessibility requirement against its exact wording and scope.
- Start with the original. Open the source and find the guidance or example relevant to your task.
- Trace the connection. Use the claim notes below to see how this site applies the source to specific patterns.
- Check the setting. Compare the source's platform, people, and constraints with your own decision.
Pattern Decisions This Source Supports
| Pattern | Supported decision | Required contract | Claim note |
|---|---|---|---|
| Data grid | Choose data grid when row-and-column data is interactive enough to require managed cell focus, arrow-key movement, selection, editing, or keyboard shortcuts. | Tab moves into the grid at one managed focus point and out to the next page control rather than visiting every cell by default. | APG grid guidance supports the core data-grid interaction model, keyboard navigation, editing boundary, selection, focus management, and ARIA roles and states. |
Comparisons supported by this source
- Data grid vs table vs inline edit vs pagination
APG grid guidance supports the data-grid boundary, keyboard model, focus management, editing, selection, roles, and ARIA state requirements.
Evidence Role
This source is treated as spec evidence. Its value comes from the specific claims and setting described above.
Publisher: W3C Web Accessibility Initiative. Last checked: .