CoChat

The making of accessible Android applications: an empirical study on the state of the practice

Open access
Di Gregorio, Marianna, Di Nucci, Dario, Palomba, Fabio, Vitiello, Giuliana · 2022 · Empirical Software Engineering

The 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

Crossref · 10.1007/s10664-022-10182-x

Cites

50 of 50 references verified0 citation errors · 0 not checkable

Statistics

Nothing to recompute.

Figures

Fig. 1 Guidelines coverage of the 50 apps. A coverage (y-axis) equal to 1 means that all guidelines were implemented in the analyzed apps
Fig. 1 Guidelines coverage of the 50 apps. A coverage (y-axis) equal to 1 means that all guidelines were implemented in the analyzed appsCC BY · PubMed Central
Fig. 2 Percentage of guidelines assessable against percentage of guidelines actually implemented in the considered mobile applications, grouped by category
Fig. 2 Percentage of guidelines assessable against percentage of guidelines actually implemented in the considered mobile applications, grouped by categoryCC BY · PubMed Central
Fig. 3 Distribution of accessibility guidelines implemented, grouped by requirements
Fig. 3 Distribution of accessibility guidelines implemented, grouped by requirementsCC BY · PubMed Central
Fig. 4 Background of our participants
Fig. 4 Background of our participantsCC BY · PubMed Central
Fig. 5 Relevance of the accessibility problem from the developer’s perspective
Fig. 5 Relevance of the accessibility problem from the developer’s perspectiveCC BY · PubMed Central
Fig. 6 Results for Question n.3—what makes you willing (or unwilling) to implement the accessibility guidelines
Fig. 6 Results for Question n.3—what makes you willing (or unwilling) to implement the accessibility guidelinesCC BY · PubMed Central
Fig. 7 Results for Questions n.4 and n.5—awareness and implementation of accessibility guidelines
Fig. 7 Results for Questions n.4 and n.5—awareness and implementation of accessibility guidelinesCC BY · PubMed Central
Fig. 8 Results Questions n.7 and n.7.1—difficulty in implementing the specific guidelines
Fig. 8 Results Questions n.7 and n.7.1—difficulty in implementing the specific guidelinesCC BY · PubMed Central

Verification

Claims the paper makes

0 Valid · 1 Not valid · 7 Not checked · 108 Own results and interpretations

45 more claims

Create a free account to see all 116 claims and to verify the 10 references still open.

See all claims — free account
  • Probably not a substantial claim. 42
  • It may state two separate claims as one. 36
  • The quote only partly states this claim. 2

Create a free account to see these claims.

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?

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.

5 of 5

Citations

Cites

Show all 50 references

Research works printed but not linked: 5

  1. 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
  2. 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
  3. 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
  4. Rossi P H, Wright J D, Anderson A B (2013) Handbook of survey research. Academic Press
  5. Turkle S (2011) Evocative objects: things we think with. MIT Press

Cited by

See all 26

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
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
Licence
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.