The making of accessible Android applications: an empirical study on the state of the practice
Open accessThe DOI matches its Crossref record; 50 of the 52 references it cites were found in a registry or an index; none of the 10 sources its claims cite is checked for support yet.
Abstract
Nowadays, mobile applications represent the principal means to enable human interaction. Being so pervasive, these applications should be made usable for all users: accessibility collects the guidelines that developers should follow to include features allowing users with disabilities (e.g., visual impairments) to better interact with an application. While research in this field is gaining interest, there is still a notable lack of knowledge on how developers practically deal with the problem: (i) whether they are aware and take accessibility guidelines into account when developing apps, (ii) which guidelines are harder for them to implement, and (iii) which tools they use to be supported in this task. To bridge the gap of knowledge on the state of the practice concerning the accessibility of mobile applications, we adopt a mixed-method research approach with a twofold goal. We aim to (i) verify how accessibility guidelines are implemented in mobile applications through a coding strategy and (ii) survey mobile developers on the issues and challenges of dealing with accessibility in practice. The key results of the study show that most accessibility guidelines are ignored when developing mobile apps. This behavior is mainly due to the lack of developers’ awareness of accessibility concerns and the lack of tools to support them during the development.
Overview
CoChat Summary
TL;DR
This mixed-method study examines how Android accessibility guidelines are implemented in practice and how developers perceive accessibility. It finds that most guidelines are ignored in top-rated Android apps, largely due to limited developer awareness and insufficient tool support.
Key findings
- No app implemented all accessibility guidelines; across 50 top-rated Android apps, coverage ranged from 24% to 63%, with an average of 41%. Of 54 guidelines, 94% (51/54) were assessable in the apps.
- Some guideline categories were more implemented than others: “Images” had the highest implementation ratio (37/41), while “Audio and Video” had the highest violation ratio, with only 44% of assessable guidelines implemented. “Design” had the highest average number implemented (28.8 out of a maximum of 50), with “Style and readability” at 47 and “Spacing” at 45; “Audio and Video” was least implemented (average 3.6), and “Volume control” was implemented in only 2 of 50 apps.
- Developers largely viewed accessibility as important: 60% considered it very important, and only 3 developers (4%) considered it negligible. Main reasons for implementing guidelines were personal ethics (39%) and widening the potential user base (37%); only 7% reported company policies ensuring mobile accessibility.
- 77% of survey respondents did not use tools to verify accessibility guideline implementation; the remaining 13% reported using Accessibility Scanner, Google Play pre-launch report, and beta tests with users. Top challenges included raising awareness of accessibility and disabled users’ needs, standardizing guidelines, implementing guidelines without compromising aesthetics/functionality, involving more disabled users, and raising company/customer awareness.
Methods
- Mixed-method design combining manual coding of Android apps with a developer survey and semi-structured interviews.
- RQ1 manually tested 50 top-rated open-source Android apps from the AndroidTimeMachine dataset against 54 accessibility guidelines across 11 categories, using a closed-coding strategy and an Excel data extraction form.
- RQ2 surveyed Android developers (paper reports 75 respondents in the results, though the introduction says 70) and conducted follow-up semi-structured interviews (paper reports eight interviews in the results/conclusion, though the introduction says ten). Closed questions were analyzed with descriptive statistics; open answers underwent iterative content analysis.
Limitations
- The paper states that findings are mainly valid for the 50 top-rated open-source Android apps and 75 survey respondents, and cannot be generalized to closed-source or industrially developed apps; larger-scale replications are needed.
- The paper states that manual coding and open-answer analysis were led mainly by the first author, though other authors validated and discussed the work; the survey response rate could not be estimated because dissemination reached an unknown number of developers.
- Evident from the text: participant and interview counts vary across sections (70 vs. 75 developers; ten vs. eight interviews), and the reported tool-use percentages (77% do not use tools, 13% use tools) do not sum to 100%.
Model-written summary. Check it against the paper before relying on it.
Integrity signals
Registry
Cites
Statistics
Figures








Verification
Claims the paper makes
0 Valid · 1 Not valid · 7 Not checked · 108 Own results and interpretations
A result the paper reports from its own data — it cites no other source for it, so there is none to check. The quote shows it is in the paper.
In the paper
“The key results yielded by our study are that only a subset of the available guidelines is typically implemented in Android apps, and these mainly relate to aspects like color contrast and interactive content.”
§ The making of accessible Android applications: an empirical study on the state of the practice > Introduction
plain- Asserted: passes — The authors put it forward as true.
- Checkable: passes — It can be checked against evidence.
- Load-bearing: passes — The paper’s conclusions depend on it.
- Based: passes — The paper gives a reason why it holds.
- Rests on an assumption not shown here.
A result the paper reports from its own data — it cites no other source for it, so there is none to check. The quote shows it is in the paper.
In the paper
“we could recognize a general lack of awareness of accessibility concerns”
§ The making of accessible Android applications: an empirical study on the state of the practice > Introduction
hedged- Asserted: passes — The authors put it forward as true.
- Checkable: passes — It can be checked against evidence.
- Load-bearing: passes — The paper’s conclusions depend on it.
- Based: passes — The paper gives a reason why it holds.
- Rests on an assumption not shown here.
A result the paper reports from its own data — it cites no other source for it, so there is none to check. The quote shows it is in the paper.
In the paper
“The key results of the study show that most accessibility guidelines are ignored when developing mobile apps.”
- Also stated in: § Introduction · plain
“The key results yielded by our study are that only a subset of the available guidelines is typically implemented in Android apps, and these mainly relate to aspects like color contrast and interactive content.”
§ The making of accessible Android applications: an empirical study on the state of the practice > Abstract
plain- Asserted: passes — The authors put it forward as true.
- Checkable: passes — It can be checked against evidence.
- Load-bearing: passes — The paper’s conclusions depend on it.
- Based: passes — The paper gives a reason why it holds.
- Rests on an assumption not shown here.
- Also stated in: § Introduction · plain
A result the paper reports from its own data — it cites no other source for it, so there is none to check. The quote shows it is in the paper.
In the paper
“developers indicated the lack of (semi-)automated support to control accessibility while developing mobile applications.”
§ The making of accessible Android applications: an empirical study on the state of the practice > Introduction
hedged- Asserted: passes — The authors put it forward as true.
- Checkable: passes — It can be checked against evidence.
- Load-bearing: passes — The paper’s conclusions depend on it.
- Based: passes — The paper gives a reason why it holds.
- Rests on an assumption not shown here.
A result the paper reports from its own data — it cites no other source for it, so there is none to check. The quote shows it is in the paper.
In the paper
“The vast majority of the participants did not consider this guideline hard to implement.”
§ The making of accessible Android applications: an empirical study on the state of the practice > Analysis of the Results > RQ2. The Developer’s Take on Accessibility
plain- Asserted: passes — The authors put it forward as true.
- Checkable: passes — It can be checked against evidence.
- Load-bearing: unclear — It is unclear whether the paper’s conclusions depend on it.
- Based: passes — The paper gives a reason why it holds.
45 more claims
Create a free account to see all 116 claims and to verify the 10 references still open.
- Probably not a substantial claim. 42
- It may state two separate claims as one. 36
- The quote only partly states this claim. 2
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?
The cited source says what the claim attributes to it.
In the citing paper
“Furthermore, this review is in line with other studies in that accessibility guidelines need to be improved.”
From The accessibility of digital technologies for people with visual impairment and blindness: a scoping review (2024) · cites this paper as [3]
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
Each contradiction between two passages listed here was confirmed by an independent check.
Rated minor: it would not touch a result — a value no result rests on, a p-value that stays on the same side of the significance level, or a conflict that is clerical, resolved elsewhere in the paper, or outside its own findings.
In the paper
§ The making of accessible Android applications: an empirical study on the state of the practice > Analysis of the Results > RQ2. The Developer’s Take on Accessibility
“77% of the respondents do not use tools.”
§ The making of accessible Android applications: an empirical study on the state of the practice > Analysis of the Results > RQ2. The Developer’s Take on Accessibility
“The remaining 13% reported the usage of the Accessibility Scanner app, the Google Play pre-launch report, and the definition of beta tests with users.”
Rated minor: it would not touch a result — a value no result rests on, a p-value that stays on the same side of the significance level, or a conflict that is clerical, resolved elsewhere in the paper, or outside its own findings.
In the paper
§ The making of accessible Android applications: an empirical study on the state of the practice > Introduction
“Then, we conducted a survey study with 70 mobile developers and ten semi-structured interviews”
§ The making of accessible Android applications: an empirical study on the state of the practice > Analysis of the Results > RQ2. The Developer’s Take on Accessibility
“our survey was answered by a total of 75 developers”
Rated minor: it would not touch a result — a value no result rests on, a p-value that stays on the same side of the significance level, or a conflict that is clerical, resolved elsewhere in the paper, or outside its own findings.
In the paper
§ The making of accessible Android applications: an empirical study on the state of the practice > Research Methodology > Execution of the Empirical Study
“The first one presents a total of nine questions about accessibility and how developers consider it in practice.”
§ The making of accessible Android applications: an empirical study on the state of the practice > Research Methodology > Execution of the Empirical Study
“| 10 | Do you use any tool to verify the implementation | Open answer |”
Rated minor: it would not touch a result — a value no result rests on, a p-value that stays on the same side of the significance level, or a conflict that is clerical, resolved elsewhere in the paper, or outside its own findings.
In the paper
§ The making of accessible Android applications: an empirical study on the state of the practice > Introduction
“ten semi-structured interviews”
§ The making of accessible Android applications: an empirical study on the state of the practice > Conclusion
“conducting eight semi-structured interviews”
Rated minor: it would not touch a result — a value no result rests on, a p-value that stays on the same side of the significance level, or a conflict that is clerical, resolved elsewhere in the paper, or outside its own findings.
In the paper
§ The making of accessible Android applications: an empirical study on the state of the practice > Discussion and Implications > Conclusion 1—Accessibility Problems are Widespread in Apps
“We discovered that, in each app, most of the guidelines were not considered by developers in the implementation phase or incorrectly applied.”
§ The making of accessible Android applications: an empirical study on the state of the practice > Analysis of the Results > RQ1. Accessibility Guidelines in Practice
“In the best case, 63% of the guidelines were implemented.”
Citations
Cites
Accessibility of information on the web
Lawrence, S., & Giles, C. L. (1999) · Nature · doi:10.1038/21987 · Cited by 1,349
Technical Debt: From Metaphor to Theory and Practice
Kruchten, P., Nord, R. L., & Ozkaya, I. (2012) · IEEE Software · doi:10.1109/ms.2012.167 · Cited by 735
IWARSSON, S., & STÅHL, A. (2003) · Disability and Rehabilitation · doi:10.1080/dre.25.2.57.66 · Cited by 724 · cited 1×
“According to Iwarsson and St˚ahl (2003), accessibility is defined as “the quality of being easily reached, entered or used by people with disabilities” .”
BackgroundSoftware engineering issues for mobile application development
Wasserman, A. I. (2010) · Proceedings of the FSE/SDP workshop on Future of software engineering research · doi:10.1145/1882362.1882443 · Cited by 515 · cited 1×
“Mobile applications, a.k.a. apps, are nowadays used by billion users for any social and emergency connectivity (Wasserman 2010).”
BackgroundA Survey of App Store Analysis for Software Engineering
Martin, W., Sarro, F., Jia, Y., Zhang, Y., & Harman, M. (2017) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2016.2630689 · Cited by 459 · cited 4×
“However, differently from iOS, accessibility work in A NDROID apps is very limited (Martin et al. 2016; Yan and Ramachandran 2019) and, as such, it is unclear to what extent developers implement universal design principles or use accessibility features in their mobile applications.”
BackgroundMethodInfluentialAccessibility of information on the Web
Lawrence, S., & Giles, C. L. (2000) · intelligence · doi:10.1145/333175.333181 · Cited by 230
Web Accessibility for People with Disabilities
Paciello, M. (2000) · CRC Press eBooks · doi:10.1201/9781482287134 · Cited by 217 · cited 2×
“…Sloan et al. 2006), and many books are now available to drive developers toward the construction of accessible websites (Harper and Yesilada 2008; Paciello 2000; Rutter et al. 2007), the definition of accessibility principles and guidelines for mobile applications can be still considered a work…”
BackgroundWeb accessibility design recommendations for people with cognitive disabilities
Friedman, M. G., & Bryen, D. N. (2007) · Technology and Disability · doi:10.3233/tad-2007-19406 · Cited by 171 · cited 2×
“However, differently from iOS, accessibility work in A NDROID apps is very limited (Martin et al. 2016; Yan and Ramachandran 2019) and, as such, it is unclear to what extent developers implement universal design principles or use accessibility features in their mobile applications.”
BackgroundThe Current Status of Accessibility in Mobile Apps
Yan, S., & Ramachandran, P. G. (2019) · ACM Transactions on Accessible Computing · doi:10.1145/3300176 · Cited by 165 · cited 5×
“Ensuring the accessibility of the app functionalities has become more crucial than ever (Yan and Ramachandran 2019) when people affected by disabilities are more dependent on their mobile devices.”
BackgroundInfluentialHow developers engage with static analysis tools in different contexts
Vassallo, C., Panichella, S., Palomba, F., Proksch, S., Gall, H. C., & Zaidman, A. (2020) · Empirical Software Engineering · doi:10.1007/s10664-019-09750-5 · Cited by 161
Self-citation
Research works printed but not linked: 5
- Di Gregorio M, Di Nucci D, Palomba F, Vitiello G (2021) The making of accessible android applications: an empirical study on the state of the practice—replication package https://tinyurl.com/accessible-mobile-apps · DOI
- Milne L R, Bennett C L, Ladner R E (2014) The accessibility of mobile health sensors for blind users. In: International technology and persons with disabilities conference scientific/research proceedings (CSUN 2014), pp 166–175
- Park K, Goh T, So H -J (2014) Toward accessible mobile application design: developing mobile application accessibility guidelines for people with visual impairment. In: Proceedings of HCI Korea, HCIK ’15. Seoul, Hanbit Media, Inc, pp 31–38
- Rossi P H, Wright J D, Anderson A B (2013) Handbook of survey research. Academic Press
- Turkle S (2011) Evocative objects: things we think with. MIT Press
Cited by
Hamideh Kerdar, S., Bächler, L., & Kirchhoff, B. M. (2024) · Discover Computing · doi:10.1007/s10791-024-09460-7 · Cited by 41
“For example, on the topic of the accessibility of mobile applications, Di Gregorio et al. [3] argued that, although there has been increased interest in accessibility and the development of ATs, there is room for improvement in accessibility guidelines for mobile applications.”
Cognitive Accessibility of Digital Payments: A Literature Review
Dai, J., Miedema, J., Hernandez, S., Sutton-Lalani, A., & Moffatt, K. (2023) · International Web for All Conference (W4A) · doi:10.1145/3587281.3587294 · Cited by 34
“Identified barriers include a lack of empathetic understanding/awareness of accessibility concerns [17, 20, 53], organizational aid [53], and supporting tools [20].”
BackgroundAutomated and Context-Aware Repair of Color-Related Accessibility Issues for Android Apps
Zhang, Y., Chen, S., Fan, L., Chen, C., & Li, X. (2023) · ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering (ESEC/FSE) · doi:10.1145/3611643.3616329 · Cited by 22
“In fact, although the repair of the apps highly depends on the detection report, if the other effective detection tools can be integrated in the future, Iris also works for them because it is scalable in practice.”
BackgroundHow accessibility affects other quality attributes of software? A case study of GitHub
Zhao, Y., Gong, L., Yang, W., & Zhou, Y. (2023) · Science of Computer Programming · doi:10.1016/j.scico.2023.103027 · Cited by 8
Matraf, M. S. B., Hashim, N. L., & Hussain, A. (2023) · Journal of Information and Communication Technology · doi:10.32890/jict2023.22.3.5 · Cited by 8
Metadata
- Authors
- Di Gregorio, M., Di Nucci, D., Palomba, F., & Vitiello, G.
- Affiliations
- University of Salerno (IT)
- Venue
- Empirical Software Engineering
- Published
- 2022-08-06
- Volume
- 27
- Issue
- 6
- Pages
- 145-145
- ISSN
- 1382-3256 (ISSN-L)
- 1573-7616
- PMC
- PMC9356958
- OpenAlex
- W4289978539
- Cited by
- 25
- References
- 52
- Citations by year
- 2026: 8 · 2025: 6 · 2024: 4 · 2023: 7
- FWCI
- 10.98
- Type
- journal article
- Language
- en
- Open access
- hybrid
- doi.org
- Licence
- cc-by
- creativecommons.org/licenses/by/4.0 (tdm)
- creativecommons.org/licenses/by/4.0 (vor)
- Locations
- Empirical Software Engineering (publishedVersion, cc-by)
- PubMed Central (publishedVersion, cc-by)
- PubMed (publishedVersion)
- Funders
- European Commission (825040)
- Schweizerischer Nationalfonds zur Förderung der Wissenschaftlichen Forschung (PZ00P2 186090)
- Università degli Studi di Salerno
- 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 accessibility, Android application, accessibility guidelines, visual impairment, assistive technology, accessibility tools, state of practice, mobile application development
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.
A language model drew the claims from the paper on 2026-10-05, under version 3 of the claim definition (model deepseek-v4.1-flash, prompt extract-v3).
A second model labelled each claim on 2026-10-05 (model jev-1.13-20260917, definition revision gold-guideline-v0.2).
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 making of accessible Android applications: an empirical study on the state of the practice. https://app.cochat.ai/papers/10.1007/s10664-022-10182-x
- The paper
- Di Gregorio, M., Di Nucci, D., Palomba, F., & Vitiello, G. (2022). The making of accessible Android applications: an empirical study on the state of the practice. Empirical Software Engineering. https://doi.org/10.1007/s10664-022-10182-x
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.