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

W3C specifications use a 2-column view, which is not universally accessible #287

Closed
MarjaE2 opened this issue Dec 17, 2021 · 12 comments · Fixed by #294
Closed

W3C specifications use a 2-column view, which is not universally accessible #287

MarjaE2 opened this issue Dec 17, 2021 · 12 comments · Fixed by #294

Comments

@MarjaE2
Copy link

MarjaE2 commented Dec 17, 2021

I visited https://drafts.csswg.org/web-animations-1/ because web animation poses way too many accessibility problems. And can make me very sick.

Following current web design tends, it has navigation in one column, and the body in another column, and has each scroll separately. This type of animation, one column scrolling without another, can trigger migraines in people with visual vertigo/visually-induced dizziness, such as some concussion survivors. So people who get sick from animation may not be able to raise accessibility concerns.

I visited https://drafts.csswg.org/web-animations-1/ but I assume other drafts are also affected.

@frivoal
Copy link
Contributor

frivoal commented Dec 17, 2021

@chrishtr @plehegar This issue seems relevant for many specs, not just of the CSSWG, but of all W3C. Should it be moved to https://github.com/w3c/tr-design/ ?

@svgeesus
Copy link

Should it be moved to https://github.com/w3c/tr-design/ ?

I think it should.

@svgeesus svgeesus transferred this issue from w3c/csswg-drafts Dec 17, 2021
@svgeesus svgeesus changed the title drafts.csswg.org uses 2-column view, which is not universally accessible W3C specifications use a 2-column view, which is not universally accessible Dec 17, 2021
@dontcallmedom
Copy link
Member

(not a solution to the issue which needs to be addressed in the style sheet, but as a temporary workaround, the second column disappear in narrow-enough windows)

@dontcallmedom
Copy link
Member

would it make sense to use the prefers-reduce-motion feature to switch to having the two columns scroll together?

@MarjaE2
Copy link
Author

MarjaE2 commented Dec 17, 2021

That makes sense to me.

For user-end workarounds, relying in page down instead of scrolling, or reducing frame rate to no more than 1 frame/second, can help. I find it helpful to push any boundary between scrolling and non-scroling elements close to the edge of the screen, and using a smaller window doesn't help with that.

@plehegar
Copy link
Member

Makes sense to me as well. @deniak , is that something you'll like to try or should I look in doing it?

@deniak
Copy link
Member

deniak commented Feb 2, 2022

Makes sense to me as well. @deniak , is that something you'll like to try or should I look in doing it?

I'll give it a try this week but what are the expectations regarding the scrolling? The TOC and the content of the spec have different heights so do you expect the scrolling rate to be the same for the 2 columns or proportional to the height of the sections?
I'm assuming it's the second option as the first one will not really solve the issue but it feels a bit weird to have different scrolling speeds on the same page as well.

@dontcallmedom
Copy link
Member

I think the first option ("scrolling rate the same for the 2 columns") solves the problem actually

@deniak
Copy link
Member

deniak commented Feb 2, 2022

Ok, I gave it a try and you can see the result here. Please comment on the PR if you have any remarks.

@MarjaE2
Copy link
Author

MarjaE2 commented Feb 2, 2022

Works great for me!

@MarjaE2
Copy link
Author

MarjaE2 commented Feb 2, 2022

.... Until the left column runs out.

@dontcallmedom
Copy link
Member

@MarjaE2 unfortunately https://cdn.statically.io/gh/w3c/tr-design/2-column-scroll/src/README.html no longer reflect the latest version of #293 which I think solves this; we'll ping you as soon as we have a proper rendition of that latest version

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

Successfully merging a pull request may close this issue.

6 participants