Smooth Scrolling and Autoscroll can be migraine triggers
Categories
(Core :: Layout: Scrolling and Overflow, defect, P1)
Tracking
()
Accessibility Severity | s2 |
People
(Reporter: erwinm, Assigned: emilio)
References
Details
(Keywords: access)
Attachments
(1 obsolete file)
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:56.0) Gecko/20100101 Firefox/56.0 Waterfox/56.2.14
Steps to reproduce:
Firefox's default settings include smooth scrolling and autoscroll. Both of these can be migraine triggers. Many pages also insist on smooth scrolling and/or autoscroll regardless of user settings.
Defaults of new profiles:
Pages:
Proposals to use system prefs:
Miscellaneous:
Assignee | ||
Updated•6 years ago
|
Assignee | ||
Comment 2•6 years ago
|
||
Does setting general.smoothScroll
to false
fix the use cases here?
Fixing the site's smooth scrolling animations implemented via JS is probably not possible, but for the ones using native smooth scrolling that should work.
Assignee | ||
Comment 3•6 years ago
|
||
What I planned to do was to gate smooth scrolling on having prefersReducedMotion
evaluating to false
, but it seems we do have a switch for that already. It's probably still worth it though.
"Does setting general.smoothScroll to false fix the use cases here?"
It's a catch-22 when setting Firefox up. (Since smooth scrolling and the other animations make it hard to get through the intro screens and turn off smooth scrolling and the other animations.) It's not dealing with enough of the website animation afterwards.
If the assumption is correct that instant rather than smooth scrolling is better for all users with motion sensitivity (is that the case?), then it seems like disabling smooth scrolling when system-wide accessibility settings request reduced motion (which should match the (prefers-reduced-motion)
media query, and appears at a quick glance to be implemented on all platforms) seems like a good idea. We should double-check that that disabling includes cases where pages use the ScrollBehavior
in ScrollOptions
to request smooth
scrolling.
Assignee | ||
Comment 6•6 years ago
|
||
Yeah, I guess I should do that, even if we can't do anything about website animations using jQuery and such...
Assignee | ||
Updated•6 years ago
|
Assignee | ||
Comment 7•6 years ago
|
||
We could put this change itself behind a pref too, if we considered that worth
it. But probably not so.
Comment 8•6 years ago
|
||
Anything else in the way of landing this? I don't think we need a pref.
Assignee | ||
Comment 9•6 years ago
|
||
Yeah, see the review, need to check that this also does the right thing for programmatic auto-scrolling.
Comment 10•6 years ago
|
||
Comment 11•6 years ago
|
||
Backed out changeset 77357e0aa88e (bug 1584859) for wpt and mochitest failures.
Failure log for wpt (position-sticky-root-scroller-with-scroll-behavior.html): https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=271050336&repo=autoland&lineNumber=2933
Failure log for mochitest (test_frame_reconstruction.html): https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=271048336&repo=autoland&lineNumber=3478
Backout: https://hg.mozilla.org/integration/autoland/rev/947c37a2523c809c99ba37e4e3db6cd3fd5fa609
Comment 12•6 years ago
|
||
There are also xpcshell failures:
https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=271054665&repo=autoland&lineNumber=1439
Comment 13•6 years ago
|
||
There's a r+ patch which didn't land and no activity in this bug for 2 weeks.
:emilio, could you have a look please?
For more information, please visit auto_nag documentation.
Assignee | ||
Updated•6 years ago
|
Comment 15•5 years ago
|
||
Access-s2 because triggering migraines is pretty severe for users that experience this. That said, WCAG classifies this as a level AAA criterion, which suggests it is considered less severe by WCAG.
Reporter | ||
Comment 16•4 years ago
|
||
Bugs which would help disable this:
bug 1743045 would keep Javascript from overriding users' settings.
bug 1753565 would check prefers-reduced-motion.
Updated•3 years ago
|
Comment 18•3 years ago
|
||
The severity field for this bug is set to S3. However, the accessibility severity is higher, [access-s2].
:emilio, could you consider increasing the severity?
For more information, please visit auto_nag documentation.
Assignee | ||
Updated•3 years ago
|
Comment 19•2 years ago
|
||
Should we consider this as fixed by bug 1753565?
Updated•2 years ago
|
Assignee | ||
Updated•2 years ago
|
Updated•2 years ago
|
Description
•