[A11y] Add labels for different screens for Talkback reader

When Talkback is on, whenever we click on any option which leads to new screen the reader will automatically read the label associated with that screen first. If in case label in not present then it will read app name i.e. Oppia.

We need correct labels for following screens:

• Onboarding Flow → Onboarding Flow
• Profile Chooser Screen → Profile selection page
• Admin Add Pin → Authorize to add profiles
• Admin Auth (when clicked on Add Profiles) → Authorize to add profiles
• Admin Auth (when clicked on Admin Controls) → Authorize to access Administrator Controls
• Pin Verification → PIN verification
• Add Profile →Add Profile
• Topic Page → Topic Page
• Story Screen / Chapter List → Chapter List
• Revision Card → Skill Page
• Question Player → Practice Mode
• Concept Card → Concept Card
• Exploration Player → Exploration Player
• Hints & Solution Screen → Hints and Solution
• Profile Progress → Profile
• Topics in Progress → Topics in Progress
• Stories Completed →Stories Completed
• Options Screen → Options
• Reading Text Size →Reading Text Size
• Default App / Audio Language →Default Audio Language / App language
• FAQ List → FAQs (Frequently Asked Questions)
• FAQ Single → FAQs (Frequently Asked Questions)
• Help →Help
• App Version → App Version
• Profile List →Profile List
• Profile Edit Screen → <Profile_name>
• Rename Profile → Rename Profile
• Reset Profile PIN →Reset PIN
• Stories for you or Recently Played Screen → Whatever is shown in toolbar/actionbar Approved (This will need slightly bigger changes to code.)

In general if there is a static/fixed Title for the screen, we use that as label. And if there is dynamic title then we need a static label which will not be shown on screen but will be read by the talkback.

Example

https://user-images.githubusercontent.com/9396084/108906068-78b75080-7646-11eb-943e-212e29fc3e98.mp4

In this above video as soon as we double-tap Battery, new screen is opened. The reader first outputs Battery followed by Navigate up, Button and finally Battery again. In this the first Battery output is the label of this new screen which indicates the learner which screen is opened. The second Battery is because we selected the title in the screen and it’s just reading that text. So we need labels for various screens general which matches the title but if the title is dynamic then we need static label.

Note: The above list can change as and when we find more such issues.

[rt4914]

@mschanteltc one concern I have around making the topic/story/etc. activities dynamic is we’re now introducing redundancy for screenreader users. They will be hearing the topic title twice: once for the activity label, and second when they swipe through the toolbar. What benefit do we gain from having this redundancy? In general, I think we should aim to reduce the amount of information we need to convey so that it’s easier to use the UI. WDYT? Edit: well it seems that this is actually standard (e.g. to have the toolbar title & activity label in-sync). However, I’m still leaning toward having static labels for all activities even if the toolbar is dynamic, especially since dynamic titles are probably longer to read out which means the redundancy is more noticeable in those cases.

Thanks for your input Ben! I think as long as the Topic/Story/Revision names are mentioned at some point, we can use the static labels so we can eliminate the redundancies like you mentioned. Should I go ahead and edit the post to reflect this?

@mschanteltc Yes, you can edit the description and add correct labels to reflect correct labels.

[rt4914]

@mschanteltc Can you update the description for 4 pending items Admin Auth (2), Pin Verification and Add Profile ?