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

Relation to prefers-reduced-motion #41

Open
plannero opened this issue Feb 15, 2023 · 2 comments
Open

Relation to prefers-reduced-motion #41

plannero opened this issue Feb 15, 2023 · 2 comments

Comments

@plannero
Copy link

plannero commented Feb 15, 2023

From an accessibility perspective, preventing autoplay in a simple way is very attractive!

However, there's already a user agent setting called prefers-reduced-motion that is readable as a css variable and accessible via javascript. In the accessibility community, many of us are trying to encourage developers of media player widgets to look at that variable and - if it is set to "reduce" - refrain from autoplaying any kind of video, audio, animation or similar.

I can come up with a few use cases where users may want to limit autoplay but NOT animations. Eg. users who have limited bandwidth or a very expensive connection, but who need the cognitive hints that animations can provide.
But I guess most users who have activated prefers-reduced-motion also do not want autoplay.

The prefers-reduced-motion preference, so far, is not universally recognized. Perhaps the proposed autoplay setting will spread quicker? If so, that would be great for accessibility (and reduce the need for prefers-reduced-motion).

What do you think? Perhaps I am missing some important differences between the two approaches?

A somewhat more detailed dialogue about this can be found in a recent thread in the W3C Community Slack, in the channel called #nordic-accessibility-group-feedback-standards-legislation

@gkatsev
Copy link

gkatsev commented Feb 15, 2023

This spec is more about knowing whether a media element could autoplay, as opposed to allowing or disallowing autoplay.

Maybe it's worth opening an issue against HTML for this, if one doesn't already exist? To amend it to say that if the autoplay attribute is set but prefers-reduced-motion is set to reduced, user agents can ignore the autoplay attribute or something along those lines.

@plannero
Copy link
Author

Thanks @gkatsev for the clarification!
I re-read the autoplay policy spec now and got a better understanding of it.

Not sure exactly how these two user settings should relate. Here are two example combinations:
If user settings indicate that autoplay is ON (audio + video), but also that the user prefers-reduced-motion, I guess autoplaying audio is fine but more hesitant about autoplaying video.
If user settings indicate that autoplay is OFF, but prefers-reduced-motion has no value, would it still be ok to let gif animations autoplay? Not obvious to me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants