WebAIM - Web Accessibility In Mind

E-mail List Archives

Where text exists but cannot be read by screenreader - which checkpoint?

for

From: Kevin Prince
Date: Nov 9, 2023 3:42PM

On the basis that no question is stupid if you don't know the answer, and I've been overthinking this one:

Text exists, it's real text so 1.1.1 doesn't apply, but the screenreader just doesn't read it. One current example is when there's only a single entry in a filtered dropdown. If there are two then I can read. (Not 1.1.1 then), a keyboard user can operate the control so not 2.1.1

I've also seen it where content is in a <div> and just doesn't appear in the reading order. A keyboard user (visual) can see it so again not 2.1 and it's real text so not 1.1.1

Thoughts from the brains trust? (My first example is clearly a bug: but it's only a bug for screenreader users so it ought to have a relevant checkpoint)

Kevin Prince
Product Accessibility & Usability Consultant