Comment 1 by vivek-panday on 2014-12-03 15:39
Changes:
Changed title from "NVDA reader Video tag Twice" to "NVDA screen reader reading Video tag Twice"

Comment 2 by vivek-panday on 2014-12-03 15:41
adding code :

Comment 5 by jteh on 2014-12-04 00:18
Please provide exact steps to reproduce. For example, when are you expecting this to be read? If i tab around in Firefox in NVDA focus mode, it reads the label, but Chrome does as well. We don't render the label in browse mode in either case.

Comment 6 by vivek-panday on 2014-12-04 03:41
Step to reproduce :
add below code in your html 5 file

<video autoplay controls tabindex="0" aria-label="This is a video Testing">
<source src="big_buck_bunny.webm" type="video/webm" />
Your browser does not support the video tag
</video>

drag your mouse on Video area (video area is focused by mouse) -NVDA screen reader only reading "video video" although we are providing aria-label.

Please suggest.

Comment 7 by vivek-panday on 2014-12-05 09:07
Hi All ,
Any suggest on above given behaviour of NVDA.

Comment 8 by jteh on 2014-12-06 03:06
Note that moving the mouse isn't how most screen reader users will interact with the page. Most will use the keyboard.

The issue is that the mouse is landing on the controls toolbar (not the container around it). Chrome exposes the aria-label on the container, not the toolbar. On the toolbar, it just exposes the name "video". (It also exposes the description as "video", which is redundant.)

Mouse tracking isn't intended to read containers, only the item directly beneath the mouse cursor. I guess you could consider asking Chrome to expose the name of the video on the controls toolbar. However, they may argue they're already exposing it on the container and therefore that this isn't necessary.

Closing this as wontfix, as @jcsteh pointed out:

Moving the mouse isn't how most screen reader users will interact with the page.

Someone is still welcome to file a Chrome issue for this if they would like.