[css-animations-2] Add non-normative accessibility considerations for animations #13243
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
vmpstr
reviewed
Dec 18, 2025
Comment on lines
+1485
to
+1486
| This specification provides declarative mechanisms for animations | ||
| that previously needed to be done using script. |
Member
There was a problem hiding this comment.
This is a bit revealing of the spec history. It could also be that WAAPI came after css animations, but it doesn't change the content of the section. Not sure if there's some more neutral wording. This is also ok as is
Contributor
Author
There was a problem hiding this comment.
WAAPI did come well after CSS animations, the "script" in this context is raf / setinterval loops. I think it's fine to get this section started.
Co-authored-by: vmpstr <[email protected]>
Co-authored-by: vmpstr <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
These are similar to the accessibility considerations when using transitions: https://www.w3.org/TR/css-transitions-1/#accessibility