测试应用程序的可访问性(对讲) [英] Test accessibility (talkback) for application

查看:204
本文介绍了测试应用程序的可访问性(对讲)的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在使我的应用程序可访问性兼容。为此,通过在xml中提供android:contentDescription = your string为可访问性框架提供正确的数据。



我也看过《 Android开发人员指南:使应用程序可访问》,概述了需要采取哪些步骤来确保您的应用程序与可访问性服务一起正常工作。



现在的问题是在每个屏幕上对它们进行测试需要更多的时间。我的应用程序有30个屏幕,开启对讲功能后,每次进入任何模块的时间都将近15-20分钟。



有人可以建议工具/更好的测试方法应用程序?

解决方案

@unof是正确的,您可以使用的一种工具是棉绒,向您显示一些有关缺少内容描述的警告。 / p>

我还在尝试Google无障碍测试框架,它可以帮助您自动化一些测试:
https://github.com/google/Accessibility-Test-Framework-for-Android



此外,一个好的建议是使用支持对讲的仿真器,我正在使用安装了Gapps的Genymotion,并且在某些情况下比使用实际设备容易/快捷得多,如果您将要测试多个手势,我建议您使用Genymotion远程控制功能:
https://docs.genymotion.com/Content/03_Virtual_Devices/Emulating_sensors_and_features/Remote_control.htm
在需要时非常方便



这仍然是您必须要做的手动任务,因此请对其进行调整。

>

转到辅助功能设置并提高说文本的速度:
http://developer.android.com/design/patterns/accessibility.html#tools



了解一些手势并浏览话语提示设置也很有帮助:
https://support.google.com/accessibility/android/answer/6006589?hl=zh_CN



我希望它会有所帮助!


I am making my application accessibility compliant. for this providing correct data to the accessibility framework by giving android:contentDescription="your string" in xml.

Also I have Seen the Android Developer guide on Making Applications Accessible for an overview of what steps you need to take to ensure your application works correctly with accessibility services.

Now problem is testing these all in each and every screen taking more time. my app has 30 screens and each time to go to any module will take almost 15-20 mins when talk back is on.

can anyone suggest tool/ better way to test app?

解决方案

@unof is right, one tool you can use is lint to show you some warnings for missing content description.

I'm also experimenting with the Google Accessibility Test framework, it can help you to automate some of your tests: https://github.com/google/Accessibility-Test-Framework-for-Android

Besides that also a good advice is to use an emulator that supports talk back, I'm using Genymotion with Gapps installed and is much easier/faster for some cases than using the actual device, if you are going to test multiple gestures, I'll recommend using Genymotion remote control feature: https://docs.genymotion.com/Content/03_Virtual_Devices/Emulating_sensors_and_features/Remote_control.htm it's very handy in situations when you need to track your network request while using the two fingers for scroll as accessibility requires.

Still is a manual task you will have to do, so try to tweak it.

Go to the Accessibility settings and increase the speed at which the text is spoken: http://developer.android.com/design/patterns/accessibility.html#tools

It's also helpful to learn some of the gestures, and to explore the TalkBack settings: https://support.google.com/accessibility/android/answer/6006589?hl=en

I hope it helps!

这篇关于测试应用程序的可访问性(对讲)的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆