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

Motion animation best practices? #12

Open
JayPanoz opened this issue Jun 27, 2019 · 1 comment
Open

Motion animation best practices? #12

JayPanoz opened this issue Jun 27, 2019 · 1 comment

Comments

@JayPanoz
Copy link

Hi there.

First and foremost, thanks for this great resource! There’s no doubt it’s been useful for a lot of authors, and at least I can say it helped me tremendously when I was doing e-production.

This issue is more of a question/comment than a feature or bug request, but I believe it could be a good idea exposing such information in the knowledge base.

I may be wrong but there appears to be quite a huge gap between WCAG 2.0 and WCAG 2.1 when it comes to motion animation.

“Success Criterion 2.3.3 Animation from Interactions” has only been added @ 2.1 it seems, but it kinda creates a huge loophole in the sense reduced motion is all the rage right now, with all major browsers implementing this media feature.

As a disclaimer, I myself experienced vestibular disorders and can testify animations can hurt or even ruin entire days, so I wouldn’t be against promoting this “issue” so that authors designing interactive EPUBs with motion be aware this is something to take into account.

One example of a best practice would probably be this Mozilla demo, asking the user if they want to disable motion animations.

I haven’t found anything about that except for metadata, but in practice, putting a little bit of effort could make at least some books more accessible – instead of just tagging the publication with motion hazard, because they could still work super fine in static form with a switch at the beggining of the book for instance.

Motion animation is something Reading Systems are taking into account more frequently, given all the work being done there, so it’s kinda important there is some evangelisation in order for authors to know this actually is an issue.

A Reading System is only as good as the contents it must handle and render, so it will be useless to a person with vestibular disorders if the interactive fixed-layout has motion animation that will make the user sick.

@mattgarrish
Copy link
Contributor

Yes, dynamic content has been a bit problematic to tackle in the KB as it can take so many different forms at the implementation level. There are more general guidelines, like this, that we could do more to put forward to people, though.

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

2 participants