A website accessibility statement can point to a URL, a page, and a browser. A native mobile app has none of those. There is no HTML to run an automated scanner against, no single address a reviewer can load, and no “page” in the sense a WCAG success criterion assumes when it talks about link text or heading structure. An app is a compiled binary running on someone else’s operating system, tested with that operating system’s own screen reader, distributed through a store that has its own review cycle and its own accessibility metadata. Writing an accessibility statement for that surface by copying a website template and swapping “site” for “app” produces a document that is technically present but not actually true of what was tested.
Why WCAG Doesn’t Map Onto an App Cleanly
WCAG (the Web Content Accessibility Guidelines) was written for web content: HTML, CSS, and the DOM. Most of its success criteria still describe the right outcome for a native app, focus order should make sense, color should not be the only way information is conveyed, touch targets should be large enough to hit reliably, but the criteria are worded in web terms that do not translate one-to-one to an iOS or Android screen built from native UI components.
The W3C’s own working group addressed this gap with a document called WCAG2ICT, a mapping of WCAG 2.x success criteria onto non-web software and other information and communication technology. It is a Working Group Note, not a binding standard on its own, but it is the closest thing to an official bridge between “WCAG 2.1 AA” as a phrase and what that actually means for a native app screen with no markup to point to. A mobile app’s accessibility statement should cite this mapping rather than quoting a raw WCAG success criterion and expecting it to read as self-evidently true of a compiled app.
The other half of the story is platform-native. Apple publishes accessibility guidance as part of its Human Interface Guidelines, and Android has its own accessibility developer documentation, both describing how VoiceOver and TalkBack are supposed to interpret an app’s UI elements through operating-system accessibility APIs rather than through anything resembling HTML semantics. A native app is really tested against two things at once: the WCAG2ICT-mapped success criteria, and the platform’s own accessibility API conventions. A statement that names only WCAG and never mentions the platform layer is incomplete for what an app actually is.
What ADA Title III Guidance Actually Says About Apps
The Americans with Disabilities Act’s Title III, the part that covers private businesses open to the public, still has no regulation naming a specific technical standard for websites or apps. The Department of Justice’s July 2022 guidance document on web accessibility and the ADA reaffirmed that Title III applies to the websites and mobile apps of covered businesses, but it stopped short of prescribing WCAG or any other standard as legally mandatory, leaving that determination to case-by-case litigation and settlement practice. Courts have been inconsistent about a related question, whether an app alone (with no accompanying physical location or connected website) counts as a place of public accommodation at all, and that split has not been resolved nationally.
Title II, the part of the ADA covering state and local government, is more concrete, and it is worth knowing about even for a private business because it is often cited as the practical benchmark. The DOJ’s 2024 final rule under Title II requires state and local government entities to make both their web content and their mobile apps conform to WCAG 2.1 Level AA, on a compliance timeline based on population (April 2026 for larger entities, April 2027 for smaller ones and special district governments). That rule explicitly lists mobile apps as in scope alongside web content, which is the first time a federal ADA regulation has named apps by name rather than leaving them to be inferred from “website” language.
Figure 1: Compliance dates under the DOJ’s 2024 ADA Title II rule. Source: U.S. Department of Justice.
For a private business under Title III, there is still no equivalent formal mandate, but the practical reference point plaintiffs’ attorneys, settlement agreements, and consent decrees have converged on is the same WCAG 2.1 (or 2.2) Level AA target, applied through the WCAG2ICT mapping for anything that is not literally a web page. Naming that target explicitly in a statement, rather than leaving it vague, is the same advice that applies to a website statement, it is just paired with a different technical mapping underneath.
Website Statement vs App Statement
| Website Statement | App Statement | |
|---|---|---|
| Conformance basis | WCAG 2.2 AA directly | WCAG2ICT plus platform guides |
| Tested against | Browser plus assistive tech | VoiceOver and TalkBack |
| Version tracked | One live URL, no version | App version and build number |
| Published | On the website itself | Settings screen, store, website |
| Update trigger | Redesign or new page | Each app store release |
Naming iOS and Android Separately
A website has one live version at any given moment. An app usually has two, an iOS build and an Android build, that share a design but not always the same implementation, and VoiceOver and TalkBack do not behave identically even when a developer built the same custom component for both platforms. A slider control that announces its value correctly under VoiceOver can be silent under TalkBack if the underlying accessibility node wasn’t set up the same way on both platforms, and the reverse happens just as often.
Figure 2: A custom control can announce correctly under VoiceOver and stay silent under TalkBack.
That makes a single, undifferentiated “the app is accessible” statement less useful for a native app than it already is for a website. A statement that says “tested with VoiceOver on iOS and TalkBack on Android, with the following known gaps on each platform” is doing real work; one that just says “our app supports screen readers” is not saying anything a reader can verify. Where the two platforms genuinely differ, in feature parity, in which screens have been retested most recently, in which custom components still lack proper accessibility labels, the statement should say so by platform rather than folding both into one paragraph that quietly describes whichever platform was tested more recently.
Tying the Statement to a Version Number
This is the part of an app statement that has no real equivalent on the web. A website is live the moment a change is pushed; there is one current version, and a statement about “the site” is a statement about what exists right now. An app is different: a build gets submitted to app store review, waits for approval, and rolls out to users gradually, which means several versions of the same app can be running on real devices simultaneously, an older build still on someone’s phone because they have not updated, alongside the newest build that just cleared review.
An accessibility statement that does not name a version is making a claim that cannot be checked against what is actually installed on a given user’s device. Naming the app version and build number the statement was tested against, and updating that reference every time a release changes something accessibility-relevant, is what keeps the statement honest about which build it actually describes.
Where the Statement Actually Lives
A website’s accessibility statement lives at a URL and links from the footer. An app doesn’t have a footer, so the statement needs a different home, and in practice it needs more than one. Most apps put the full statement inside the app itself, usually under Settings or an About screen, since that is the place a user who hits a barrier is most likely to look first. The same statement, or a link to it, should also live on the company’s website, since a user who cannot get into the app in the first place has nowhere else to find it. App store listings add a third surface worth knowing about: Apple added an optional accessibility information section to App Store product pages, letting developers declare which accessibility features (VoiceOver support, Voice Control, larger text, sufficient contrast, and similar) the app actually supports, shown to a shopper before they ever download it. Google Play does not yet have an equivalent standardized field on the store listing itself. Whatever is declared in that App Store section should match what the in-app statement says; a mismatch between what a store listing promises and what the statement discloses is worse than a plain, honest statement with real limitations listed.
Figure 3: The three surfaces where an app’s accessibility statement should appear.
- References pages and browser support
- One undifferentiated iOS/Android claim
- No app version or build referenced
- Lives only inside the app, if anywhere
- Cites WCAG2ICT plus platform guidelines
- Lists iOS and Android gaps separately
- Names the app version it was tested against
- Published in-app, on the site, and in the store listing
The Statement Still Isn’t the Fix
Everything true of a website accessibility statement is still true here: publishing one documents a state of testing, it does not create an accessible app. A statement that names five known gaps on the checkout screen and never gets updated after the next three releases is worse evidence than no statement at all, because it shows the gaps were known and left in place. Treat the statement as the layer on top of a real testing cycle: an audit with an actual screen reader on each platform, a prioritized list of what blocks a task outright (a checkout button VoiceOver can’t reach) over what is a lower-severity annoyance (a decorative icon missing a label), and a statement that gets touched every release, not just once a year.
If the same product also has an authenticated web dashboard alongside the mobile app, the accessibility work does not stop at the app store; see accessibility statement for a SaaS dashboard for what WCAG 2.2 expects of the logged-in web surface most companion apps sit next to. For the general structure a statement needs regardless of platform, conformance target, limitations, and a working contact channel, start with how to write an accessibility statement that meets ADA and WCAG expectations. Our Accessibility Statement generator builds the base document from those same required fields, which you can then adapt with the version number, platform split, and in-app placement a native app needs on top.








