“编辑”文本框中的文本中的Android可访问性无法正常读取/“再聊后再期待” [英] Android accessibility in Edit text box text not reading properly/Expect After Talk back on

问题描述

我正在为盲人创建应用程序。在那里，当盲人在个人资料注册编辑文本框中输入邮政编码后，例如45987。它的读数为四万五千九百八十七。

I am creating app for blind people. there, when blind people after entered the zip code on that profile registration Edit Text box, like 45987. It reading as Fourty Five Thousand and Nine hundred eighty seven.

我想读四五九八七。 4 5 9 8 7。

But, I want to read an Four Five Nine Eight Seven. 4 5 9 8 7.

注意：当我在TexView中尝试相同操作时，其读数正确。

Note: when i tried for the same in TexView, its reading as correctly. only problem with EditText.

我的示例代码：zipCode_EditText.setContentDescription（ 4 5 9 8 7）;

My Sample Code: zipCode_EditText.setContentDescription("4 5 9 8 7");

我已引用以下链接：

Android Acccessibility: How do I change the text read out loud for an EditText View

如何制作话语提示是否自动读取TextView错误消息？

感谢进阶

推荐答案

最好不要强迫回话执行此操作。我的建议实际上是完全停止这样做。作为盲人，解析单个数字实际上比单个数字更容易。 45,500比4、5、5、0、0更容易记住。在心理上将四万五千九百八十七覆盖到邮政编码成为第二自然。而且，如果有足够长的号码，一次需要检查一个号码，那么话语提示会提供支持该功能的模式。您可以将话语提示切换为字符模式，然后手动进行浏览。

It is best to not force Talk Back to do this. My recommendation would actually be to just stop doing this altogether. As a blind person it is actually easier to parse a single number than individual ones. 45,500 is easier to remember than 4, 5, 5, 0, 0. Covering "forty-five thousand nine-hundred eighty-seven" mentally to a zip code becomes second nature. And if there's a number long enough such that it requires inspection one number at a time, TalkBack has modes to support that. You can switch TalkBack to character mode and explore it like that manually.

此要求实际上仅来自于有见识的人像有见识的人一样思考，并解决了盲人没有的问题。

This requirement really just comes from sighted individuals thinking like a sighted individuals and solving problems blind individuals don't have.

由于另一个用户提出了该建议，因此在Android中编写编辑文本的最佳方法是

And since another user brought it up, the best way to code an edit text in Android is

TextView label = ....
EditText editBox = .....

label.setLabeFor(editBox);

这篇关于“编辑”文本框中的文本中的Android可访问性无法正常读取/“再聊后再期待”的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！