[csswg-drafts] No-motion / forced-reduced-motion issue draft (#7440)

stubbornella has just created a new issue for https://github.com/w3c/csswg-drafts:

== No-motion / forced-reduced-motion issue draft ==
The [TAG review of scroll linked animations](https://github.com/w3c/csswg-drafts/issues/5321) identified an existing issue that without explicit developer support, animations with motion on the web do not respect a user's desire to reduce motion. [We explored many options for reducing motion but found that it was not possible](https://github.com/w3c/csswg-drafts/issues/5321) to automatically reduce motion without sometimes making content invisible. We still feel it is worthwhile exploring whether we can forcibly reduce or remove motion with a new user setting. From our [demo](https://flackr.github.io/reduce-motion/demos/phone/) we came up with at least two feasible options to force motion reduction, though we are open to exploring others:

- Not running animations.
- Stepping between key points of animation.

We propose adding a new setting for users to elect to forcibly reduce motion, possibly breaking content in the same way that other existing settings such as disabling images or Javascript does and exposing a media query value for when this setting is on so that developers can provide a fallback variant.


Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7440 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Thursday, 30 June 2022 17:59:03 UTC