Re: Flash index problem.

Hi Wayne,

Ah, math <smile>. This presumes that the end-user has configured their TTS
engine to read at this speed - but since all screen readers I've seen also
allow the end-user the ability to adjust the reading rate, this by
extension means they can also adjust "flashing" in the use-case context you
provided. (And if the user-agent stack doesn't, this is a failure of UAAG,
which is non-normative, sadly.)

Additionally, this will manifest on *any* content rendered in the
user-agent - this cannot be mitigated by the individual content
author/owner - it is a concern rooted at the user-agent level.

One has to presume that a user who both requires
text-to-speech+highlighting AND is also sensitive to flashing content will
have previously adjusted their user-agent stack to address this issue.

JF

On Tue, Aug 24, 2021 at 6:57 PM Wayne Dick <wayneedick@gmail.com> wrote:

> If you are reading with a text-to-speech reader and it highlights words at
> more than 180 words per minute, then you have more than 3 flashes per
> second.
>
>

-- 
*John Foliot* |
Senior Industry Specialist, Digital Accessibility |
W3C Accessibility Standards Contributor |

"I made this so long because I did not have time to make it shorter." -
Pascal "links go places, buttons do things"