在Android对讲无障碍中将缩写或首字母缩写发音为单个字符 [英] Pronounce abbreviations or initialisms as individual characters in androids Talkback accessibility

问题描述

我正在使用对讲功能开发语音可访问性功能，但是当旁白从文本视图中读取文本时，它会将缩写/首字母缩写作为一个单词而不是单个字符来读取。例如，FBI应该是FBI，而不是一个单词。

解决方案

请勿尝试强制屏幕阅读器读取单词或缩写的某种方式。这可能会影响盲文用户的用户体验。屏幕阅读器的设置可以控制详细程度以及如何使用全部大写的单词。

另外，当单词以不熟悉的方式发音时，屏幕阅读器用户可以逐个字母导航到

更新2018年11月29日：
根据评论，这里有一些其他信息。

如果句子中有缩写，例如

  FBI总是让他的人
  

然后您可以为屏幕阅读器隐藏文字迫使字母分别发音，但是我再次要说这是强烈劝阻。

 < p> FBI总是得到他的人< / p> 
  

可以成为

 < p>< span aria-hidden = true> FBI< / span> < span class = sr-only> F B I< / span>总是得到它的人< / p> 
  

因此可见的 FBI对于屏幕阅读器是隐藏的，其后是 FBI，屏幕阅读器将以单独的字母形式宣布。

（ sr-only类可在

在这种情况下，大写字符（单点）必须出现在每个字母之前，因为它们是分开的单词 和每个字母之间都有间隙。

因此， FBI占据5个单元格， FBI占据8个单元格。

第二个缺点是，在iOS设备和Voiceover上，由于段落（< p>）被嵌入的< span>元素分割，因此当您使用Voiceover向右滑动时，会在每次休息时停止，因此您会听到 The，然后是 FBI，然后总是得到它的帮助。不好的用户体验。不确定对讲功能是否也一样。

I am working on an voice accessibility feature using talkback but when the voice over reads of the text from the text view, it reads the abbreviation/initialism as a word instead of individual characters. For example FBI should be F B I and not read out as a word.

解决方案

Do not try to force a screen reader to read words or abbreviations a certain way. That can mess up the user experience for braille users. Screen readers have settings to control the verbosity and what to do with words that are in all caps. This allows the user to control how they want to hear it.

Additionally, when a word is pronounced in an unfamiliar way, the screen reader user can navigate letter by letter to hear the abbreviation.

Update November 29, 2018: Based on comments, here is some additional information.

If you have an abbreviation in the middle of a sentence, such as

The FBI always gets its man

then you can have hidden text for screen readers to force the letters to be pronounced separately, but I will again say that this is highly discouraged.

<p>The FBI always gets its man</p>

can become

<p>The <span aria-hidden="true">FBI</span> <span class="sr-only">F B I </span> always gets its man</p>

So the visible "FBI" is hidden from screen readers and it's followed by a visually hidden text of "F B I" for screen readers to announce as separate letters.

(The "sr-only" class can be seen at What is sr-only in Bootstrap 3?)

There are two (at least) disadvantages to forcing this behavior:

1. As mentioned, Braille users will get extra text. Granted, in this case, it's not that much but still adds to overhead in reading Braille.

   Basic "FBI" in Braille:
   There are two single dots in the beginning. The first single dot usually means the next character is uppercased. When you have two single dots in a row, it's like a "caps lock" so it tells you all the following letters are in caps.

   Embedded spaces in "F B I"
   In this case, the "caps" character (single dot) has to appear before each letter because they're separate "words" and there are gaps between each letter.

   So "FBI" takes up 5 cells and "F B I" takes up 8 cells.

2. The second disadvantage is that on iOS devices and Voiceover, since the paragraph (<p>) is split up by embedded <span> elements, as you swipe right with Voiceover, it will stop on every break so you'll hear "The", then "F B I", then "always gets its man". Not a great user experience. Not sure if Talkback does the same.

这篇关于在Android对讲无障碍中将缩写或首字母缩写发音为单个字符的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！