- From: Karen Lewellen <klewellen@shellworld.net>
- Date: Sat, 22 Mar 2025 16:48:55 -0400 (EDT)
- To: "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
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
Received on Saturday, 22 March 2025 20:49:04 UTC