WebAIM - Web Accessibility In Mind

E-mail List Archives

Embarrassing question - text isn't read but it's neither a control nor is it non-text content

for

From: Kevin Prince
Date: Jan 26, 2023 8:40PM

I've had the scenario a couple of times recently on Mobile Apps, often on only one platform where a section of text is not read or even found by the usual swiping/exploring motions. As the other platform reads it I can't call it out under 1.1.1 and it's not really 2.1.1 cos it's not a control that I can't reach. Clearly it entirely breaches the spirit of Principle 1 - Perceivable but not the detail of any obvious checkpoint. Is this a hole in WCAG? Or is my brain so frazzled by the joy or having just helped t run Deafblind New Zealand's second bi-annual conference that I can't see the wood for the trees.

Summary.

Paragraph of normal text following a heading.
It's read by Voiceover but Talkback only finds the heading
It's real text - VO reads it.
It's not 1.1.1, it's not 1.3.1 cos it's not the relationships that are the issue, or any of the 1.4 checkpoints
It's not 2.1 cos it's not operable - it's just text.

TL;DR - it's clearly a bug and I wouldn't care but the customer insists on having a WCAG guideline is possible.

Thank you all in advance.

Kevin Prince