一句话：通过实证研究提炼开发者修复策略，提出自动修复 Android 应用颜色对比度可访问性问题的 DroidPalette。
Android 应用常因 UI 颜色配置不当产生颜色对比度不足的可访问性问题，影响视障用户体验；现有修复方法依赖预定义规则，缺乏对替代颜色选择策略的理解，生成的补丁难以同时被用户和开发者接受。为弥补这一空白，作者先对真实应用中开发者修复此类问题的常用策略开展实证研究，再提出自动修复方法 DroidPalette。该方法将实证得到的选色策略编码为修复规则，并结合从 Android 框架与第三方库中识别出的候选修复属性来生成补丁。评估在 105 个真实 Android 应用的 497 个颜色相关可访问性问题上进行，成功率为 66.60%；提交至 GitHub 的 13 个补丁中有 8 个获得开发者的正面反馈。
As Android apps become increasingly prevalent in daily life, a common issue in the development process is the configuration of UI colors, leading to color-related accessibility issues that make the text or non-text on the app’s UI difficult to see due to low color contrast. Such color-related accessibility issues are among the top issues in apps, having a negative impact on vision and user experience. However, state-of-the-art approaches are based on predefined rules and lack an understanding of strategies for alternative colors, therefore failing to generate patches acceptable to both app users and developers. To address this research gap, we first conducted an empirical study to explore common strategies used by app developers when fixing real-world color-related accessibility issues. Based on these findings, we proposed DroidPalette, an automated approach for repairing color-related accessibility issues in Android apps. DroidPalette encodes the common strategies used by app developers for selecting issue-fixing colors, as identified in our empirical study, and combines this with the candidate issue-fixing attributes identified from the Android framework and third-party libraries to generate patches. We evaluated DroidPalette on 497 color-related accessibility issues across 105 real-world Android apps, achieving a success rate of 66.60%. Encouragingly, out of 13 patches submitted to GitHub repositories, 8 have received positive feedback from app developers.
DOI 原文 ·
@inproceedings{paperbot9517,
title = {Characterizing and Repairing Color-Related Accessibility Issues in Android Apps},
author = {Jiahao Gu and Huaxun Huang},
booktitle = {ASE},
year = {2025},
doi = {10.1109/ase63991.2025.00169}
}