Opened 3 years ago

Last modified 3 years ago

#5485 accepted defect

Audio player controls not announced to Orca screenreader

Reported by: André Jaenisch Owned by:
Priority: major Milestone:
Component: graphic design/interface Keywords: Audio, JavaScript, Accessibility
Cc: Michael Taboada Parent Tickets:

Description

As reported on the Orca Mailing List: https://mail.gnome.org/archives/orca-list/2016-October/msg00113.html

there is at least one instance with an inaccessible video player control:
http://vidstorm.tk/u/storm_dragon/m/the-insane-song/

Looking into the Markup it looks like audio.js is the problematic bit:
http://git.savannah.gnu.org/cgit/mediagoblin.git/tree/mediagoblin/static/js/audio.js

The user reported it in https://mail.gnome.org/archives/orca-list/2016-October/msg00120.html as

"There are no controls, no play, stop, pause, anything other than the slider, which itself is unlabeled."

A good entry point was suggested in https://mail.gnome.org/archives/orca-list/2016-October/msg00121.html

What led to the decision of using/writing this audio.js?
Where there alternatives to be considered?

Subtickets

Change History (4)

comment:1 Changed 3 years ago by André Jaenisch

Summary: Video player controls not announced to Orca screenreaderAudio player controls not announced to Orca screenreader

As reported on the Orca Mailing List: ​https://mail.gnome.org/archives/orca-list/2016-October/msg00113.html

there is at least one instance with an inaccessible audio player control:
http://vidstorm.tk/u/storm_dragon/m/the-insane-song/

Looking into the Markup it looks like audio.js is the problematic bit:
http://git.savannah.gnu.org/cgit/mediagoblin.git/tree/mediagoblin/static/js/audio.js

The user reported it in ​https://mail.gnome.org/archives/orca-list/2016-October/msg00120.html as

"There are no controls, no play, stop, pause, anything other than the slider, which itself is unlabeled."

A good entry point was suggested in ​https://mail.gnome.org/archives/orca-list/2016-October/msg00121.html

What led to the decision of using/writing this audio.js?
Where there alternatives to be considered?

comment:2 Changed 3 years ago by André Jaenisch

Thanks, ayleph, for pointing out, that this issue described here is with the audio player.

comment:3 Changed 3 years ago by Ben Sturmfels

Component: programminggraphic design/interface
Status: newaccepted

Thanks Ryuno-Ki, this is very valuable feedback, as accessibility is a high priority for MediaGoblin.

I'll note that this ticket is closely related to #5483 about the JAWS screen reader, opened a couple of days ago by lilmike (one of the administrators of the vidstorm.tk MediaGoblin instance you mentioned).

comment:4 Changed 3 years ago by Ben Sturmfels

Cc: Michael Taboada added
Note: See TracTickets for help on using tickets.