W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > July to September 2017

SV: What exactly will trigger a screen reader buffer update?

From: Lars Holm Sørensen <lhs@diversa.dk>
Date: Tue, 5 Sep 2017 12:17:16 +0200
To: "'Jan Hellbusch'" <hellbusch@2bweb.de>, "'WAI IG'" <w3c-wai-ig@w3.org>
Message-ID: <002001d32630$274d0100$75e70300$@diversa.dk>
Hi Jan

Thanks for your reply.

You are right that in most cases the screen reader will update its buffer.

However, as a screen reader user I do still encounter situations, in modern web applications, where I have to perform a manual update of the screen reader buffer. (“Ins” + “Esc” in Jaws)

One example is the Atlassian Jira project management software. When I choose an issue to edit an overlay window opens. In this case my screen reader do not see any content until I have manually updated the buffer. IE 11 + Jaws.
I do not know how that specific overlay window is implemented but it is not the only case where my screen reader do not automatically update the buffer.

Perhaps I should turn my question around and ask if anyone knows which ways of dynamically updating content that should be avoided if one wants to be sure that screen readers will encounter the update in the page?
 
Best regards:
Lars




De bedste hilsner
Lars Holm Sørensen
Diversa ApS
Tlf: 25 21 17 41
www.Diversa.dk

Udelukker du 10% - 20% af brugerne fra din hjemmeside? Se videoen!


-----Oprindelig meddelelse-----
Fra: Jan Hellbusch [mailto:hellbusch@2bweb.de] 
Sendt: Tuesday, September 5, 2017 11:14 AM
Til: 'WAI IG' <w3c-wai-ig@w3.org>
Emne: RE: What exactly will trigger a screen reader buffer update?

Hi Lars,

nowadays screenreaders synchronize DOM and their buffer continuously. Approximately 10 years ago there were problems and screenreaders didn't always catch dynamic updates to page content - that was known as the latency issue. I haven't noticed that problem in many years, now.

Live-Regions are not  connected to that issue.

If you have added content dynamically, you will need to navigate to the new content with a screenreader to check, whether the content is there. It should be.

Jan

--
Jan Hellbusch
Chemnitzer Str. 50, 44139 Dortmund
Tel.: +49 (231) 58054815 Mobil: +49 (163) 3369925
--
Accessibility-Consulting seit 15 Jahren: http://2bweb.de
Blog: www.hellbusch.de
Bücher, Artikel: www.barrierefreies-webdesign.de
Received on Tuesday, 5 September 2017 10:17:52 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 5 September 2017 10:17:52 UTC