Automated Code Fix Suggestions for Accessibility Issues in Mobile Apps

Forough Mehralian, Titus Barik, Jeff Nichols, Amanda Swearngin
8/7/2024
cs.SEcs.AIcs.HC

No confident code implementation found for this paper.

Abstract

Accessibility is crucial for inclusive app usability, yet developers often struggle to identify and fix app accessibility issues due to a lack of awareness, expertise, and inadequate tools. Current accessibility testing tools can identify accessibility issues but may not always provide guidance on how to address them. We introduce FixAlly, an automated tool designed to suggest source code fixes for accessibility issues detected by automated accessibility scanners. FixAlly employs a multi-agent LLM architecture to generate fix strategies, localize issues within the source code, and propose code modification suggestions to fix the accessibility issue. Our empirical study demonstrates FixAlly's capability in suggesting fixes that resolve issues found by accessibility scanners -- with an effectiveness of 77% in generating plausible fix suggestions -- and our survey of 12 iOS developers finds they would be willing to accept 69.4% of evaluated fix suggestions.

View on arXivView PDF

Code Implementations

No confident code match yet

We couldn't find an author-owned or strongly-evidenced community implementation for this paper. Any repos shown below are weak matches — verify before relying on them.

No code implementations found yet.

Know of an implementation? Let us know in the comments below!

Similar Papers

Cite this paper

@article{mehralian2024automated,
  title  = {Automated Code Fix Suggestions for Accessibility Issues in Mobile Apps},
  author = {Forough Mehralian and Titus Barik and Jeff Nichols and Amanda Swearngin},
  year   = {2024},
  eprint = {2408.03827},
  archivePrefix = {arXiv},
  url    = {http://arxiv.org/abs/2408.03827v1}
}

Add a badge to your README

Shows whether official code is linked for this paper.

Code of Paper badge
[![Code of Paper](https://codeofpaper.com/badge/2408.03827.svg)](https://codeofpaper.com/paper/2408.03827)

Discussion