WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: error messages only announced by Chrome (using NVDA)

for

From: Reinhard Stebner
Date: Aug 4, 2017 5:24AM

I tested this on voiceover on the iPhone and saw exactly what you're talking about. Just want to give you a quick update from her use her using voiceover on the iPhone.

Sent from my iPhone

> On Aug 3, 2017, at 11:10 PM, Tim Harshbarger < <EMAIL REMOVED> > wrote:
>
> Well, I evidently was moving too fast for my own good.
>
> I wrote the code and tested it myself with Firefox and JAWS 18. I evidently forgot to test it with NVDA.
>
> So, when I just ran the test with NVDA 2017.2, the first time I clicked the test button the aria-live region updated but did not speak. The second time I clicked it, it did speak. I started the testing process over again 3 times and I ended up with the same result each time. The region was updated the first time but did not speak when I was using NVDA 2017.2. However, every time I clicked the button after the first time, it did speak.
>
> In my code, when the button is clicked:
> * I check for the existence of the live region.
> * If the region does not exist, I create the node, add the attributes, and append it to the body element.
> * if the region already exists, I skip to the next step.
> * I then update the innerHTML property of the live region.
>
> Appending the live region node and updating the contents of the live region node are separate steps. But could there be something amiss in the timing of appending the region and updating the region? I could try using a setInterval method to delay the updating of the content to see if that helps. However, it is only a guess on my part that some technique like that is being used on the original site. I would try that now, but evidently it is late and I need to rise early in the morning.
>
> Thanks,
> Tim
>
>