WebAIM - Web Accessibility In Mind

E-mail List Archives

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

for

From: Dean.Vasile@outlook.com
Date: Nov 9, 2023 6:17PM

In cases where screen readers fail to read specific text, and it's not covered by 1.1.1 (non-text content), you might want to consider looking into guidelines related to the structure and presentation of content. Checkpoints related to semantic structure, focus management, or ARIA roles could be relevant. Consider guidelines like 1.3 (Adaptable), 2.4 (Navigable), or 4.1 (Compatible). These guidelines often address issues related to how content is presented and accessed by different user agents, including screen readers.
Dean Vasile


617-799-1162

On Nov 9, 2023, at 8:01 PM, Kevin Prince < <EMAIL REMOVED> > wrote:

Thanks Dean, I can usually sort the solution - my issue is what checkpoint should they come under (for instance - the single line in the drop down is a selectise issue and we have a solution). Occasionally I'll see text that just isn't read: but it isn't 1.1.1 because it's not non-text content.

kevin