The Current Status of Accessibility in Mobile Apps
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
Cites
Statistics
Verification
Claims the paper makes
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?
In the citing paper
“In addition, the accessibility requirements assessed by the tools—with the exception of MAC—are limited and not standardized. This may cause a lack of systematic or predictive results [40].”
From Are Saudi Arabian banks' mobile applications accessible for blind or partially sighted users?: a customers' perspective and evaluation (2025) · cites this paper as [40]
In the citing paper
“Moreover, the accuracy of automatic accessibility evaluation results is varied and lower than the accuracy of manual expert accessibility evaluation results [39, 40].”
From Are Saudi Arabian banks' mobile applications accessible for blind or partially sighted users?: a customers' perspective and evaluation (2025) · cites this paper as [40]
In the citing paper
“On the contrary, the accessibility of mobile applications has not been examined so thoroughly (Yan and Ramachandran 2019)”
From The making of accessible Android applications: an empirical study on the state of the practice (2022) · cites this paper as Yan and Ramachandran 2019
In the citing paper
“differently from iOS, accessibility work in Android apps is very limited (Martin et al. 2016; Yan and Ramachandran 2019)”
From The making of accessible Android applications: an empirical study on the state of the practice (2022) · cites this paper as Yan and Ramachandran 2019
Citations
Cites
Guidelines are only half of the story: accessibility problems encountered by blind users on the web
Power, C., Freire, A., Petrie, H., & Swallow, D. (2012) · Proceedings of the SIGCHI Conference on Human Factors in Computing Systems · doi:10.1145/2207676.2207736 · Cited by 327 · cited 3×
“The effectiveness of an automated tool depends on its coverage and correctness [5, 20].”
BackgroundMethodResultThe state of the art of mobile application usability evaluation
Nayebi, F., Desharnais, J.-M., & Abran, A. (2012) · 2012 25th IEEE Canadian Conference on Electrical and Computer Engineering (CCECE) · doi:10.1109/ccece.2012.6334930 · Cited by 236 · cited 2×
“Previous studies on mobile accessibility have mostly focused either on mobile accessibility guidelines [4, 7, 14, 17, 21, 28], mobile web accessibility [33, 36], accessibility features integrated into a mobile operating system [15, 18, 19], or on apps that are specifically designed for disabled people [23].”
BackgroundVigo, M., Brown, J., & Conway, V. (2013) · Proceedings of the 10th International Cross-Disciplinary Conference on Web Accessibility · doi:10.1145/2461121.2461124 · Cited by 215 · cited 3×
“A combination of test suites (unit test apps), test apps, and commercial apps are used to verify the correctness of the results from MAC, because test suites alone may miss some types of errors and also can produce false positives [5, 27].”
BackgroundMethodInfluentialBarriers to use: usability and content accessibility on the Web's most popular sites
Sullivan, T., & Matson, R. (2000) · Proceedings on the 2000 conference on Universal Usability - CUU '00 · doi:10.1145/355460.355549 · Cited by 183 · cited 2×
“Further, conformance to a guideline does not necessarily convey the experience of the user although a study found a low but significant relationship between accessibility and usability [22].”
BackgroundMethodProgress on Website Accessibility?
Hanson, V. L., & Richards, J. T. (2013) · ACM Transactions on the Web · doi:10.1145/2435215.2435217 · Cited by 145 · cited 1×
“Nevertheless, studies reported significant accessibility issues in websites [12] and a lack of significant evolution in web accessibility evaluation methods for the period from 2011 to 2015 [2].”
BackgroundAccessibility of Internet websites through time
Hackett, S., Parmanto, B., & Zeng, X. (2003) · Proceedings of the 6th international ACM SIGACCESS conference on Computers and accessibility · doi:10.1145/1028630.1028638 · Cited by 145 · cited 2×
“Hackett et al. [11] proposed a Web Accessibility Barrier Score (WABScore) that is calculated as the ratio of actual to potential number of violations, then multiplied by a weight in inverse proportion to WCAG 1.0 priorities.”
MethodInfluentialInteracting with mobile devices via VoiceOver: usability and accessibility issues
Leporini, B., Buzzi, M. C., & Buzzi, M. (2012) · Proceedings of the 24th Australian Computer-Human Interaction Conference · doi:10.1145/2414536.2414591 · Cited by 116 · cited 3×
“Previous studies on mobile accessibility have mostly focused either on mobile accessibility guidelines [4, 7, 14, 17, 21, 28], mobile web accessibility [33, 36], accessibility features integrated into a mobile operating system [15, 18, 19], or on apps that are specifically designed for disabled people [23].”
BackgroundAutomatic web accessibility metrics: Where we are and where we can go
Vigo, M., & Brajnik, G. (2011) · Interacting with Computers · doi:10.1016/j.intcom.2011.01.001 · Cited by 112 · cited 2×
“…figure” that appears to be a simple error count although it was characterized elsewhere as a failure rate defined as a ratio between actual and potential points of failure [25, 26], which is similar to the WABScore for a single page but without the weight factor (priority in WCAG 1.0) [25].”
BackgroundResultInfluentialQuantitative metrics for measuring web accessibility
Vigo, M., Arrue, M., Brajnik, G., Lomuscio, R., & Abascal, J. (2007) · Proceedings of the 2007 international cross-disciplinary conference on Web accessibility (W4A) - W4A '07 · doi:10.1145/1243441.1243465 · Cited by 106 · cited 6×
“0 as in WABScore [11] and failure rate [25].”
BackgroundMethodInfluentialComparing accessibility evaluation tools: a method for tool effectiveness
Brajnik, G. (2004) · Universal Access in the Information Society · doi:10.1007/s10209-004-0105-y · Cited by 101 · cited 5×
“In prior work, the coverage for a web accessibility evaluation tool has often been expressed as a percentage of checkpoints (in WCAG 1.0) or SC in WCAG 2.0 checked by a tool [5, 16, 20, 27].”
BackgroundMethodResultInfluential
Research works printed but not linked: 17
- Apple Inc., 2016, Proceedings of the Apple Worldwide Developers Conference 2016
- BBC., 2016, Retrieved
- 2018, Retrieved
- Google LLC., 2018, Accessibility scanner app. Retrieved
- Google, 2017, Retrieved
- Accessibility IBM, 2017, Retrieved
- Mauro, Proceedings of the 9th International Conference on Universal Access in Human-Computer Interaction (UAHCI’15)
- Torres-Carazo M. I., Proceedings of the IEEE International Conference on Serious Games and Applications for Health Location (SeGah’16)
- United States Access Board., 2017, Retrieved
- Web Accessibility, 2015, Retrieved
- AIM., 2017, Retrieved
- World Wide Web Consortium (W3C). 2008., 2018, Web Content Accessibility Guidelines (WCAG) 2.0. Retrieved
- World Wide Web Consortium (W3C). 2015., 2018, Cognitive Accessibility User Research. Retrieved
- World Wide Web Consortium (W3C). 2016., 2018, Web Accessibility Evaluation Tools List. Retrieved
- World Wide Web Consortium (W3C)., 2016, Retrieved
- World Wide Web Consortium (W3C)., 2016, Retrieved
- World Wide Web Consortium (W3C). 2018., 2018, Web Content Accessibility Guidelines (WCAG) 2.1. Retrieved
Cited by
Accessibility issues in Android apps: state of affairs, sentiments, and ways forward
Alshayban, A., Ahmed, I., & Malek, S. (2020) · Proceedings of the ACM/IEEE 42nd International Conference on Software Engineering · doi:10.1145/3377811.3380392 · Cited by 142
Unblind your apps: predicting natural-language labels for mobile GUI components by deep learning
Chen, J., Chen, C., Xing, Z., Xu, X., Zhu, L., Li, G., & Wang, J. (2020) · ACM/IEEE International Conference on Software Engineering: Companion Proceedings (ICSE-Companion) · doi:10.1145/3377811.3380327 · Cited by 182
“Many works in Human-Computer Interaction area have explored the accessibility issues of small-scale mobile apps [63, 75] in different categories such as in health [71], smart cities [60] and government engagement [51].”
BackgroundWhy Software is Not Accessible: Technology Professionals' Perspectives and Challenges
Patel, R., Breton, P., Baker, C. M., El-Glaly, Y. N., & Shinohara, K. (2020) · Extended Abstracts of the 2020 CHI Conference on Human Factors in Computing Systems · doi:10.1145/3334480.3383103 · Cited by 96
“Despite such efforts in computing education, it is not clear that the technology industry has increased focus on accessibility as mainstream mobile technologies remain inaccessible [1,2,22].”
BackgroundAccessible or Not? An Empirical Investigation of Android App Accessibility
Chen, S., Chen, C., Fan, L., Fan, M., Zhan, X., & Liu, Y. (2021) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2021.3108162 · Cited by 95
“Yan and Ramachandran [17] adopt the IBM Mobile Accessibility Checker to explore if 479 Android apps violate the accessibility guidelines and calculate the degree of violation.”
BackgroundMethodFinding the Needle in a Haystack: On the Automatic Identification of Accessibility User Reviews
AlOmar, E. A., Aljedaani, W., Tamjeed, M., Mkaouer, M. W., & Elglaly, Y. N. (2021) · CHI Conference on Human Factors in Computing Systems · doi:10.1145/3411764.3445281 · Cited by 77
“Even though user reviews can be a robust tool to mobile apps evolution, and that even mature apps have many trivial accessibility issues [19, 71], only 1.”
Background
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
How to cite
Cite CoChat for the checks on this page, and the paper for its own findings.
- This page
- CoChat. (2026). Citation check: The Current Status of Accessibility in Mobile Apps. https://app.cochat.ai/papers/10.1145/3300176
- The paper
- Yan, S., & Ramachandran, P. G. (2019). The Current Status of Accessibility in Mobile Apps. ACM Transactions on Accessible Computing. https://doi.org/10.1145/3300176
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.