- From: Janina Sajka <janina@rednote.net>
- Date: Sun, 23 Mar 2025 05:53:41 -0400
- To: Karen Lewellen <klewellen@shellworld.net>
- Cc: "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
Dear Karen: Thank you for alerting us of James' article. I expect it's important for quite a few of us. Unfortunately the link you forward is (at least currently) 404. Can you say where you're forwarding from? I can't tell from your message. best, Janina Karen Lewellen writes: > Hi all, > I am sharing the below article for a couple of reasons. First because the > writer explains quite clearly what contributes to the often poor async > patterns between modern browsers and screen readers. > Second, I am wondering if there might be a tiny way to begin change via > standards? > Here is the article and a bit on the source. > > Date: Sat, 22 Mar 2025 16:20:21 -0400 > Subject: An answer to the busy messages from screen readers > > James Tey who used to be an NVDA developer and is now a Firefox developer describes why communications between browsers and screen readers is synchronous and causes poor performance. > > https://www.jantrid.net/2025/03/20/async-accessibility-apis/https://www.jantrid.net/2025/03/20/async-accessibility-apis/ > > Thoughts? > Karen > -- Janina Sajka (she/her/hers) Accessibility Consultant https://linkedin.com/in/jsajka The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI) Co-Chair, Accessible Platform Architectures http://www.w3.org/wai/apa Linux Foundation Fellow https://www.linuxfoundation.org/board-of-directors-2/
Received on Sunday, 23 March 2025 09:53:46 UTC