WebAIM - Web Accessibility In Mind

E-mail List Archives

Media player/recorder accessibility


From: Isabel Holdsworth
Date: Nov 15, 2018 1:11AM

Hi all,

I'm creating an all-purpose media player and audio capture component,
and I have a few quick questions:

Is it a good idea to use a single button for Play/Pause, or are
separate buttons preferable so long as the focus is managed? Is it
easier for users with cognitive issues or learning disabilities if
both buttons are always visible?

What's the best way to implement a volume control? I'm guessing a
vertical slider with ten stop points, but is there a better way?

If the user is playing and recording at the same time, would a tabbed
interface be the best way to provide access to the player and
recorder, or would it be better to present them in separate sections
with H1 or H2 headers? This approach could be clumsy for sighted
keyboard users, who would still have to tab their way through a bunch
of controls to get to the one they need.

Thanks as always, Isabel