Countries - Main List Screen and Individual Country Screen - Search Function Does Not Notify VoiceOver Users

[jfc3-dol]

When using the search function as you type the countries name the auto populate does not notify anyone using VoiceOver that they are there. Plus, when you tap the enter key it does not say you have found any countries. I first attempted to look for China and VoiceOver told me nothing. VoiceOver should say it's putting up countries that start with "CH" or that there is nothing found for your search results.

[jfc3-dol]

There is still no notification to the VoiceOver user that Countries, Goods, etc. have been displayed by the auto populate of the search terms.

[jfc3-dol]

VoiceOver is still not notifying the users that there are any countries listed on the Main country list screen or the main goods screen. If you type in the letter "b', you see the list of "X" number of items but are not notified that they are there. Same happens as you add more letters such as "a" so you end up looking for countries that start with "ba".

[jfc3-dol]

VoiceOver is still not notifying the users that there are any countries listed on the Main country list screen or the main goods screen. If you type in the letter "b', you see the list of "X" number of items but are not notified that they are there. Same happens as you add more letters such as "a" so you end up looking for countries that start with "ba".

Also, when a VoiceOver user hits the submit button because they are not told the results are automatically, they are not told there are any results and how many there are.

[jfc3-dol]

When searching from the "Goods" screen, VoiceOver does not tell the user how many countries it has found. The same applies to the "Countries" search.

[jfc3-dol]

VoiceOver is now announcing who any items it has found, but when I tap the "Search" key, it does not announce the number. So I'm going to keep the issue open.

[harpreetsdev]

@jfc3-dol
For this issue there isn't a lot that can be done, since the search functionality is more of an auto-populate (As-You-Type-suggestions) type of search. So when you begin typing the search term or even an alphabet, you already see suggested results announced and the focus moving out of the search bar. The Voice over focus is ready to announce returned results. The VO focus more or less moves on before the user would have a chance to tap on the "Search" key.

Tapping the keyboard search key usually adds value when you use traditional search functionality where user would enter the entire search term and the focus is still within Search box to invoke search algorithm.

Please let me know what you think.

@pbhatt17 @Abychalil

[jfc3-dol]

@harpreetsdev @pbhatt17 @Abychalil

I will give it a look early next week.

[jfc3-dol]

@pbhatt17

VoiceOver now reads out the number of a given letter or set of letters for the searches, such as "4 results for ba". If you clear out all the letters, VoiceOver reads for Goods "157 results for," which is weird and a bit confusing. It might be something to create a new issue to fix that in the future.

Let me leave this open to remind me while we talk about it at our next meeting.

[pbhatt17]

@jfc3-dol
This issue was resolved some time back. Please check again and close it.

[jfc3-dol]

@pbhatt17

I now get VoiceOver to tell me how many search results it found when searching for a country that starts with a given letter.

But I'm having an issue getting out the search INPUT field to get to them, which can be a user error. So need to look at how to do that with VoiceOver.

[jfc3-dol]

@pbhatt17

After doing some research, I found the following BBC article ( https://www.bbc.co.uk/accessibility/forproducts/guides/mobile/keyboard-trap/ ) on adding code to get unstuck (keyboard trap) from the search INPUT field.

Not sure how up-to-date the code recommendations are, but I can not swipe out of the search INPUT field after it auto-populates results for a given letter or to the circle with the "X" in it (clear button) while using VoiceOver. I can get to the results by tapping towards the top of the screen away from the bottom of the screen where the keyboard is located.

The issue also has code for Android and the web too.

I assume all the search fields in the different applications might have this issue.

If necessary, I can create a new issue for this and then close this one.