voiceover

Voice over doesn't read phone number properly

故事扮演 提交于 2019-11-29 05:08:06
I have phone number in below format 1-1xx-2xx-9565 Currently VO read it as " One (pause) One x x (pause) two x x (pause) minus nine thousand five hundred sixty five ". VO should read it as " One (pause) One x x (pause) two x x (pause) nine five six five ". What could be the problem? Is this wrong phone format? Let's break down what is happening. VoiceOver doesn't know that the text you are presenting is a phone number and treats it like a sentence of text. In that text it tries to find distinct components and read them appropriately. For example, the text "buy 60 cantaloupes" has 3 components,

VoiceOver: force an accessibility element to be selected after a screen transition

南笙酒味 提交于 2019-11-28 06:56:04
I'm in the process of making my iOS app accessible and I'm nearly finished. My app contains several custom screen transitions, and when VoiceOver is on it seems to pick either the top-leftmost element to describe after the transition or, occasionally, a random element. UIAccessibilityTraitSummaryElement looked promising but as I understand it only works when the app is started, not after arbitrary transitions. There doesn't seem to be an accessibility trait or property to specify the preferred order that elements are given VoiceOver focus. Is there any way to force VoiceOver focus? EDIT: iOS 6

Change order of read items with VoiceOver

£可爱£侵袭症+ 提交于 2019-11-28 03:58:31
I have a bunch of buttons on the screen which are positioned intuitively visually but are not read in an intuitive order by VoiceOver. This is because certain buttons like Up and Down are placed above and below each other. However, voiceover starts reading from Left to Right, from Top to Bottom, it seems. This results in voiceover reading the button to the right of "Up" after "Up", instead of reading "Down" immediately afterward. How do I force voiceover to read the button that I want to read? I should mention that I'm using the swipe-to-cycle-through-elements feature on voiceover. All my

Voice over doesn't read phone number properly

爱⌒轻易说出口 提交于 2019-11-27 22:35:41
问题 I have phone number in below format 1-1xx-2xx-9565 Currently VO read it as " One (pause) One x x (pause) two x x (pause) minus nine thousand five hundred sixty five ". VO should read it as " One (pause) One x x (pause) two x x (pause) nine five six five ". What could be the problem? Is this wrong phone format? 回答1: Let's break down what is happening. VoiceOver doesn't know that the text you are presenting is a phone number and treats it like a sentence of text. In that text it tries to find

Get line information from UITextView and NSLayoutManager

时间秒杀一切 提交于 2019-11-27 13:56:32
问题 In order to support the UIAccessibilityReadingContent protocol, I need my UITextView to answer me questions about its lines. These are the methods of the protocol that I need to implement: accessibilityLineNumberForPoint: <- Provided a coordinate, return a line number accessibilityContentForLineNumber: <- Return the text of a given line accessibilityFrameForLineNumber: <- Given a line number, return its frame accessibilityPageContent <- The entire text content. That I have. :) I figure that

Change order of read items with VoiceOver

末鹿安然 提交于 2019-11-27 05:17:27
问题 I have a bunch of buttons on the screen which are positioned intuitively visually but are not read in an intuitive order by VoiceOver. This is because certain buttons like Up and Down are placed above and below each other. However, voiceover starts reading from Left to Right, from Top to Bottom, it seems. This results in voiceover reading the button to the right of "Up" after "Up", instead of reading "Down" immediately afterward. How do I force voiceover to read the button that I want to read

VoiceOver: force an accessibility element to be selected after a screen transition

て烟熏妆下的殇ゞ 提交于 2019-11-27 01:21:55
问题 I'm in the process of making my iOS app accessible and I'm nearly finished. My app contains several custom screen transitions, and when VoiceOver is on it seems to pick either the top-leftmost element to describe after the transition or, occasionally, a random element. UIAccessibilityTraitSummaryElement looked promising but as I understand it only works when the app is started, not after arbitrary transitions. There doesn't seem to be an accessibility trait or property to specify the