Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not hurting users should be standard, not aaa #27

Open
MarjaE2 opened this issue Oct 1, 2023 · 1 comment
Open

Not hurting users should be standard, not aaa #27

MarjaE2 opened this issue Oct 1, 2023 · 1 comment

Comments

@MarjaE2
Copy link

MarjaE2 commented Oct 1, 2023

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

  1. only applicable at aaa-- not hurting users should apply regardless, even if higher standards apply at aaa.
  2. 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.
  3. 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.

@MarjaE2
Copy link
Author

MarjaE2 commented Oct 25, 2023

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant