CoChat

The Current Status of Accessibility in Mobile Apps

Yan, Shunguo, Ramachandran, P. G. · 2019 · ACM Transactions on Accessible Computing

The DOI matches its Crossref record; 21 of the 21 references it cites were found in a registry or an index.

Abstract

This study evaluated the status of accessibility in mobile apps by investigating the graphical user interface (GUI) structures and conformance to accessibility guidelines of 479 Android apps in 23 business categories from Google Play. An automated tool, IBM Mobile Accessibility Checker (MAC), was used to identify the accessibility issues, which were categorized as a violation (V), potential violation (PV), or warning (W). The results showed 94.8%, 97.5%, and 66.4% of apps studied contained issues related to V, PV, or W, respectively. Five widget categories (TextView, ImageView, View, Button, and ImageButton) were used to create 92% of the total number of the GUI elements and caused 89%, 78%, and 86% of V, PV, and W, respectively. These accessibility issues were mainly caused by lack of element focus, missing element description, low text color contrast, lack of sufficient spacing between elements, and less than minimum sizes of text fonts and elements. Together, these accessibility issues accounted for 97.0%, 77.8%, and 94.5% of V, PV, and W, respectively. This study proposed coverage measures to estimate the percentage of accessibility issues identified by an automated tool. The result showed that MAC, on average, identified about 67% of accessibility issues in mobile apps. Two new accessibility conformance measures were proposed in this study: inaccessible element rate (IAER) and accessibility issue rate (AIR). IAER estimates the percentage of GUI elements that are inaccessible. AIR calculates the percentage of the actual number of accessibility issues relative to the maximum number of accessibility issues. Average IAER and AIR scores were 27.3%, 19.9%, 6.3% and 20.7%, 15.0%, 5.4% for V, PV, and W, respectively, for the studied apps. The IAER score showed approximately 30% of the GUI elements had accessibility issues, and the AIR score indicated that 15% of the accessibility issues remained and need to be fixed to make the apps accessible.

Overview

Integrity signals

Registry

Crossref · 10.1145/3300176

Cites

21 of 21 references verified0 citation errors · 0 not checkable

Statistics

Recomputing p-values needs the paper’s full text.

Verification

Claims the paper makes

This paper’s full text isn’t openly available, so its claims and self-check weren’t run. The registry and citation checks still apply.

Claims other papers make about this one

Each is checked against this paper’s own text: does it say what the citing paper says it does?

Citations

Cites

Show all 21 references

Research works printed but not linked: 17

  1. Apple Inc., 2016, Proceedings of the Apple Worldwide Developers Conference 2016
  2. BBC., 2016, Retrieved
  3. 2018, Retrieved
  4. Google LLC., 2018, Accessibility scanner app. Retrieved
  5. Google, 2017, Retrieved
  6. Accessibility IBM, 2017, Retrieved
  7. Mauro, Proceedings of the 9th International Conference on Universal Access in Human-Computer Interaction (UAHCI’15)
  8. Torres-Carazo M. I., Proceedings of the IEEE International Conference on Serious Games and Applications for Health Location (SeGah’16)
  9. United States Access Board., 2017, Retrieved
  10. Web Accessibility, 2015, Retrieved
  11. AIM., 2017, Retrieved
  12. World Wide Web Consortium (W3C). 2008., 2018, Web Content Accessibility Guidelines (WCAG) 2.0. Retrieved
  13. World Wide Web Consortium (W3C). 2015., 2018, Cognitive Accessibility User Research. Retrieved
  14. World Wide Web Consortium (W3C). 2016., 2018, Web Accessibility Evaluation Tools List. Retrieved
  15. World Wide Web Consortium (W3C)., 2016, Retrieved
  16. World Wide Web Consortium (W3C)., 2016, Retrieved
  17. World Wide Web Consortium (W3C). 2018., 2018, Web Content Accessibility Guidelines (WCAG) 2.1. Retrieved

Cited by

Metadata

Authors
Yan, S., & Ramachandran, P. G.
Affiliations
IBM (United States) (US)
Venue
ACM Transactions on Accessible Computing
Published
2019-02-11
Volume
12
Issue
1
Pages
1-31
ISSN
  • 1936-7228 (ISSN-L)
  • 1936-7236
OpenAlex
W2911344747
Cited by
165
References
21
Citations by year
2026: 18 · 2025: 33 · 2024: 27 · 2023: 31 · 2022: 20 · 2021: 24 · 2020: 9 · 2019: 3
FWCI
40.91
Type
journal article
Language
en
Open access
closed
Locations
ACM Transactions on Accessible Computing (publishedVersion)
Topics
  • Social Sciences › Human Factors and Ergonomics › Digital Accessibility for Disabilities
  • Physical Sciences › Computer Science › Human-Computer Interaction › Usability and User Interface Design
  • Physical Sciences › Computer Science › Information Systems › Mobile and Web Applications
Keywords
mobile app accessibility, Android application, coverage measures, Google Play apps

About these checks

Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.

Statistics and arithmetic are recomputed, not judged.

Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.

What counts as a claim ›How we measure confidence ›How we check this ›

Are you an author, or do you see a problem with this page? Request a review

Data sources

Bibliographic data: Semantic Scholar, OpenAlex, Crossref.

Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).

Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.