Skip to content

Relation to prefers-reduced-motion #41

@plannero

Description

@plannero

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions