MotorEase: Automated Detection of Motor Impairment Accessibility Issues in Mobile App UIs
Not on the map. Why?
Abstract (arXiv)
Recent research has begun to examine the potential of automatically finding and fixing accessibility issues that manifest in software. However, while recent work makes important progress, it has generally been skewed toward identifying issues that affect users with certain disabilities, such as those with visual or hearing impairments. However, there are other groups of users with different types of disabilities that also need software tooling support to improve their experience. As such, this paper aims to automatically identify accessibility issues that affect users with motor-impairments. To move toward this goal, this paper introduces a novel approach, called MotorEase, capable of identifying accessibility issues in mobile app UIs that impact motor-impaired users. Motor-impaired users often have limited ability to interact with touch-based devices, and instead may make use of a switch or other assistive mechanism -- hence UIs must be designed to support both limited touch gestures and the use of assistive devices. MotorEase adapts computer vision and text processing techniques to enable a semantic understanding of app UI screens, enabling the detection of violations related to four popular, previously unexplored UI design guidelines that support motor-impaired users, including: (i) visual touch target size, (ii) expanding sections, (iii) persisting elements, and (iv) adjacent icon visual distance. We evaluate MotorEase on a newly derived benchmark, called MotorCheck, that contains 555 manually annotated examples of violations to the above accessibility guidelines, across 1599 screens collected from 70 applications via a mobile app testing tool. Our experiments illustrate that MotorEase is able to identify violations with an average accuracy of ~90%, and a false positive rate of less than 9%, outperforming baseline techniques.
Key facts. No citing papers in the map yet (data through 14 Oct 2026). Builds on 17 of its 81 references that are in the map. First posted on arXiv 20 Mar 2024.
Builds on
17 of 81 references.
References · 17
- 2015Faster R-CNN: Towards Real-Time Object Detection with Region Proposal Networkscited by 9,639
- 2021Screen Recognition: Creating Accessibility Metadata for Mobile Applications from Pixelscited by 58
- 2020Unblind Your Apps: Predicting Natural-Language Labels for Mobile GUI Components by Deep Learningcited by 25
- 2019Modeling Mobile Interface Tappability Using Crowdsourcing and Deep Learningcited by 18
- 2020Owl Eyes: Spotting UI Display Issues via Visual Understandingcited by 16
- 2018Automated Reporting of GUI Design Violations for Mobile Appscited by 15
- 2020Translating Video Recordings of Mobile App Usages into Replayable Scenarioscited by 9
- 2023AidUI: Toward Automated Recognition of Dark Patterns in User Interfacescited by 9
- 2018Continuous, Evolutionary and Large-Scale: A New Perspective for Automated Mobile App Testingcited by 7
- 2018How do Developers Test Android Applications?cited by 5
- 2018Detecting and Summarizing GUI Changes in Evolving Mobile Appscited by 4
- 2018Mining Android App Usages for Generating Actionable GUI-based Execution Scenarioscited by 3
5 more
- 2021VET: Identifying and Avoiding UI Exploration Tarpitscited by 3
- 2021V2S: A Tool for Translating Video Recordings of Mobile App Usages into Replayable Scenarioscited by 3
- 2023Translating Video Recordings of Complex Mobile App UI Gestures into Replayable Scenarioscited by 3
- 2015Optimization of Switch Keyboardscited by 1
- 2022TangibleGrid: Tangible Web Layout Design for Blind Userscited by 1
Built on by
Not cited yet.