Writing & StyleStyle guide

Writing Accessible Gridcell Labels

Writing Accessible Gridcell Labels records a distinct W3C-supported interface-content task while keeping implementation mechanics outside the writing guidance.

Quick answer

Let meaningful visible cell content provide the gridcell name; add a separate accessible name only when the cell’s content is insufficient.

Key details

Core IssueW3C APG says a gridcell is ideally named by its visible descendant content and does not require a separate name when that content is sufficient; an empty cell may legitimately have an empty name.
Registerweb accessibility and interface content

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.

Purpose

Clear wording helps assistive-technology users understand the component or content in context without relying on implementation details.

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.

  1. 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.

Explore the topic