Embeddable player fails Accessibility Insights Audit
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 254
- Forks
- 53
- PR merge metrics
- No merged PRs in 30d
Description
I hope this is the correct place to post this bug report, with no other obvious repository for it, and as the embedded player makes use of api.soundcloud.com, I thought perhaps it might be. If it's not, please advise and I will happily post elsewhere.
Title: Embeddable player fails Accessibility Insights Audit
Issue found of: May 24th 2022
Endpoint(s):
- An iframe loading a given embedded player, e.g:
https://w.soundcloud.com/player/?url=https%3A//api.soundcloud.com/tracks/982691227&color=%23ff5500&auto_play=false&hide_related=false&show_comments=true&show_user=true&show_reposts=false&show_teaser=true
Scope(s):
- None
Steps to reproduce:
- Get the embedded player markup for a given Soundcloud track
- Embed it in a webpage and test using Accessibility Insights (Chrome extension)
Expected behaviour:
- In order to ensure accessibility compliance there should not be any accessibility errors reported. Accessibility Insights' Fast Pass feature is a useful tool for accessing compliance.
Actual behaviour:
- There are multiple accessibility issues, including some simple changes to markup that would be easily to implement. You can see an example of the report generated here.
I hope this is report helpful. 🙌
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by loading the example embedded player endpoint and reviewing the linked Accessibility Insights report. Run the Accessibility Insights Fast Pass audit against the player and identify the reported failures and where its markup is generated. Done means the reported accessibility errors are addressed and the audit no longer reports them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- accessibility, frontend, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100