A 15-minute accessibility check before launch
· 8 min read
You have tested your app a hundred times. But always with your own eyes, your own hands and your phone at its default settings. Some of your users will open it with a screen reader, with the text turned up, or with a thumb that is not quite as precise as yours. You can spot most of the common problems yourself in about 15 minutes, with no tools to buy. This post is that routine, plus how to ask testers about it without making things awkward.
Why bother
I read the W3C's introduction to accessibility on 10 November 2026. It says accessibility helps people with disabilities "perceive, understand, navigate, and interact with the Web". It also helps people without disabilities, such as those with "situational limitations" like being "in bright sunlight", and older people with "changing abilities due to ageing". The same page says "Accessible design improves overall user experience and satisfaction" and that "there is also a strong business case for accessibility".
Screen reader in 5 minutes
A screen reader speaks what is on the screen and lets people move through it without looking. Both platforms have one built in. Try your main flow with it, from opening the app to the first useful thing. If your app is a web app, run the same test in the phone's browser.
VoiceOver on iPhone
I read Apple's Turn on and practice VoiceOver page and the VoiceOver gestures page on 10 November 2026. Apple calls VoiceOver "a gesture-based screen reader". To turn it on, go to Settings, then Accessibility, then VoiceOver. You can also use Control Center or the Accessibility Shortcut if you have set them up, or ask Siri to "Turn on VoiceOver." Apple warns that "When VoiceOver is on, you must use VoiceOver gestures to operate iPhone", so learn the basics first:
- Touch an item or drag a finger over the screen to hear its name.
- Swipe right to select the next item and swipe left for the previous one.
- Double tap to activate the selected item.
- Two-finger swipe down to speak the entire screen from the selected item.
TalkBack on Android
I read Google's Turn on TalkBack and Use TalkBack gestures pages on 10 November 2026. Google notes that how you turn it on "can be a little different" depending on your phone and Android version. The usual route is: open Settings, tap Accessibility, tap TalkBack, then choose Use TalkBack. When it is on, a box goes around the item that is in focus. The basic one-finger gestures from Google's table:
- Swipe right moves to the next item on the screen and swipe left to the previous one.
- Drag a finger on the screen for explore by touch, which speaks the item below your finger.
- Double-tap activates the focused item.
What to listen for
- A button that is only called "button". An icon button with no name is a dead end for someone who cannot see the icon. Give every icon button a short label such as "Add photo" or "Close".
- Images with no description, or a useless one. If an image carries meaning, it needs a short description. If it is only decoration, it should be skipped.
- Focus order. Swipe through a whole screen. Does the order follow the order a sighted person reads in? Does anything get skipped, or read twice?
Touch target size
A target is anything you can tap. If it is too small, people miss it and hit the wrong thing. Three official sources give three numbers, and they are not the same because they measure different things. I read each of these on 10 November 2026.
- Apple. The Buttons guidelines say "a button needs a hit region of at least 44x44 pt". The Accessibility guidelines list a default control size of 44x44 pt for iOS and iPadOS and a minimum control size of 28x28 pt.
- Android. Google's Touch target size page suggests a "width and height of at least 48dp". It adds that an icon may look like 24x24dp but the padding around it makes up the full 48x48dp touch target, which is "about 9mm" in physical size.
- WCAG 2.2. Success Criterion 2.5.8, Target Size (Minimum), says "The size of the target for pointer inputs is at least 24 by 24 CSS pixels", with a list of exceptions that includes Spacing, Equivalent, Inline, User Agent Control and Essential.
How to read that: if you build a native iPhone app, aim for 44 points. For a native Android app, aim for 48dp. For a web app in a phone browser, WCAG's 24 by 24 CSS pixels is the minimum, and the bigger platform numbers are a good goal. The size can come from padding, so a small icon is fine if the tappable area around it is big enough. To test, tap every small control with your thumb, one-handed, while walking around the room.
Text size
People change their text size for all sorts of reasons. Turn it to the maximum and see what happens to your app.
- iPhone. Apple's Make text easier to read page says to go to Settings, then Accessibility, then Display & Text Size, tap Larger Text and drag the slider. "For additional text sizes, turn on Larger Accessibility Sizes." Apple's text guidance for developers is to support Dynamic Type, which it describes as a system feature that "lets people adjust the size of visible text on their device", in its typography guidelines. The accessibility page adds that you should ideally "give people the option to enlarge text by at least 200 percent".
- Android. Google's Change text & display settings page says to open Settings, search for Font size or Display size, and move the slider. It warns that "The font size setting doesn't apply to some apps", and that some of the steps work only on Android 13 and up.
Open your key screens at the largest setting. Look for text that is cut off, buttons whose labels no longer fit, text that overlaps other text, and anything you can no longer scroll to. Fix the worst screens first: sign-up, checkout and anything with a primary button.
Contrast
Light grey text on white looks elegant on your bright desk and disappears on a train. WCAG's Contrast (Minimum) criterion, 1.4.3, which I read on 10 November 2026, asks for a contrast ratio of "at least 4.5:1" for text. Large-scale text needs "at least 3:1". The page defines large-scale text as "at least 18 point or 14 point bold". A quick test: turn your screen brightness down and walk to a window. If you squint at placeholder text, hint text or disabled buttons, they probably fail. A free contrast checker will give you the exact ratio for a colour pair.
Free tools
- Accessibility Scanner (Android). Google's Get started with Accessibility Scanner page says it "scans your screen and provides suggestions to improve the accessibility of your app", based on content labels, touch target size, clickable items, and text and image contrast. It is available from Google Play for Android 9.0 and up. Google also says it "isn't a replacement for manual testing and doesn't guarantee the accessibility of the app", so treat it as a second pair of eyes.
- Accessibility Inspector (Xcode). Apple's inspection article says to open it from Xcode, under Xcode, Open Developer Tool, Accessibility Inspector. It shows the accessibility properties of elements on screen, and lets you step through them in the same order that VoiceOver uses. Apple's audits article says an audit gives feedback on issues "such as insufficient contrast, text clipping, or missing element descriptions".
What to ask testers
Don't guess who your testers are, and don't ask anyone to prove anything. Many people don't use any of these settings, and that is fine. Make it an optional extra. Something like this at the end of a test task:
"Optional: if you already use a screen reader (VoiceOver or TalkBack), larger text, or another accessibility setting on your phone, please do the first task with it on, and tell me anything that didn't work. If that's not you, no problem, skip this."
Ask about settings, not about people, and say out loud that it is optional. Ask for specifics: which screen, what they heard or saw, and which phone and setting. If someone doesn't use these settings, you can still ask them to turn the text up for two minutes and look.
The structure of a good task matters here too, so see how to write a test task. And since settings and screens vary between phones, ask every tester what phone they used, as in testing on phones you don't own.
The 15-minute checklist
- Minutes 1 to 5: turn on VoiceOver or TalkBack and run your main flow. Note every unlabeled button, every image with no description and any odd focus order.
- Minutes 6 to 8: tap every small control with your thumb. Aim for 44 pt on iPhone, 48dp on Android, and at least 24 by 24 CSS pixels on the web.
- Minutes 9 to 11: set the text size to the largest and open your key screens. Look for cut-off text and broken layouts.
- Minutes 12 to 13: lower the brightness and look for text that is hard to read. Check suspect colour pairs against 4.5:1 for normal text and 3:1 for large text.
- Minutes 14 to 15: run Accessibility Scanner on Android, or Accessibility Inspector on a Mac, and write down what it finds.
- Afterwards: fix the labels and the sizes first, since they are quick, then add an optional accessibility line to your test task.
Where TestSwap fits
TestSwap is a free site where app makers review each other's apps: you test someone's app, they test yours. You can post web, iOS and Android apps, and link to wherever testers can open or install it. Every app is tested by real people on their own phones. That is useful for this, because settings like text size and screen readers are personal and differ from phone to phone.
I won't pretend TestSwap picks testers by their accessibility settings. It doesn't, so ask for it in your test task. A review has an optional private bug notes box that only the maker sees, so ask testers to put what they found there, with the phone and setting they used.
Try it
Do the 15-minute check on your own phone first, fix what you find, then post your app on TestSwap with a test task that includes the optional accessibility line. Reviewing someone else's app first is the quickest way to see how it works, and you might notice your own habits in theirs. Tell me what's missing or broken (@dizid on X).