When using TalkBack, what is the preferred way to alert the user when the contents of a TextView have changed?

twaddington picture twaddington · Nov 3, 2012 · Viewed 7.5k times · Source

I have an unlock screen where the user is prompted to enter a four digit pin. If the user enters their pin incorrectly, a previously invisible TextView is shown with an error message. At this point it would be useful for TalkBack to read the contents of the error message out loud.

Through some experimentation, I realized I could set android:focusableInTouchMode="true" on the view and programmatically call View#requestFocus(). This works the first time, but fails on subsequent errors since the view already has focus. Also it seems like a bad idea in general to override the current view focus.

I then tried invoking View#announceForAccessibility(java.lang.CharSequence) when the error message is displayed. Apparently this method will silently fail if the view is not currently visible. No problem and otherwise it works perfectly. However, it's only available in API level 16+ (Jelly Bean) which really limits it's usefulness. There has to be a better solution since TalkBack supports API level 7+.

I've watched both the 2011 and 2012 Google I/O sessions on accessibility, but neither seem to cover this basic use case. What's the best way to do this?

Edit 1: TLDR; Is there a way to force TalkBack to read some text out loud prior to the introduction of View#announceForAccessibility(java.lang.CharSequence) in Jelly Bean?

Answer

Techwolf picture Techwolf · Nov 9, 2012

You should be able to use View.sendAccessibilityEvent(AccessibilityEvent.TYPE_VIEW_FOCUSED) on your TextView to trigger TalkBack in the same way that View.requestFocus() would. Since it only triggers the event, and doesn't actually focus the View, it shouldn't crash after the first time.