I tried the updated TTS app from that thread. The new version reads AlertDialog titles and messages now, although it still does not read other non-focusable text on the screen. Perhaps I'm not aware of an input function that will prompt TTS to read the entire screen. I'll take my follow-up questions to that group.
Thanks for the info and link. On Dec 18, 1:13 pm, blindfold <[email protected]> wrote: > You might wish to check if the following recent update addresses your > problem > > http://groups.google.com/group/tts-for-android/browse_thread/thread/2... > > or else bring up your problem on that list. > > Regards > > On Dec 18, 5:55 pm, RNekic <[email protected]> wrote: > > > > > So I tried turning on TalkBack to see how well my application works > > with the feature and I was surprised to discover that TalkBack does > > not speak the title or text of an AlertDialog. It's only speaking the > > text from the buttons I add to the dialog. Am I doing something wrong > > when I define my AlertDialogs or is this intended behavior? > > > Do I need to code specifically against the AccessibilityManager to > > have AlertDialog text (or any other non-focusable text) spoken by > > TalkBack? > > > I'm currently using 1.5 (SDK 3) in my manifest's minSdkVersion. As I > > understand it, I'd have to bump the setting to 1.6 (SDK 4) if i want > > to use the AccessibilityManager. Am I mistaken? I'm reluctant to > > change my minSdkVersion to 4 after seeing how large the v1.5 slice of > > the OS pie still is according to > > Google:http://developer.android.com/intl/fr/resources/dashboard/platform-ver... > > > Is there another solution? -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
