android辅助功能_3个适用于Android的辅助功能测试工具

android辅助功能

The Web Accessibility Content Guidelines (WCAG) 2.1 recommendations explain the success criteria for making web and mobile apps accessible to people with disabilities. The guidelines are pretty straightforward, but can be difficult to eyeball, as they make very specific requirements about the visual qualities of text and other on-screen elements. As someone without any recognized disabilities, I find it difficult to spot potential problems on my own, so it’s helpful to use tools to point out where they occur.

《 Web无障碍内容指南》(WCAG)2.1的建议解释了使残疾人能够访问Web和移动应用程序的成功标准。 这些准则非常简单明了，但由于它们对文本和其他屏幕元素的视觉质量有非常特定的要求，因此可能很难引起注意。 作为没有公认的残疾的人，我发现自己很难发现潜在的问题，因此使用工具指出发生问题的位置会很有帮助。

If you don’t know if your app is WCAG compliant, it probably isn’t. Here are three tools that help you get there. Note that these tools do not certify an app for WCAG compliance — they merely help spot certain issues that are possible to assess using Android APIs.

如果您不知道您的应用是否符合WCAG，则可能不符合。 这里有三个工具可以帮助您实现目标。 请注意，这些工具并不对应用程序进行WCAG合规性认证-它们只是帮助发现某些可能使用Android API进行评估的问题。

• Google — Accessibility Scanner (Play Store)

  Google —辅助功能扫描器 ( Play商店 )

• Deque Systems — Accessibility Engine (axe) for Android (Play Store, web)

  Deque Systems —适用于Android的辅助功能引擎(axe) ( Play商店 ， 网络 )

• Microsoft — Accessibility Insights for Android Service (web, GitHub)

  Microsoft-Android服务的可访问性见解 ( web ， GitHub )

These tools require only an installed APK to test on. There are other tools that take a more programmatic approach to testing during development (such as Espresso’s accessibility checking), but I won’t cover those here.

这些工具仅需安装APK即可