Search: Accessibility

[peterfremlin]

• [x] The line about results gets read multiple times

Screen-reader use hears the line "32 newsletters, 8 pages, and 174 library links found" three times, and for some reason appears just as one link rather than the three separate links.

If there's an obvious fix to this then that's fine, but otherwise feedback from Áine is that we can just remove the links - the sections are navigable by themselves as headings.

• [x] Show results as headings

Results are easier to navigate if they can be put at a heading level (eg h3), so that navigating to next heading gets to the next result

• [x] Emojis not making sense to screenreader

Some of the emojis (like open book) don't make sense when read out and the star emoji was getting read out as 2605. Perhaps the visual indicators can be removed for screenreader users?

• [x] add to filter button -- text tweaked.
• [x] make sure adding to filter triggers a new search Not clear to a screenreader user what happens when this is pressed

[peterfremlin]

Access review from Áine (screen-reader user)

• Search loads, but doesn't advise user that it's loaded
• there is addition text of "submit the search query" - not necessary as button already says search

[cathysarisky]

On the first point - that’s the results? Or when the page first is loaded? I removed the "X page, Y links... " line because Aine said it wasn't necessary, but I think that's what was announcing - what's the desired behavior, please?

[peterfremlin]

It's good to have the line that said "X page, Y links". There were two issues with it

• the line included links to those parts on the page (it's the links to place in page that weren't necessary)
• the line was being announced more than once (perhaps because of the links)

So we should bring that line back, without links in it.

And focus should be shifted to the line that announces the number of results.

[cathysarisky]

"And focus should be shifted to the line that announces the number of results."

It's reading because it is set to role=status. My reading on this is that it should not get focus. See https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/status_role

But I think I've resolved the repeat reading. Wrapping up a few more things and then will get it to you for more testing. :)