E-mail List Archives
Re: error messages only announced by Chrome (using NVDA)
From: Tim Harshbarger
Date: Aug 7, 2017 7:09AM
- Next message: Jim Homme: "Re: VS.NET 2017 inaccessible Installation UI"
- Previous message: JP Jamous: "VS.NET 2017 inaccessible Installation UI"
- Next message in Thread: Angela French: "Re: error messages only announced by Chrome (using NVDA)"
- Previous message in Thread: Birkir R. Gunnarsson: "Re: error messages only announced by Chrome (using NVDA)"
- View all messages in this Thread
I think that might be the best approach.
I had a chance to try some things with the code this weekend--unfortunately due to some problems with the accessibility of the UI for Coe Pen I accidentally deleted the code later. But in those tests, I found out if I used window.setTimeout to add a 5 millisecond delay between when the live region is created and appended to the document and the message is written to the live region that NVDA would then speak the message every time. I wonder if this has to do with the asynchronous nature of javascript. It does not necessarily wait for one command to complete before it processes the next command so it is always possible that the message might be written to the live region before the live region is added to the document. If that is the case, I don't think the message would be spoken. All that is just a guess on my part. But I expect if the aria-live regions already exist on the page prior to the message being written to them that it should speak then.
Thanks,
Tim
- Next message: Jim Homme: "Re: VS.NET 2017 inaccessible Installation UI"
- Previous message: JP Jamous: "VS.NET 2017 inaccessible Installation UI"
- Next message in Thread: Angela French: "Re: error messages only announced by Chrome (using NVDA)"
- Previous message in Thread: Birkir R. Gunnarsson: "Re: error messages only announced by Chrome (using NVDA)"
- View all messages in this Thread