Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve support for HTML5 Player #4046

Closed
nvaccessAuto opened this issue Apr 3, 2014 · 5 comments
Closed

Improve support for HTML5 Player #4046

nvaccessAuto opened this issue Apr 3, 2014 · 5 comments

Comments

@nvaccessAuto
Copy link

Reported by netblue on 2014-04-03 09:33
Hi, when using the HTML5 player on websites NVDA identifies sum clickable elements as just clickable without description or identification of the element. Also volume controls cannot be accessed with NVDA but they can with Jaws.

@nvaccessAuto
Copy link
Author

Comment 1 by ateu on 2014-04-03 09:39
I think you are using Google Chrome or a derivatire. When using Firefox, the changes in the volume are announced, which means likely a chrome issue.

@nvaccessAuto
Copy link
Author

Comment 2 by blindbhavya on 2014-10-04 12:20
Hi,
Can you give some examples of websites with the HTML 5 Player?
Also, as ateu said, could you test if the issue persists with Firefox as well?

@nvaccessAuto
Copy link
Author

Comment 3 by blindbhavya (in reply to comment 1) on 2014-10-04 12:22
Replying to ateu:

I think you are using Google Chrome or a derivatire. When using Firefox, the changes in the volume are announced, which means likely a chrome issue.

Even if the reporter is using Google Chrome, he has said that JAWS handles this correctly while NVDA doesn't.
Therefore, this issue can be fixed in NVDA.

@bhavyashah
Copy link

This ticket contains no specifics - no STR, no test case, and no means to contact the original reporter. Please consider closing as Invalid. @jcsteh @feerrenrut @LeonarddeR

@feerrenrut
Copy link
Contributor

Happy to reopen this issue if we can get some more specific information:

  • Example website or more ideally a minimal test case.
  • The actions required to trigger the problematic behaviour, or in other words "the steps to reproduce".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants