Finally, I managed it by mixing both Talkback(with the use android:setcontentDescription for each widget) and text to speech (android.speech.tts).
On Feb 24, 11:54 pm, kalgik <kal...@gmail.com> wrote: > Dear all, > I have installedTalkBackapplication in Samsung Galaxy S II in order > to see the interaction with a sample application of mine. > I added contentDescritpion to any of the widget of my application. As > I saw, it does not make any difference for Button, ImageView and > Spinner widgets if you added contentDescription.For example, when I > click the Button, TalkBacks says "clicked" without mentioning the > valued from the contentDescription. Moreover, when I focus to > ImageView (by just touching a bit the screen or touching > continuosuly),talkbackdoes not say anything. Is this the right way > that an ImageView is getting focus on, on touch screen devices? > > Do I have to create my own custom components overriding the > corresponding methods and implement AccessibilityEventSource? For > example, is it possible for theTalkBackto "say" the spinner's > current selection?Currently, I manage it by showing the selected value > on an EditText which is focused on. > > Or can I alternatively use the Text to Speech engine API (from the > example) in order to manually enable text to speech? > > Regards,kalgik -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
