Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Serhiy Zakharchenko

    (@zahardoc)

    Hi @adrianb,

    Thank you for bringing this to our attention. Yes, we’d be happy to improve the player’s accessibility. Do you have any specific attributes in mind?

    Thread Starter AdrianB

    (@adrianb)

    During a accessibility review we got this comment about the player:

    This element has no name and no role that is available in code.

    I’m no expert on a11y but from what I’ve read the role could either be “group” or, if the player is more advance, “application”. And some aria label to describe the player. When I asked my friend ChatGPT about it, it suggested more labels on controls like this:

    <div role="group" aria-label="Audio Player">
    <button aria-label="Play">▶</button>
    <button aria-label="Pause">⏸</button>
    <button aria-label="Stop">⏹</button>
    </div>

    Also, better keyboard navigation of the controls. At least in our use it does not work.

    Plugin Author Serhiy Zakharchenko

    (@zahardoc)

    Thanks @adrianb,
    I’ll update you when this is done.

    Plugin Support keleigh824

    (@keleigh824)

    Hi @adrianb,

    Version 3.9 of SSP contains improved player accessibility and keyboard controls.

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Accessibility for HTML5 player’ is closed to new replies.