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 screenreader UX for audio player placeholder #9037

Open
1 task
gavinspence opened this issue Apr 8, 2021 · 0 comments
Open
1 task

Improve screenreader UX for audio player placeholder #9037

gavinspence opened this issue Apr 8, 2021 · 0 comments
Labels
blocked This issue should not be worked on until another internal issue is completed - see desc for details Refinement Needed This is ready for refinement. It shouldn't be worked on until it has been refined by Dev & Test.

Comments

@gavinspence
Copy link

gavinspence commented Apr 8, 2021

Is your feature request related to a problem? Please describe.
We've recently introduced a loading indicator placeholder in place of the audio player on our radio and podcast pages. This is to better inform those on slower devices and connections that a media player is loading instead of just showing a white space.

We've broken out some of the accessibility requirements as we require translations in order to complete them.

Describe the solution you'd like
For services that have audio pages, ensure the screenreader UX is correct and we read out 'audio player loading'.

Given I use a screen reader
And I am viewing a page with the audio player
When the audio player loading indicator is displayed
And I navigate to this element
Then this content is announced as “Audio player loading” (translated)
And no HTML semantics are announced (as it’s a strong element which doesn’t convey semantics)
And is announced in the content order in the same position as the audio player would be

Given I use a screen reader
And I am viewing a page with the audio player
When the audio player loading is complete
Then I should not be able to navigate to content announced as “Audio player loading” (translated)

Translations have been requested on #wstranslations for the following services:

  • afaanoromoo
  • afrique
  • amharic
  • arabic
  • bengali
  • burmese
  • gahuza
  • hausa
  • hindi
  • indonesia
  • korean
  • kyrgyz
  • marathi
  • nepali
  • pashto
  • persian
  • portuguese
  • russian
  • somali
  • swahili
  • tamil
  • tigrinya
  • urdu
  • uzbek
  • zhongwen/simp
  • zhongwen/trad

Describe alternatives you've considered
NA

Testing notes
[Tester to complete]

Dev insight: Will Cypress tests be required or are unit tests sufficient? Will there be any potential regression? etc

  • This feature is expected to need manual testing.

Additional context
Add any other context or screenshots about the feature request here.

@gavinspence gavinspence added blocked This issue should not be worked on until another internal issue is completed - see desc for details Refinement Needed This is ready for refinement. It shouldn't be worked on until it has been refined by Dev & Test. labels Apr 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocked This issue should not be worked on until another internal issue is completed - see desc for details Refinement Needed This is ready for refinement. It shouldn't be worked on until it has been refined by Dev & Test.
Projects
None yet
Development

No branches or pull requests

1 participant