A 17-million-element study links missing GUI accessibility labels to both agent-training debt and benchmark selection bias
A paper submitted on November 11 and accepted at AISSA 2026 analyzes 17,373,614 interface elements in Rico and AndroidControl. Under the authors' coding rule, content-description coverage among elements that need it is 17.74% and 57.27%, respectively. Input controls are the least labelled role in both corpora.
Why it matters
Computer-use agents and screen readers consume the same accessibility tree. Missing labels exclude users and remove interface semantics from agent training, evaluation, and operation. If benchmark demonstrations disproportionately touch the elements that happen to be labelled, reported agent capability can also be optimistic.
A closer look
The authors resolve 26,205 task actions to touched elements. Among tappable graphics without text, demonstrations touch described elements 9.0 percentage points more often than other elements on visited screens, with about 3.5 points from within-screen target selection. Two coders independently label 300 elements, reaching κ=0.96 for role and κ=0.91 for label status. The codebook, pipeline, and number-trace repository are public.
Who this is for
Research, product, and engineering teams training or evaluating GUI agents, building generative interfaces, or maintaining mobile corpora, accessibility trees, and benchmarks.
Original sources
- arXiv primary paper and reproducibility repository ↗arxiv.org
- Methods and reproducibility repository ↗github.com
Revisions & corrections (1)
— New primary empirical research with a reproducibility repository; dates, sample sizes, effects, and limits verified.