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

audio player accessibility #3382

Open
tmakarios opened this issue Apr 16, 2024 · 3 comments
Open

audio player accessibility #3382

tmakarios opened this issue Apr 16, 2024 · 3 comments
Labels
Feature UI User interface

Comments

@tmakarios
Copy link

Describe the bug
Screen reader users can't play audio.

To Reproduce
Steps to reproduce the behavior:

  1. Use a screen reader and keyboard to go to the play button on an audio file in a chat, such as at https://freespoken.nz/bible-radio/
  2. Press Enter
  3. Discover that the play button is unavailable.

Expected behavior
The audio file should play.

Environment (please complete the following information):

  • Desktop or Mobile? Windows 11 with NVDA, or JAWS
  • Browser [e.g. Chrome, Firefox] Not sure
  • Converse.js version [e.g. 4.2.0] 10.1.7, I think

Additional context
You can see the comments of the person who actually tested it in the replies to this toot https://theres.life/@TMakarios/112278231413032952

@unwaivering
Copy link

unwaivering commented Apr 16, 2024

I'm actually one of the screen reader users who did the testing. I can confirm that this is the problem I'm having when using the web interface.

@unwaivering
Copy link

I've tried this in Firefox, and I was able to read the audio player controls. I've tried using the carrot browsing in NVDA, and it made the navigation much better. However while using the carrot browsing, it did not play. It did play without it. Perhaps you may want to test conversant JS to see if it complies with WCAG standards. you could do so by going here.
https://webaim.org/resources/evalquickref/

@jcbrand
Copy link
Member

jcbrand commented May 10, 2024

Converse doesn't do anything fancy with audio/video, it uses the built-in HTML audio and video elements.

The issue seems to be that browsers don't support accessibility features for these built-in elements. 🙄

This article has more info:
https://developer.mozilla.org/en-US/docs/Learn/Accessibility/Multimedia

Looks like the workaround is to create a custom interface.

@Echolon Echolon added Feature UI User interface labels Jun 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature UI User interface
Projects
None yet
Development

No branches or pull requests

4 participants