WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Aria live region

for

From: Steve Green
Date: Oct 7, 2022 7:23AM

I would question whether you need to make screen reader users aware of the number of search results. It is not the normal or expected behaviour on any website I can think of, except when the results are updated without a page reload, in which case the text is a status message and must meet SC 4.1.3.

Unless there is evidence to the contrary, I always advise that you don't change standard behaviours that users expect. By "evidence", I mean user research, not just something that a product owner dreamed up. Alternatively, build prototypes of both versions and conduct user testing so see which performs best.

Steve


-----Original Message-----
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of Geethavani.Shamanna
Sent: 07 October 2022 14:13
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: Re: [WebAIM] [EXTERNAL] Re: Aria live region

That is very interesting, thanks Steve.

So in this instance, if we need to make screen reader users aware of the number of search results displayed on the page without them having to scroll down to view the message, would the best option be to move the focus to that message?

Geetha
-----Original Message-----
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of Steve Green
Sent: 07 October 2022 13:43
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: Re: [WebAIM] [EXTERNAL] Re: Aria live region

CAUTION: This mail comes from outside the University. Please consider this before opening attachments, clicking links, or acting on the content.

It is not a status message. The first part of the WCAG definition of a status message says that a status message is a "change in content that is not a change of context". A change of context occurs when the page loads, so the text cannot be a status message. SC 4.1.3 therefore does not apply.

https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2FWAI%2FWCAG21%2FUnderstanding%2Fstatus-messages%23dfn-status-message&amp;data%7C01%7Cgeethavani.shamanna%40open.ac.uk%7C54aa7b1504524fa7f04608daa86187b7%7C0e2ed45596af4100bed3a8e5fd981685%7C0%7C0%7C638007434082793436%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=TGtTNlt0KfBSue%2FfAdBUUpYZGFCB41hTXccV8iIKEM8%3D&amp;reserved=0

Steve

-----Original Message-----
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of Geethavani.Shamanna
Sent: 07 October 2022 12:39
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: Re: [WebAIM] [EXTERNAL] Re: Aria live region

Hi Mark,

Many thanks for your response.

When the search results are updated, the message 'Your search yielded 15 results' is displayed on the screen. This message is not automatically read out by the screen reader. Rather than moving focus to this message, is it not better practice to get the screen reader to read out this status message (SC 4.1.3)?

Geetha
-----Original Message-----
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of Mark Magennis
Sent: 07 October 2022 11:55
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: Re: [WebAIM] [EXTERNAL] Re: Aria live region

CAUTION: This mail comes from outside the University. Please consider this before opening attachments, clicking links, or acting on the content.

Hi Geethavani,

In a situation like this, some screen reader users prefer focus to be set to the start of the search results list because you can almost guarantee that's where they want to start reading. Specifically, for focus to go to the statement of the number of results, e.g. "showing 1,832 results for xxx. When focus is set to this text, the screen reader will read it automatically (the JAWS bug preventing this is fixed) and there will be no need for a live region to announce the results statement.

I said "some screen reader users prefer", but how many is "some" is open to debate and not all screen reader users or accessibility practitioners would agree with this approach. Some would prefer, as Steve says, for the screen reader to be left to do what it naturally does. My interactions with screen reader users makes me inclined towards the "move focus" approach, but I know Steve also has a lot of insight into what users want and need, having done a lot of user testing with real users.

Also note, if there is no actual page load (e.g. you have a single page application) then you are going to have to place focus somewhere anyway. This could be top of page, results statement, or anywhere else you think is appropriate.

Mark

-----Original Message-----
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of Steve Green
Sent: Friday 7 October 2022 11:30
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: [EXTERNAL] Re: [WebAIM] Aria live region

You should not be using a live region if the page reloads. Your screen reader is doing what it's designed to do when a new page loads, and there's nothing you can do to stop it. Indeed, you shouldn't do anything to stop it.

Steve Green
Managing Director
Test Partners Ltd


-----Original Message-----
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of Geethavani.Shamanna
Sent: 07 October 2022 11:16
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: [WebAIM] Aria live region

Hello all,

I am currently testing a search page where aria live region is implemented. On entering a search term and activating the Search button, the page reloads and my screen reader starts reading text from the top of the page, instead of announcing the number of search results. The number of search results as well as the time taken to search are displayed on the page, but this is not announced by the screen reader.

Can this be resolved by using the status role and by setting aria-atomic attribute to false? How can we ensure that the screen reader announces only the updated status message?

Many thanks.
Geetha