Writing & StyleStyle guide

Writing Accessible Disclosure Button Labels

Writing Accessible Disclosure Button Labels narrows the queued intent to disclosure-specific context and naming, rather than duplicating the engine’s general accessible-button-label guidance.

Quick answer

Keep a disclosure button label concise but sufficiently descriptive; when “Details” alone is ambiguous, include the related item or heading in its accessible name.

Key details

Core IssueW3C APG’s disclosure-card example emphasizes a disclosure button accessible name that is brief, understandable, and sufficiently descriptive in context.
Registerweb accessibility and interface content

Important caveats

Scope Boundary

This page covers disclosure-control wording; aria-expanded, click targets, focus placement, and animation behavior are implementation concerns.

Further guidance

Content

Write a disclosure-button label that names the reveal/hide action or content clearly enough to make sense with its surrounding context; add contextual naming when a generic word such as “Details” would be ambiguous.

Purpose

A concise but context-rich disclosure label helps users understand which hidden content a show/hide control affects.

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. Disclosure (Show/Hide) Card Example — WAI-ARIA Authoring Practices Guide (opens in a new tab)World Wide Web Consortium (W3C) · W3C APG example guidance for concise, understandable disclosure-button accessible names with sufficient context.

Related guides

Writing & Style

Writing Accessible Button Labels

Writing Accessible Button Labels records accessibility-focused writing guidance from the named standards body while keeping implementation and wording advice separate from unrelated general style rules.

Writing & Style

Writing Accessible Radio Button Labels

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

Explore the topic