After auditing some native mobile apps for accessibility I tried to understand the capabilities and possibilities of native mobile platforms for Android and iOS applications. In this post I try to reflect on the fact that making native mobile apps accessible can be much harder than when we try to make web accessible.
I had to fail an Android app in a recent WCAG audit because it’s expand/collapse components didn’t have the semantics. On the review I got asked about possible solutions and here you go – hope it will help somebody make accordions on Android more accessible.
Mobile native applications are often with no headings. Sometimes even have visual headings but are missing on the semantics. Screen-reader users can and also like to navigate via headings, so we should be responsible and use them. They are supported on both iOS and Android.
It was not clear to me if WCAG 4.1.3 can be applied to native mobile applications. At least on both iOS and Android. So I did some research and came with the conclusion that we can and should or even must use status messages also on native mobile apps.
A short post about my Global Accessibility Awareness Day 2022 contribution – online escape room for mobile screen-readers called Voice-Back.
What was the motivation, intention, implementation and goal behind voice-back.net.
Please try it out if you want and let me know how it went.
Not everybody can or want to use their apps in a single predefined screen orientation. It should be a matter of preference and choice. That is accessibility as well. And we even have it as an WCAG Success Criteria. And yes – it should also be applied to native mobile devices.