Forum Discussion
iFrame video becoming a keyboard trap
I think the major problem here is with YouTube.
I'm starting to wonder whether it is worth embedding YT videos as I don't think YT appear to be interested in making their embedded player accessible. It's a horrible experience. When testing embedded YT videos, I don't bother testing the embed and open directly on the YT site now, which is what I suspect YTs goal is and why the embedded YT video experience appears to be getting better.
I know this isn't always possible, but the Vimeo embed or importing the video directly is a much more accessible experience.
The last few courses I have accessibility tested with YT video have been horrible. Full of unwanted extra bits and pieces all over the interface, difficult to know where you are in the video (terrible focus visibility) and keyboard trap.
Heres a fairly recent article discussing the known issues: https://accessible.org/youtube-video-player-accessibility/?utm_source=chatgpt.com
Thoughts
I wonder if Articulate could use the YT API instead and not the embed, and use their own player for YT video. This would also give access to video events such as media completes, to enable the next block.
Related Content
- 1 year ago