Mobile app accessibility: a practical guide for iOS and Android
How to make mobile apps usable for people with disabilities, using platform accessibility features, good design and testing with screen readers.
The automated and manual tools that help you find accessibility problems, what each one catches, and a testing routine that fits into normal website work.
No single tool can confirm a website is accessible. Automated checkers such as axe, WAVE and Lighthouse quickly catch common issues like missing alt text, low contrast and unlabelled forms, but they find only part of the problems. Combine them with keyboard testing, screen reader testing, contrast checks, zoom testing and, ideally, feedback from disabled users. Build checks into everyday work, not just one-off audits.
Accessibility means people with disabilities can use your website: people who are blind or have low vision, are deaf or hard of hearing, have motor impairments or cognitive differences. The Web Content Accessibility Guidelines (WCAG) are the international standard, with level AA the common target. Testing against them requires a mix of tools and human judgement.
Automated tools scan pages and flag issues that can be detected by code.
axe and axe DevTools. A widely used testing engine available as a browser extension and for automated testing pipelines.
WAVE. A browser extension and online tool that overlays icons on the page to show errors and warnings visually.
Lighthouse. Built into Chrome's developer tools, with an accessibility score alongside performance and SEO.
Accessibility Insights. Microsoft's free tool with automated checks and guided manual tests.
What they catch well:
What they miss: whether alt text is meaningful, whether the reading order makes sense, whether keyboard navigation is logical, whether content is understandable, and many interaction problems. Automated tools typically catch only a portion of real issues.
Unplug the mouse, or simply stop using it, and navigate with Tab, Shift+Tab, Enter, Space and arrow keys:
This simple test reveals many serious problems.
Screen readers read content aloud and let users navigate by headings, links and landmarks.
Check that headings make sense, images have useful descriptions, buttons announce their purpose, forms explain errors and dynamic updates are announced. Mobile screen readers matter too; see our guide to mobile app accessibility.
Contrast checkers measure text and background colour combinations against WCAG ratios: at least 4.5:1 for normal text and 3:1 for large text and key interface elements. Also check that colour isn't the only way information is conveyed, such as error states shown only in red.
Zoom the browser to 200% and 400%. Content should remain readable without sideways scrolling, and nothing should overlap or disappear.
Nothing replaces feedback from people who use assistive technology every day. Usability testing with disabled participants reveals real-world issues that checklists miss.
If you also have a mobile app, test it with mobile screen readers and system text sizes; our guide to mobile app accessibility covers the specifics. Forms are a frequent source of accessibility problems, so pay special attention to labels and errors, as explained in our guide to website forms best practices.
Record issues with the page, the WCAG criterion, severity and how to reproduce them. Prioritise problems that block key tasks, like forms, navigation and checkout.
Tools find problems; habits prevent them. Add accessibility checks to design reviews and code reviews, include them in your definition of done, and share short examples of good and bad patterns with the team. Small, consistent habits make far more difference than an annual audit on its own.
Our web development team builds and tests to WCAG 2.2 AA, our UI/UX design team designs accessible components, and our maintenance plans include periodic accessibility checks.
No. Automated tools find some issues quickly, but manual testing with keyboards and screen readers is essential.
WAVE, axe DevTools, Lighthouse and the free NVDA screen reader are good starting points.
Test new features before release, and run a fuller audit of key pages at least once a year.
This guide is general information, not legal, tax or financial advice, and details such as prices, features and rules can change. Product and company names mentioned are trademarks of their respective owners and are used only to identify those products; UK Technology Hub is not affiliated with or endorsed by them.
Tell us about your project and get a free, fixed quote.
Get a free quoteHow to make mobile apps usable for people with disabilities, using platform accessibility features, good design and testing with screen readers.
What user interface and user experience design each cover, how they work together, and what to expect from UI and UX work on a website or app project.
What the Jamstack approach is, how pre-built pages and APIs make sites faster and more secure, and when it's the right choice for a business website.