Convert all intros to TextViews or TTS

[mcrossman]

Convert TTS intros into TextViews for easier navigation.

Not necessary for live readouts. These should instead use TTS engine as per usual and preferring announcements if possible (see #104).

Key considerations

Focus issues

TalkBack may focus on the wrong block of text. You'll need to use

View.sendAccessibilityEvent(AccessibilityEvent.TYPE_VIEW_FOCUSED)

to make sure that it starts at the beginning.

Design approach

It's fine to start by moving TTS content straight into TextViews (i.e. pointing a TextView to the same string resource).

However, if it gets too long that a repeat instruction gets annoying, you should break it up. In lessons after Lesson 3, you can use paragraphs by adding line breaks (\n) into your strings. The user should understand how to jump paragraphs at this point.

Rephrase prompts/rethink your layout

Some strings tell people to do something immediately. This may not work as they'll be, for example, on a TextView instead of the intended continue button.

However, it might work better to take what comes after the continue button and instead just put it underneath the TextView.

[Chokss54]

Converted TTS intro to text. However, for jump text char reading mode TTS is still used because of the bug where android talkback will skip text elements if the fragment has less text elements from the previous fragment