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

Provide styles to remove/obscure images #43

Open
JayPanoz opened this issue Apr 30, 2018 · 2 comments
Open

Provide styles to remove/obscure images #43

JayPanoz opened this issue Apr 30, 2018 · 2 comments
Labels
a11y Accessibility-related issues and feature requests feedback required
Milestone

Comments

@JayPanoz
Copy link
Collaborator

This is part of the a11y baseline, as defined in issue #18

It seems removing/obscuring images can help with dyslexia. I’ll need confirmation there.

If so, what would be the best option? Removing images entirely? Replacing them with a placeholder? Obscuring them? What about figcaptions?

@JayPanoz JayPanoz added feedback required a11y Accessibility-related issues and feature requests labels Apr 30, 2018
@JayPanoz JayPanoz added this to the beta release milestone Apr 30, 2018
@llemeurfr
Copy link
Contributor

What I understood from Mobidys experts is that text + image side by side are the issue.
Meaning that a way to display some placeholder instead of images by default and make them appear at will could be good.
This is 100% open to discussion.

@JayPanoz
Copy link
Collaborator Author

Hmm which means issue #42 and this one could be interlaced, at least when it comes to images.

Placeholder can definitely be implemented using CSS, displaying at will can be a lot of implementations, all of which being not necessarily doable with CSS:

  • display all images when disabling the feature – doable with CSS;
  • display the image the user clicks/taps – not doable with CSS unless we abuse ::selection so that would be a double-click or long tap;
  • display the image the user clicks/taps in a modal – not doable with CSS as it creates too many accessibility issues + we need to know scrollLeft or whatever is used to progress in the paginated view.

One major benefit of this solution over unfloating is that we wouldn’t mess up with icons (e.g. aside with a notepad icon).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
a11y Accessibility-related issues and feature requests feedback required
Projects
None yet
Development

No branches or pull requests

2 participants