Writing & StyleStyle guide

Writing Accessible Article Labels

Writing Accessible Article Labels records a distinct W3C-supported accessible-naming task and keeps implementation mechanics outside the writing guidance.

Quick answer

When multiple article regions need distinction, use a concise name based on each article’s own visible title or unique subject.

Key details

Core IssueW3C APG recommends naming article roles when a name is needed to distinguish articles from one another.
Registerweb accessibility and interface content

Important caveats

Scope Boundary

This page covers general article-region naming; feed-specific article naming remains owned by the existing feed-article guide.

Further guidance

Content

Prefer visible article heading text as the naming basis when it already identifies the article; keep labels short and unique enough to distinguish peers.

Practical Application

When multiple article regions need separate accessible names, base each label on the article’s visible title or unique subject so users can distinguish them.

Purpose

Distinct article names can make a collection of article regions easier to navigate and identify.

Reader Check

Are there multiple articles or repeated regions on the page? If a label is needed, does it match or closely reflect the visible article heading?

Worked Example

Example: For an article headed “Quarterly Results,” use the accessible label “Quarterly Results” rather than the generic “Article 1.”

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.

Related guides

Writing & Style

Writing Accessible Feed Article Labels

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

Explore the topic