# Screen Reader Design

Screen reader design creates meaningful structure, names, states, order, and feedback that assistive technology can present nonvisually.

- Type: practice
- Domain: Experience & interface
- Level: Advanced
- Last reviewed: 2026-09-21
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/screen-reader-design/>)

## What it means

Screen readers use platform accessibility APIs derived from semantic HTML, accessible names, roles, properties, states, relationships, and live updates. Designing for them means specifying this nonvisual interface alongside the visual one, while preferring native semantics over custom ARIA.

## Why it matters

Visual layout alone communicates hierarchy, grouping, status, and control purpose to many users. If those relationships are absent or misleading in code, screen-reader users may encounter unlabeled controls, noisy repetition, silent changes, or an order that does not match the task.

## When to use it

Include screen-reader behavior when designing forms, icons, tables, navigation, dialogs, validation, asynchronous updates, and custom widgets. Test common task paths with more than one relevant browser and screen-reader combination when risk justifies it.

## How it works

1. Define a logical document outline, landmarks, lists, tables, labels, and reading order.
2. Give controls concise accessible names that match visible language and expose state.
3. Prefer native elements; use ARIA only to supply semantics HTML cannot provide.
4. Specify what dynamic updates should announce and avoid excessive live-region noise.
5. Keep hidden, disabled, loading, and error states understandable nonvisually.
6. Inspect the accessibility tree and test real tasks with screen readers and users.

## A practical example

An icon-only mute button has the accessible name “Mute,” exposes its pressed state, and updates to “Unmute” consistently with the visible tooltip. Joining a call announces the new status once, while decorative participant animations remain hidden from the accessibility tree.

## Where it breaks

Screen readers differ by platform, settings, browser, and user skill. Passing one scripted test does not represent all users, and adding ARIA can make native semantics worse. Nonvisual access must be evaluated together with keyboard operation and clear content.

## Common mistakes

- Using placeholder text as the only field label.
- Adding redundant ARIA roles or names to semantic elements.
- Announcing every visual update through an assertive live region.
- Hiding focused content with aria-hidden.
- Writing accessible names that do not match visible labels.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/screen-reader-design/#visualization-screen-reader-design>)

## Sources

1. [ARIA Authoring Practices Guide](<https://www.w3.org/WAI/ARIA/apg/>) — W3C Web Accessibility Initiative · Technical guidance
2. [Providing Accessible Names and Descriptions](<https://www.w3.org/WAI/ARIA/apg/practices/names-and-descriptions/>) — W3C Web Accessibility Initiative · Technical guidance
3. [Introduction to Web Accessibility](<https://www.w3.org/WAI/fundamentals/accessibility-intro/>) — W3C Web Accessibility Initiative · Institutional guidance

## Related topics

- [Focus Management](<https://wiki.soroush.uk/topic/focus-management/>)
- [Keyboard Accessibility](<https://wiki.soroush.uk/topic/keyboard-accessibility/>)
- [Accessibility](<https://wiki.soroush.uk/topic/accessibility/>)
