1
votes

Putting a with an aria-hidden=”true”, NVDA will still read “Your browser does not support the video tag.” while the video is loading. Once the video is loaded, it will play. For some reason when using IE, NVDA will not ignore that text. It does not read it when using Chrome nor does VoiceOver read it. Has anybody run across this and no how to fix it?

here is the code:

<video id="view-video" controls>
    <source src="#" type="#">
    <span aria-hidden="true">Your browser does not support the video    tag.</span>
 </video>
2
Note that NVDA pairs best with Firefox. JAWS generally pairs best with IE (not Edge).aardrian
see this link for a number of tests with different browsers and tools: stevefaulkner.github.io/HTML5accessibility/tests/…Davemundo

2 Answers

0
votes

It would help if you provide more details of specific versions of IE and NVDA and whether you are using a keyboard or mouse. I am assuming mouse interaction because that's usually the culprit one in IE.

With that assumption, I don't think it's something you can really fix with just HTML or CSS https://github.com/nvaccess/nvda/issues/5320. NVDA in IE in mouse mode ends up reading a fair amount of unnecessary items. I assume this is what it relates to.

You can try display none, role=presentation, aria-hidden, position off screen, etc. and it will still seem to read it (whether it is inside or outside of the video tag).

So then it comes to why you are wanting this to be hidden. I figure this is not your real code, since you do have sources and they do load. So if the text is there just for older browsers, I would suggest not having the span at all initially. You might want to use modernizr, or do checks to see if the video tag is supported and then if it isn't add in the span. Or if you just want to account for older versions of IE you could put the content within conditional tags.

Unfortunately there doesn't look to be an easy answer from everything that I've found.

0
votes

Sorry, found the issue was a problem between IE 11 and Edge and NVDA 2016. The bug has been reported.