Apple

Am 16.01.2011 um 02:48 schrieb George Nachman:

That's a useful page, but it looks like the techniques described there are an alternative to the built-in accessibility APIs. Do many applications decide not to use VoiceOver and do their own speech synthesis? I want to make sure it's a good experience for VO users and not do anything too weird. How weird would it be to go this way?

2011/1/15 Peter Lübke <email@hidden>

Hi George,
take a brief look at:
http://developer.apple.com/library/mac/#documentation/UserExperience/Conceptual/SpeechSynthesisProgrammingGuide/FineTuning/FineTuning.html

- Peter

Am 14.01.2011 um 07:36 schrieb George Nachman:

Hi accessibility-dev,

I have a custom NSView subclass that displays text received from a server. Text comes in unpredictably--sometimes a bunch quickly, sometimes slowly. My goal is to get voiceover to work properly with this. So far what I've done is to post a NSAccessibilityValueChangedNotification notification whenever new text is received and to have -accessibilityAttributeValue: return whatever text is new since its last call as a NSAccessibilityValueDescriptionAttribute (I'm using NSAccessibilityValueIndicatorRole as my NSAccessibilityRoleAttribute). This works, but the problem is that if I get two updates in quick succession, the voiceover for the first one is aborted and the second one is played instead.

I could rate limit them, but to do so optimally would require trying to guess how long voiceover will take to speak a phrase, and I'm sure that's nontrivial. Any better ideas? Can I do this by fiddling with the accessibility hierarchy somehow?

Thanks!
-George