Checklist: testing an app for accessibility
For: Product owners, development and marketing
Updated: 2026-11
A first accessibility test of an app covers: full keyboard operation, understandable screen reader output, sufficient contrast, zoom without loss, labelled forms, understandable error messages, no overly short time limits and the required accessibility information.
The checklist covers the most common defects and suits a first assessment by your own team. It follows WCAG 2.1 level AA, on which the European requirements are based.
Testing is done on the journeys users actually go through, not on a single home page.
The checklist
- 01
Operate with a keyboard
Go through the main journey without a mouse and watch for visible focus and logical order.
Done when: The journey can be completed fully by keyboard, and focus is visible at all times.
- 02
Test with a screen reader
Check with VoiceOver or NVDA whether buttons, images and headings are announced sensibly.
Done when: All controls have understandable names, and meaningful images have alternative text.
- 03
Measure contrast
Check text and important graphics for sufficient contrast against the background.
Done when: Normal text reaches at least 4.5 to 1, large text at least 3 to 1.
- 04
Zoom
Zoom to 200 percent and enlarge text on mobile devices via system settings.
Done when: Content remains readable and operable; nothing is cut off or overlapped.
- 05
Check forms
Every field needs a visible label, and required fields must be marked.
Done when: All fields are labelled and programmatically associated with their label.
- 06
Check error messages
Trigger errors deliberately and check that cause and solution appear understandably at the field.
Done when: Error messages name the field, the error and a way to fix it.
- 07
Provide information
Describe how the service meets the requirements and give a contact route for feedback.
Done when: The accessibility information is published and easy to find.
Common mistakes
- —Only automated tools are used, which miss a large share of defects.
- —Individual pages are fixed, but not the components from which new pages are built.
- —Overlay tools are treated as a solution although they do not fix the causes.
What this checklist does not cover
- —The checklist is a first assessment, not a complete test against all criteria.
- —It does not settle whether your service legally falls under the BFSG, BaFG or the European Accessibility Act.
Parent service: App Development
Matching offers
Accessibility for apps and online shops
Since 28 June 2025, Germany’s BFSG, Austria’s BaFG and the European Accessibility Act have required accessibility for many consumer services, including online shops and apps used to conclude contracts. We test your app or shop against WCAG, fix the issues in the code and draft the required accessibility information.
Accessible website
We audit existing websites against WCAG with automated and manual tests, fix the reused components, support content and PDFs and write the accessibility statement. New websites are built to WCAG 2.2 level AA from the start, compatible with eCH-0059 and the requirements of the European Accessibility Act.
FAQ
Who should carry out the test?
Your own team for a first assessment. For a robust test, someone experienced with assistive technology.
Does the list apply to websites too?
Largely yes. For websites there is also our website accessibility checklist.
More checklists
Checklist: starting an AI project properly
An AI project starts properly with a clear problem and a measurable success criterion, clarified data and permissions, a reasoned model choice, AI Act and data protection classification, a test set of real cases, defined human approvals and a plan for operation.
Checklist: preparing software makers for the new product liability rules
By December 2026, software makers should inventory their products, define update commitments, introduce a vulnerability process, retain development and test records, review contracts and terms of use, and check that their liability insurance covers software risks.
Checklist: introducing an ISMS to ISO 27001
Introducing an ISO 27001 ISMS follows fixed steps: define the scope, appoint roles, inventory assets, assess risks, select controls in the statement of applicability, introduce policies, train staff, audit internally and have management review the system.