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: Wed, 6 Sep 2017 08:51:35 +0200
To: "'Sean Murphy \(seanmmur\)'" <seanmmur@cisco.com>, "'Jan Hellbusch'" <hellbusch@2bweb.de>, "'WAI IG'" <w3c-wai-ig@w3.org>
Message-ID: <006e01d326dc$95977cb0$c0c67610$@diversa.dk>
	Hi Sean and Jan

Thanks for your answers.

So I suppose the best thing to do for now is just to report that kind of issues to the browser vendors and cross the fingers for more reliable behavior in the future. 

Thank you.

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

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

-----Oprindelig meddelelse-----
Fra: Sean Murphy (seanmmur) [mailto:seanmmur@cisco.com] 
Sendt: Wednesday, September 6, 2017 1:29 AM
Til: Jan Hellbusch <hellbusch@2bweb.de>; 'WAI IG' <w3c-wai-ig@w3.org>
Emne: RE: What exactly will trigger a screen reader buffer update?

Hi all,

The actual triggering of the virtual buffer depends on the browser, the accessibility  framework and the screen reader. Depending on how of each these programs communicate with each other determines success or failure. I am aware of specific web sites that visually load fine, while the screen reader/ Accessibility framework and browser don't give the end-user the correct information. The actual defect in this situation appears to be related to the browser. The challenge I see is how to track the issue down?

Sean Murphy
Tel: +61 2 8446 7751

Cisco Systems, Inc.
The Forum 201 Pacific Highway

Think before you print.
This email may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message.
-----Original Message-----
From: Jan Hellbusch [mailto:hellbusch@2bweb.de]
Sent: Wednesday, 6 September 2017 5:58 AM
To: 'WAI IG' <w3c-wai-ig@w3.org>
Subject: RE: What exactly will trigger a screen reader buffer update?

Hi Lars,

> 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)

OK, there are pages that take ages to load (or seem to go into an endless script loop) that will not be read in JAWS. JAWS will only read the page once the page is fully loaded, although everything might be visible on screen. In those cases JAWS+Esc will help.

I have talked to various people in the past about this problem, but I haven't heard of a different strategy to that problem, yet. 

I am sure there are other people on the list that have encountered the same issue. Perhaps somebody else has a solution? I find it quite bothersome, too, but I probably press JAWS+Esc 20 times a day quite unconsciously.


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 Wednesday, 6 September 2017 06:52:12 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 6 September 2017 06:52:12 UTC