Accessible Name
An accessible name is the label software computes for a control or image. Screen readers use it to identify the item.
Another example
A screen-reader user reaches an icon-only transfer button. Its accessible name is “Transfer NT$2,400,” and the decorative icon beside it has no name. When the amount changes, the name changes too.
Main parts
- 01Name source
- 02Referenced text
- 03Computed result
Use it when
Give each control and meaningful image a short, clear name. Make nearby items easy to tell apart.
Do not use it when
Do not repeat visible text in aria-label. Do not name decorative items, because screen readers would announce extra or conflicting words.
Name used in code
label, alt, aria-labelledby, or aria-label in the accessible-name computation Before you ship
Give assistive tools the control’s name (accessible name), purpose (role), value, and state. Check keyboard use, visible focus, target size, disabled and busy states, feedback, and recovery.
Outcome: Use Accessible Name to solve this user need without losing the current context. User context: A screen-reader user reaches an icon-only transfer button. Its accessible name is “Transfer NT$2,400,” and the decorative icon beside it has no name. When the amount changes, the name changes too. Recommended pattern: Accessible Name. Why it fits: Give each control and meaningful image a short, clear name. Make nearby items easy to tell apart. Do not use it when: Do not repeat visible text in aria-label. Do not name decorative items, because screen readers would announce extra or conflicting words. Product requirements: Define the default, loading, empty, error, success, and recovery states. Keep user input. Give clear feedback after every action. Accessibility and resilience: Use semantic HTML, full keyboard access, and visible focus. Make the layout work when zoomed and support reduced motion. Follow the project’s current rules. Do not add a new UI library unless the project already uses it. Acceptance criteria: The main task works with keyboard only and at 320px width. Focus and status changes are announced. Check loading, failure, retry, cancel, and reduced-motion paths. Evidence and limits (evidence boundary): The standard covers only the listed scope. It does not choose the visual style, product decision, or Vibulary example. Unknowns to confirm: Product wording, data source, analytics events, supported devices and languages, and platform limits.
Check this request
Review the current use of Accessible Name. Definition: An accessible name is the label software computes for a control or image. Screen readers use it to identify the item. Release checks: Give assistive tools the control’s name (accessible name), purpose (role), value, and state. Check keyboard use, visible focus, target size, disabled and busy states, feedback, and recovery. Before changing code, report the evidence you found, gaps, severity, and the smallest safe fix.