Guides

The team added labels, actions, Dynamic Type support and focus handling, and now asks how to check it without fooling itself. This is the short toolkit: a walkthrough on a device, Accessibility Inspector, the XCTest audit, snapshot tests, UI tests and an evidence record.

4 smells · 2 patterns · 2 chapters

A slider, a stepper, a page indicator, a rating or an amount picker needs .adjustable for VoiceOver. Adjustable is the right tool for one value that goes up and down. It's the wrong tool when the user picks an option by name.

1 patterns · 4 chapters

Leadership, product, legal or sales asks: "Why invest in accessibility when the roadmap is already full?"

2 smells · 4 patterns · 3 chapters

The project mentions ADA, the European Accessibility Act, the Web Accessibility Directive, EN 301 549 and WCAG, and the team expects one scanner report to answer all of it.

2 smells · 4 patterns · 4 chapters

The screen is long, every card has secondary actions, and a VoiceOver user needs 20 swipes for one action. The rotor and custom actions make that faster, and they're easy to overload. This guide shows what goes where.

2 smells · 3 patterns · 4 chapters

Touch works, and nobody knows how the screen behaves with Switch Control: how many steps it takes to reach the main button, whether scanning gets stuck in a list, whether secondary actions are reachable.

3 smells · 3 patterns · 3 chapters

A quick way to find bad control names: unnamed buttons, duplicates, vague names like "More", "Close", "Image" or "Button". Voice Control shows every name on screen at once, so a naming audit takes 2 minutes per screen.

2 smells · 2 patterns · 2 chapters

The screen has labels and still feels broken with VoiceOver: focus jumps, a swipe action is unreachable, a sheet can't be dismissed, the order fights the task, or QA can't reproduce a bug reliably. This is the gesture reference for product, design, developers and QA reviewing a screen.

4 smells · 5 patterns · 3 chapters

The screen looks fine and QA says "VoiceOver reads it strangely". This guide shows how to capture what VoiceOver actually says, find the broken part of the accessibility tree, and put reproducible evidence in the bug or the PR.

2 smells · 4 patterns · 2 chapters