Skip to content
Open
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
66 changes: 60 additions & 6 deletions css-animations-2/Overview.bs
Original file line number Diff line number Diff line change
Expand Up @@ -1448,15 +1448,69 @@ console.log(anim.playState); // Should be 'running'.

</div>

<h2 id="priv">
Privacy Considerations</h2>
<h2 id="privacy">
Privacy Considerations</h2>

No privacy concerns have been reported on this specification.
<em>This section is not normative.</em>

<h2 id="sec">
Security Considerations</h2>
As for security, the privacy considerations of this specification are limited
because it does not allow Web content to do things that it could not do before.

No security concerns have been reported on this specification.
This specification may provide additional mechanisms that help to determine
characteristics of the user's hardware or software.
However, ability to determine performance characteristics of the user's
hardware or software is common to many Web technologies,
and this specification does not introduce new capabilities.

As described in [[#accessibility]],
implementations may provide mitigations to help users with disabilities.
These mitigations are likely to be detectable by Web content,
which means that users who would benefit from these mitigations
may face a tradeoff between keeping their disability private from
the Web content or benefiting from the mitigation.

<h2 id="sec">
Security Considerations</h2>

No security concerns have been reported on this specification.

<h2 id="accessibility">
Accessibility Considerations</h2>

<em>This section is not normative.</em>

<h3 id="accessibility-motion">
Motion</h3>

This specification provides declarative mechanisms for animations
that previously needed to be done using script.
Comment on lines +1485 to +1486
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Copy link
Contributor Author

@flackr flackr Dec 18, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Providing a declarative mechanism has multiple effects:
it makes such animations easier to make and thus likely to be more common,
but it also makes it easier for user agents to modify those animations
if such modifications are needed to meet a user's accessibility needs.

Authors are strongly encouraged to use the '@media/prefers-reduced-motion' media query to provide alternative
reduced motion or instant animations when the user has indicated a preference to ''@media/prefers-reduced-motion/reduce'' motion.

Users who are sensitive to movement,
or who require additional time to read or understand content,
may benefit from user agent features that allow
animations to be disabled or slowed down.
(But see [[#privacy]] for information on the privacy implications
of such mitigations.)

User agent implementors should be aware that Web content
may depend on the firing of <a href="#events">animation events</a>,
so implementations of such mitigations may wish to fire animation events
even if the animations were not run as continuous animations.
However, it is probably poor practice for Web content to depend on
such events to function correctly.

<h3 id="accessibility-cascade">
Cascade</h3>

The cascade also allows users to disable animations entirely
by overriding the animation properties.

<h2 id="changes">Changes</h2>

Expand Down