[NFBCS] JAWS DOM changes in web apps?

Lewis Wood lewislwood at gmail.com
Mon Mar 16 11:39:50 UTC 2026


I noticed the same issue.  I am having to do f6 and back with shift f6.

 

Very annoying..

 

From: NFBCS <nfbcs-bounces at nfbnet.org> On Behalf Of Ty Littlefield via NFBCS
Sent: Monday, November 24, 2025 11:57 AM
To: NFB in Computer Science Mailing List <nfbcs at nfbnet.org>
Cc: Ty Littlefield <tyler at tysdomain.com>
Subject: [NFBCS] JAWS DOM changes in web apps?

 

Hi all,

I've been working on some frontend code at work lately, and one of the issues I'm running into is that when content is changed on a page (for example in a react app where a component refreshes), JAWS does not always see these changes. This is a particular problem in a component with a live region, because JAWS will sometimes re-read the prior content in the live region rather than the most recent.

In general, what notifies JAWS of a DOM change? More specifically, are there any tips or tricks for handling this properly from within react/other applications like this that are component based? Generally this doesn't seem to be an issue, but we seem to have a pattern in play that is causing problems with JAWS (NVDA is perfectly fine).

Thanks,

-- 

Ty Littlefield (he/him/his)

*	From Bytes to Bites <https://tysdomain.com> | 
*	Linkedin <https://www.linkedin.com/in/ty-lerlittlefield/> |
*	Github <https://github.com/sorressean> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260316/f478c8e0/attachment.htm>


More information about the NFBCS mailing list