Writing Accessible Gridcell Labels
Writing Accessible Gridcell Labels records a distinct W3C-supported interface-content task while keeping implementation mechanics outside the writing guidance.
Let meaningful visible cell content provide the gridcell name; add a separate accessible name only when the cell’s content is insufficient.
Key details
Important caveats
Scope Boundary
This page does not require labels for empty cells and does not treat row or column headers as the gridcell’s own accessible name.
Further guidance
Content
Keep cell wording aligned with the visible data or control it contains so the cell remains understandable in the grid context.
Practical Application
Let concise visible cell content provide the gridcell name when it already identifies the value; add a separate accessible name only when the visible content is insufficient or intentionally absent.
Purpose
Clear wording helps assistive-technology users understand the component or content in context without relying on implementation details.
Reader Check
Would a separate label add real meaning, or would it simply repeat the cell’s visible text and make navigation more verbose?
Worked Example
Example: A cell visibly containing “Pending” can normally use that text as its name; an icon-only cell may need a label such as “High priority.”
Sources and evidence
Sources are shown with the role they play in this guide. Historical or style-sensitive claims are kept within the evidence boundary described above.
- Providing Accessible Names and Descriptions — W3C WAI ARIA APG (opens in a new tab)W3C Web Accessibility Initiative · W3C WAI-ARIA Authoring Practices guidance for descriptive accessible names, visible labels, and button/control naming.