You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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).
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?
The text was updated successfully, but these errors were encountered: