WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Where do single page applications fail WCAG2?

for

From: Jonathan Avila
Date: Feb 10, 2015 10:58AM

> I wish I knew what event causes screenreaders to read new pages and not significant amounts of new content. Then perhaps we could fire off that event.

Normally screen readers look for the document's loaded event and probably check the document readyState property.

Jonathan

--
Jonathan Avila
Chief Accessibility Officer
SSB BART Group
<EMAIL REMOVED>

703-637-8957 (o)
Follow us: Facebook | Twitter | LinkedIn | Blog | Newsletter

-----Original Message-----
From: <EMAIL REMOVED> [mailto: <EMAIL REMOVED> ] On Behalf Of Lynn Holdsworth
Sent: Tuesday, February 10, 2015 7:40 AM
To: WebAIM Discussion List
Subject: Re: [WebAIM] Where do single page applications fail WCAG2?

Hi Patrick,

> This sounds more like the focus is actually lost, rather than being programmatically set to the newly shown content.

But is it? If we're mimicking a new page load, which is surely what SPA's are doing, shouldn't the focus behave in the same way as it would if we'd reached a new page?

I wish I knew what event causes screenreaders to read new pages and not significant amounts of new content. Then perhaps we could fire off that event.

Thanks for all your input - it's given me a lot of food for thought. I guess I'll fail this issue under focus order, but it doesn't feel like a great fit to me.

Best, Lynn

On 10/02/2015, Patrick H. Lauke < <EMAIL REMOVED> > wrote:
> On 10/02/2015 10:38, Lynn Holdsworth wrote:
>> And as for focus order, the focus seems to go to the first link in
>> the document, which is where it would go if a whole new page were
>> loaded, so I'm not sure I can fault them on that.
>>
>> What I really want to fail them on is something around AT not being
>> alerted to the fact that new content has loaded. JAWS for one isn't
>> always great at refreshing its off-screen model, and in this case it
>> tells me that I'm still on the Login button, which doesn't exist in
>> the newly loaded view.
>
> This sounds more like the focus is actually lost, rather than being
> programmatically set to the newly shown content. A subsequent TAB
> would then go to the first link in the document, purely because the
> browser actually lost it and reset it to the start of the document.
>
> P
> --
> Patrick H. Lauke
>
> www.splintered.co.uk | https://github.com/patrickhlauke
> http://flickr.com/photos/redux/ | http://redux.deviantart.com
> twitter: @patrick_h_lauke | skype: patrick_h_lauke
> > > list messages to <EMAIL REMOVED>
>