Skip to content
This repository has been archived by the owner on Aug 14, 2024. It is now read-only.

Accessibility - When Searching Application Does Not Notify Screen Reader User Results Were Found #25

Open
jfc3-dol opened this issue Aug 24, 2017 · 15 comments

Comments

@jfc3-dol
Copy link

While searching from the application it does not notify the screen reader (VoiceOver) user that results were found. The application dumps you on a screen and does nothing else.

@adriennerlong
Copy link

I've flagged this as a high priority issue. We will ask the developers to address before 9/11.

@jfc3-dol
Copy link
Author

@adriennerlong,

Thanks, for getting the developers to fix this item. It's important for those using screen readers.

@jfc3-dol jfc3-dol changed the title Accessibility - When Searching Application Does Not Notify Screen Reader User Resutls Were Found Accessibility - When Searching Application Does Not Notify Screen Reader User Results Were Found Aug 30, 2017
@jfc3-dol
Copy link
Author

VoiceOver now starts reading the search results but starts with the plain text and not a top of the list which starts with a link. VoiceOver seems to be reading the items at the end of the screen and not those at the top of the screen.

Leaving this issue open until reading order is corrected.

@adriennerlong
Copy link

John, if we remove the sub-headings under the search results so that the results only contain links to the relevant pages, will this address the issue?
search results edited

@jfc3-dol
Copy link
Author

jfc3-dol commented Sep 1, 2017

@adriennerlong,

That makes sense if the text is going to be like that.

Can we also make the links part of an un-ordered list so a screen reader user be told there is an un-ordered list with fifteen items. Doing so always the user to know how many results that are in the page/screen.

@adriennerlong
Copy link

That sounds good. ICF, please remove the sub-headings in the search results and make the links an un-ordered list.

@jfc3-dol
Copy link
Author

jfc3-dol commented Sep 7, 2017

@adriennerlong,
VoiceOver starts reading the results as soon as they are on the screen.

If you do a second search, it does not do that.

Also, if a person searches for something and does not find it, there is no message saying there are no search results found. Will open another issue to correct this functional issue.

@jfc3-dol
Copy link
Author

Not able on the Android to use TalkBack to enter information in the search input field.

@adriennerlong
Copy link

From ICF: Partially fixed. Issue with the underline may still exist.

@jfc3-dol
Copy link
Author

jfc3-dol commented Nov 1, 2017

VoiceOver now reads the search results once if the application finds items that match your search criteria.

As stated in another issue the first text on the screen in the main content section say "true No results found.". not sure why that is on the screen. I'm thinking it was debugging messages that were left int he application.

I search term I tested with was the following text "test" which is found records and had the above message. I then tested with "testtt" and the message "false No results found.".

I would expect when I found records that the application might tell me how many results it found.

@jfc3-dol
Copy link
Author

jfc3-dol commented Nov 3, 2017

TalkBack now reads the search results once if the application finds items that match your search criteria.

As stated in another issue the first text on the screen in the main content section say "true No results found.". not sure why that is on the screen. I'm thinking it was debugging messages that were left int he application.

I search term I tested with was the following text "test" which is found records and had the above message. I then tested with "testtt" and the message "false No results found.".

I would expect when I found records that the application might tell me how many results it found.

@ghost
Copy link

ghost commented Nov 27, 2017

The app now displays the number of results found ... but the voice over focus (black background) is somewhere in the middle of the page rather than on the first link

@jfc3-dol
Copy link
Author

For the Android native application TalkBack read "10 results found" for the search term "test". Then the ten results were read after that TalkBack stated "10 results found" twice. Next, "Main" eight or ten times. I didn't count, but my guess would be ten times to match the number of results.

When I used the search term "testt" I got zero results found. TalkBack read the information as the following: "zero results found", "ten results found", "zero results found", "zero results found", and then "double tap to activate".

@jfc3-dol
Copy link
Author

The page now does not contain the "true" and "false" text before the number of search results found.

For the iOS version of the application VoiceOver is reading the list of search results twice.

On some screens when I toggle the search icon the cursor focuses in the INPUT field and on other screens it does not. One screen it does not focus the user is the main home screen. Two of the screens it does focus the user is the "What are Child Labor and Forced Labor?" and the "About This App" screens.

@jfc3-dol
Copy link
Author

When I re-tested on both of our Android devices with the newest version of the application, I get the following results.

For the Android native application TalkBack read "10 results found for test" for the search term "test". Then the ten results were read after that TalkBack stated "10 results found for test 10 results found for test". Next, TalkBack read "Main" eight or ten times. I didn't count, but my guess would be ten times to match the number of results. Plus, it said, "10 results found for test double tap to activate".

I know I have a newer version because the search results screen has the following text "10 results found for test". The older version did not have the words "for" and the search term.

Similar results happen for iOS too.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants