Speed controls for pre-recorded audio and video

[manchuck]

I would like to start a discussion on adding a new success criterion for speed controls in pre-recorded audio and video. Having the ability to speed up and slow down can help those with cognitive impairments digest the information being presented. For example, when I watch something on YouTube, I'll use 2x speed to get past the crux of what I'm looking for. It helps me focus on the content. This SC would apply to audio and video that is used to relay information (training videos, ads, etc).

[patrickhlauke]

Reposting my comment from w3c/wcag#4455 (comment)

Admittedly, I think this might be unrealistic if aimed at all instances of audio and video. Sites don't just provide "content" audio/video ... it may be background videos used for decoration, sound effects, background music, etc. Video may not just be a video file per se, but another type of animation (CSS, SVG, etc) where it may not be as straightforward to implement speed controls either.

[ewightman]

Could it be limited to media which contain speech?

[manchuck]

I added: "This SC would apply to audio and video that is used to relay information (training videos, ads, etc)."

[ewightman]

I don't think 'speech' or 'relay information' is the right restriction, but I'm not sure what is yet. Some cases to think about (and my thoughts on whether speed control should be required for them):

• Video of a signed language (Probably. Would need to talk to people who are Deaf and neurodivergent. I'd find it helpful to slow down signed content as an intermediate signer, but I'm not the target audience.)
• Audio of a song with words (Probably not. Lyrics may be information, but adjusting the delivery speed for music is uncommon enough that Spotify has a speed control for podcasts but not music.)
• A video with informative text, but no spoken audio (Probably, but it might not need to be specified here because of overlap with other criteria.)

[manchuck]

You're right @ewightman not quite there yet. I started this conversation in the A11y slack channel and I would like to post some of the comments made there by those not on GitHub:

I'm not on github so wanted to add my experience to this here.
I think it's a good idea. When speed control is not available (which is not very often) I struggle. As my mind might even start to wander during longer YouTube shorts splitting content into shorter segments to go back would not be an ideal solution for me. I would just not process the information multiple times 😅

There was then a mention about the COGA design pattern for chunked media

And then this comment:

I don't think that COGA pattern is the same or necessarily even relevant here. That said, I think adding playback speed controls is a huge boon to accessibility - the way my ADHD brain works, for example, means that I can't focus on video of someone just talking at "normal" (interminally slow) speed. Speeding it up helps it "hook into" my brain.

[manchuck]

I had an HR training video where the setting was a game show, followed by a TLC style interview ("Real Housewives") . The interview portion had all the information I needed in order to take the test. Some of the information referenced the game show. The video did not allow me to search around (even after completing the video). All that made it more difficult and frustrating to complete the module.

[mraccess77]

For COGA the ability to go back and re-listen/review several times is likely an important need in addition to speed. I wonder what level of controls should be required then - go back 10 seconds? And in what situations should these be required or not.

[patrickhlauke]

so probably taking a step back, we're looking at more of a requirement that for meaningful/content audio/video (which may also include things like SVG-based animations and similar, not just limited to audio or video files) users must have not only play/pause controls, but also controls to control playback position (either with a full-on progress/scrub bar, or at least a 10 sec back/foward style set of controls), playback speed, easy replay options

[manchuck]

Yeah, that sounds like what we are looking for. There was also some chatter about breaking the content up using chapters. I would say that it is better to have a different SG instead of this one.