E-mail List Archives
Re: Where text exists but cannot be read by screenreader - which checkpoint?
From: Patrick H. Lauke
Date: Nov 10, 2023 4:52AM
- Next message: Mark Magennis: "Re: Where text exists but cannot be read by screenreader - which checkpoint?"
- Previous message: Mark Magennis: "Re: Where text exists but cannot be read by screenreader - which checkpoint?"
- Next message in Thread: Mark Magennis: "Re: Where text exists but cannot be read by screenreader - which checkpoint?"
- Previous message in Thread: Mark Magennis: "Re: Where text exists but cannot be read by screenreader - which checkpoint?"
- View all messages in this Thread
On 10/11/2023 10:09, Mark Magennis wrote:
> This is often something I wonder about. Here's a really simple example.
>
> <span>Password<span aria-hidden="true"> not </span>accepted</span>
>
> Visually it says "Password not accepted" but a screen reader reads "Password accepted". Obviously this is a massive accessibility fail, but is it a WCAG violation?
I'd usually slot this under 1.3.1 Info and Relationships, because
visually the "not" is styled to be visible and readable, but it's not
programmatically conveyed as such (or rather, it's programmatically
being suppressed).
P
--
Patrick H. Lauke
https://www.splintered.co.uk/ | https://github.com/patrickhlauke
https://flickr.com/photos/redux/ | https://www.deviantart.com/redux
https://mastodon.social/@patrick_h_lauke | skype: patrick_h_lauke
- Next message: Mark Magennis: "Re: Where text exists but cannot be read by screenreader - which checkpoint?"
- Previous message: Mark Magennis: "Re: Where text exists but cannot be read by screenreader - which checkpoint?"
- Next message in Thread: Mark Magennis: "Re: Where text exists but cannot be read by screenreader - which checkpoint?"
- Previous message in Thread: Mark Magennis: "Re: Where text exists but cannot be read by screenreader - which checkpoint?"
- View all messages in this Thread