WCAG2 Mobile: another step toward accessible apps
More and more people are using apps on their phones or tablets to look up information, make purchases or arrange their healthcare. Therefore, it is important that mobile applications are also accessible to everyone. On May 6, 2025, W3C published the first version of WCAG2 Mobile: a document that explains how to apply the guidelines of WCAG 2.2 to mobile apps. This explanation helps develop WCAG2 Mobile accessible apps and contributes to better mobile accessibility.
What is WCAG2 Mobile?
WCAG2 Mobile is a document that clarifies how the existing success criteria of WCAG 2.2 (and thus also of 2.1 and 2.0) can be applied to mobile apps. It is not a new version of WCAG, nor does it contain any new obligations. It is intended to be explanatory: a practical guide for developers, designers, testers and policy makers concerned with mobile accessibility.
The document was created by the Mobile Accessibility Task Force (MATF), a working group within the W3C. They built on an earlier version from 2015, but with a clear focus on mobile applications rather than mobile Web sites. The latest version aligns with the WCAG2ICT document, which explains how WCAG can be applied to non-web software such as PDFs or desktop applications.
The full WCAG2 Mobile guidelines can be found here Finding.
Why is WCAG2 Mobile needed?
While many WCAG 2.2 success criteria also apply to apps, they are often written with Web sites in mind. For example, the guidelines always refer to “Web pages,” but apps do not consist of pages. They work with screens or views (views). WCAG2 Mobile helps by translating such terms to the mobile context. This makes it clear what the intent of a success criterion is, and how to apply it to a mobile user interface.
WCAG2 Mobile also explains specific concerns that are especially important in apps. Think about the right size of buttons, support for screen rotation, one-finger operation, or the use of platform-specific accessibility features such as VoiceOver or TalkBack.
How is the document structured?
WCAG2 Mobile follows the structure of WCAG 2.2. That means the document is divided into four principles: observable, operable, understandable and robust. For each principle, the guidelines and associated success criteria are discussed. First, the original success criterion from WCAG is presented. Then it explains how that criterion can be interpreted for mobile apps.
Sometimes the explanation is quite simple: the criterion can be applied literally. In other cases, an adaptation or explanation is needed, such as when it's about navigation or how keyboard controls work within an app.
As an example, WCAG states that a “web page” must be operable by a keyboard. In an app, there is usually no physical keyboard. Nevertheless, this criterion is still relevant. This would include, for example, support for accessibility features that work with a virtual keyboard, or navigation via an external input such as a switch or speech.
What does WCAG2 Mobile mean in practice?
For developers and designers of mobile apps, WCAG2 Mobile means above all: more clarity. The document helps interpret existing guidelines and provides direction for designing and building accessible mobile interfaces. Because it contains no new rules, organizations already working on digital accessibility do not have to completely change their approach. But it does provide guidance for honing existing practices and making them more responsive to mobile technology.
WCAG2 Mobile helps organizations create apps that meet mobile accessibility requirements. For example, are you developing a new app? Then it is wise to already take into account the explanations from WCAG2 Mobile. Are you working on an update or improvement of an existing app? Then this is the time to test whether that app is in line with the latest insights on accessibility.
Is compliance with WCAG2 Mobile mandatory?
Right now, WCAG2 Mobile is still a so-called “Group Draft Note.” That means it is a working document, a first version that can still change. So it is not an official standard or commitment. However, the document has been published by the Accessibility Guidelines Working Group, the same group responsible for the official WCAG guidelines. That gives the document weight.
It is expected that WCAG2 Mobile will eventually become a final “Group Note.” Even then, it is still a note and not a standard. But for organizations serious about WCAG2 Mobile accessible apps, the document is valuable. It makes the translation of WCAG to the app world and helps to get started on improvements in concrete terms.
What's new from previous guidelines?
WCAG2 Mobile is not the first attempt to translate WCAG to mobile use. A draft document on mobile accessibility was published back in 2015, but it focused mainly on mobile websites. The new version is much broader in scope. For example, native apps and hybrid apps are also discussed, and there is much more focus on platform-independent frameworks such as React Native or Flutter.
In addition, WCAG2 Mobile aligns with WCAG2ICT, the sister document that explains how to apply WCAG to software outside the browser. Together, these documents form a bridge between the classic Web world and today's reality, where users access information, fill out forms and interact with digital services on a variety of devices.
Mobile accessibility deserves attention
Meanwhile, many people use smartphones exclusively to access digital services. Think of the elderly, people with motor disabilities or users with visual impairments. For these groups, it is extra important that an app works well, provides clear feedback and is easy to use. Mobile accessibility therefore goes beyond technology: it touches on usability, equality and inclusion.
By taking WCAG2 Mobile seriously, designers and developers can make better choices. They can create mobile apps that are not only legally correct, but actually usable by everyone. Accessibility need not be a limitation - quite the contrary: it leads to clear, thoughtful designs that work for a wide audience.
Conclusion
WCAG2 Mobile is a welcome addition to existing accessibility guidelines. It provides clarity on how WCAG 2.2 can be applied to mobile apps without imposing new obligations. For those working on WCAG2Mobile accessible apps, the document provides valuable insights and guidance on how to improve mobile accessibility. And for anyone contributing to an inclusive digital world, WCAG2 Mobile is a step forward.
The full WCAG2 Mobile guidelines can be found here find
