Many sites inflict their own smooth scrolling, regardless of prefers-reduced-motion, and regardless of browser settings to disable smooth scrolling, disable animation, disable autoplay, etc.
And the old criterion is
only applicable at aaa-- not hurting users should apply regardless, even if higher standards apply at aaa.
allows "essential" smooth animation. Although there are cases where it's genuinely essential, I worry that this will be interpreted to mean any essential move or transition can be made into a smooth one.
allows any smooth animation, as long as there's some way to disable it, but doesn't require discoverability of site-specific means, or adherence to prefers-reduced-motion.
I think criteria about avoiding harm, such as "Harm from Motion," and "Prevent Harm," should have basic standards at lower levels, even if they have stricter standards at aaa.
A related point is that many sites, including github, use javascript for animations, including the sticky headers here. So it's even harder for users to protect ourselves from these elements.
I'm going to use the old criterion 2.3.3 as an example.
https://www.w3.org/WAI/WCAG21/Understanding/animation-from-interactions.html#dfn-motion-animation
Many sites inflict their own smooth scrolling, regardless of prefers-reduced-motion, and regardless of browser settings to disable smooth scrolling, disable animation, disable autoplay, etc.
And the old criterion is
I think criteria about avoiding harm, such as "Harm from Motion," and "Prevent Harm," should have basic standards at lower levels, even if they have stricter standards at aaa.