A 10-minute screen reader test for your app
Screen readers read your interface out loud for people who cannot see it well. Ten minutes with one will show you problems that sighted testing never reveals, and many fixes are small.
Set up
- Android: turn on TalkBack in Settings → Accessibility. Swipe right to move to the next element, double tap to activate.
- iPhone: turn on VoiceOver in Settings → Accessibility. Swipe right to move on, double tap to activate.
Learn the gestures first, then close your eyes or turn the screen brightness down so you cannot cheat.
The routine
- Open the app and listen to the first screen. Does it say what the screen is for?
- Move through every element. Each button and field needs a spoken label. "Button" alone is a bug.
- Complete your core flow: sign-up, the main action, the confirmation. Can you finish it without looking?
- Check the order. Focus should follow the visual order from top to bottom.
- Check errors and changes. When a message appears or content updates, is it announced?
- Check images. Meaningful images need a description, decorative ones should be skipped.
Fixes that pay off
- Add content descriptions (Android) or accessibility labels (iOS) to icon-only buttons.
- Group related text into one element so it reads as one thought.
- Make touch targets at least about 48 dp on Android and 44 pt on iOS.
- Do not rely on color alone to show a state.
Questions developers ask
Is this enough for compliance? No. It is a fast way to find the biggest blockers. Laws and standards such as WCAG ask for more.
Who should test? Ideally also people who use a screen reader every day. A developer test is the start, not the end.
Need testers for your app? Open a test group on AppReviewX. Start free