WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: fade-in text abd auto-navigation to next slide

for

From: glen walker
Date: Oct 29, 2021 4:26PM

I try not to limit what the designers want to do and work with them to make
their concept accessible. Personally, I'd rather see all the text rather
than having it fade in. The timing of the fade might be too slow for my
taste, or if it's too fast it could be distracting from me reading the
content. But if that's what they want to do, we can try to make it
accessible.

*Not* being able to read the text with assistive tech while the text is
visible (albeit partially faded) could be a 1.3.1 or 1.3.2 issue. Take
your pick. As long as it's an accessibility issue, it doesn't really
matter which one you use.

As far as the speed of the fade-in, that could be 2.2.1 or 2.2.2. If the
fading lasts longer than 5 seconds, then it's a 2.2.2 issue, sort of.
2.2.2 specifically points out "Moving, blinking, scrolling" content.
Content that fades in isn't really moving, blinking, or scrolling so
someone might nitpick that 2.2.2 doesn't apply. But 2.2.1 could equally
apply. 2.2.1 talks about a "time limit" and has a note that says "This
success criterion helps ensure that users can complete tasks without
unexpected changes in content or context that are a result of a time
limit." Again, someone might argue that text fading in isn't a "change of
content" but that would be a stretch argument. I think it applies.

You could even go so far as to say 1.4.3 applies because before the text is
fully faded in, it probably has insufficient contrast.

The higher view here is to make it as accessible as possible to everyone
and to not nit pick which success criterion (or criteria) it fails. I think
you have plenty of failures to choose from.

All the issues could be avoided if you had a simple "allow text fading" or
"allow animations" option.