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

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

From: Jan Hellbusch <hellbusch@2bweb.de>
Date: Tue, 5 Sep 2017 11:13:56 +0200
To: "'WAI IG'" <w3c-wai-ig@w3.org>
Message-ID: <014901d32627$4db1bbf0$e91533d0$@2bweb.de> 
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 09:14:23 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 5 September 2017 09:14:24 UTC