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

I've put together an updated explainer with a possible proposal at:
https://github.com/flackr/reduce-motion

After having given this some thought, I'm wondering if we could re-use the existing media query support and automatically annotate animations declared within a reduce motion media query to be supporting of reduced motion. This would reduce the syntactic overhead for authors not having to think about a new property. We would of course still need such a property in the web animations API but it could be a hidden internal value in CSS for both transitions and animations.

I still think that when we forcibly reduce motion we probably want to do so by disabling smooth interpolation rather than completely removing animations, as their animated values may be critical to the usability of the page.

-- 
GitHub Notification of comment by flackr
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7440#issuecomment-1645701025 using your GitHub account


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

Received on Friday, 21 July 2023 14:41:07 UTC