Accessibility Navigation: Voiceover/Talkback errors with Entry/Editor controls #12612
Description
Description
This issue occurs when in Voice Over Mode on iOS or in TalkBack on Android, and using an Editor or an Entry to enter data.
What happens is this, user enters data on an editor/entry and closes the device keyboard by selecting Done. The keyboard closes but the accessibility focus is moved to the topmost item on the page, as if it's starting over again at the top of the accessibility tree. The topmost item could be a label or an image button (I have experienced both in my app).
.
Steps to Reproduce
For iOS (14.4.2) iPhone Xs Max
1. Activate VoiceOver
2. Start app
3. Navigate to Browse Tab
4. Activate Add Button
a. Navigates to Add Page
5. Swipe navigation (left-right)
a. Navigation proceeds as expected, in order through Text Label, Text Entry, Description Label, Description Editor, Cancel Button, Save Button.
6. Navigate to Text Entry, and add text, then activate Return on keyboard.
a. Results: Keyboard closes and accessibility focus is set on Text Label, rather than Description Label or remaining on Text Entry.
b. The requirement that I've been given for my app is to have accessibility focus remain on the Text Entry after closing keyboard.
7. Navigate to Description Editor, and add text, then select "Done" to close keyboard
a. Results: Keyboard closes and accessibility focus is set on Text Label, rather than on Cancel Button or remaining on Description Editor field.
b. The requirement that I've been given for my app is to have accessibility focus remain on the Description Editor after closing keyboard.
For Android (9 - API 28) Samsung SM-N97OU (Galaxy Note 10)
1. Activate Screen Reader/Voice Assistant
2. Start app
3. Navigate to Browse Tab
4. Activate Add Button
a. Navigates to Add Page
5. Swipe navigation (left-right)
a. Navigation does not proceed as expected. Initially the entire view is given accessibility focus in place of the Text Label
b. Continuing to swipe right, accessibility focus is then set to Text Entry, skips Description Label and goes to Description Editor, then proceeds to Cancel Button and Save Button.
6. Navigate to Text Entry, and add text, then activate Done on keyboard.
a. Results: Keyboard closes and accessibility focus remains on Text Entry, as desired.
b. The requirement that I've been given for my app is to have accessibility focus remain on the Text Entry after closing keyboard. So it works as desired here.
7. Navigate to Description Editor, and add text.
a. There is no "Done" button on the keyboard for the user to use to close the keyboard
i. If I change the keyboard type to "numeric" I get a done button and selecting that leaves the accessibility focus on the Description Editor field as expected.
b. The requirement that I've been given for my app is to have accessibility focus remain on the Description Editor after closing keyboard.
For Android (11 - API 30) Samsung SM-A716U (Galaxy A71 5G)
1. Activate Screen Reader/Voice Assistant
2. Start app
3. Navigate to Browse Tab
4. Activate Add Button
a. Navigates to Add Page
5. Swipe navigation (left-right)
a. Navigation does not proceed as expected. Initially the entire view is given accessibility focus in place of the Text Label, and reads aloud "Text Description - double tap to activate". It's reading both labels.
b. Continuing to swipe right, accessibility focus is then set to Text Entry, skips Description Label and goes to Description Editor, then proceeds to Cancel Button and Save Button, then moves to Edge panels.
6. Navigate to Text Entry, and add text, then activate Done on keyboard.
a. Results: Keyboard closes and accessibility focus is not set. Immediately swiping right sets the Accessibility Focus to the full page in place of the Text Label, and reads aloud "Text Description - double tap to activate". It's reading both label.
b. The requirement that I've been given for my app is to have accessibility focus remain on the Text Entry after closing keyboard.
7. Navigate to Description Editor, and add text.
a. There is no "Done" button on the keyboard for the user to use to close the keyboard
i. If I change the keyboard type to "numeric" I get a done button and selecting that leaves the accessibility focus on the Description Editor field as expected.
b. The requirement that I've been given for my app is to have accessibility focus remain on the Description Editor after closing keyboard.
Expected Behavior
After selecting done on an Editor/Entry in voiceover/talkback mode, the user should land on the same field (if it's the last one) or the next one in the tabindex order.
Actual Behavior
After selecting done on an Editor/Entry in voiceover/talkback mode, the user actually lands on the topmost field on the page that is in the accessibility tree.
Basic Information
- Version with issue: 4.8, 5.0.0.2012
- Last known good version: unknown
- IDE: VS Mac / VS Windows
- Platform Target Frameworks:
- iOS: 13.7, 14.4.2
- Android: 9, 11
- UWP:
- Android Support Library Version:
- Nuget Packages:
- Affected Devices: