E-mail List Archives
Re: WCAG criterion failed when content can be read screen reader, when it shouldn't be?
From: Robert Fentress
Date: Dec 18, 2015 8:29AM
- Next message: Patrick H. Lauke: "Re: WCAG criterion failed when content can be read screen reader, when it shouldn't be?"
- Previous message: Bourne, Sarah (ITD): "Re: WCAG criterion failed when content can be read screen reader, when it shouldn't be?"
- Next message in Thread: Patrick H. Lauke: "Re: WCAG criterion failed when content can be read screen reader, when it shouldn't be?"
- Previous message in Thread: Bourne, Sarah (ITD): "Re: WCAG criterion failed when content can be read screen reader, when it shouldn't be?"
- View all messages in this Thread
I tend to agree. I guess 4.1.2 would fail, since the aria-hidden property
is not set properly, but it seems like a bit of a stretch, for some reason.
On Fri, Dec 18, 2015 at 8:40 AM, Bourne, Sarah (ITD) <
<EMAIL REMOVED> > wrote:
> 4.1.2 seems more likely to me. But I would consider this a failure of a
> functional requirement: some users are being shown content that is supposed
> to be hidden. You happened to notice it because a screen reader was
> picking it up, but there may other situations where this flaw is evident as
> well.
>
> sb
> Sarah E. Bourne
> Director of IT Accessibility, MassIT
> Commonwealth of Massachusetts
> 1 Ashburton Pl. rm 1601 Boston MA 02108
> 617-626-4502
> <EMAIL REMOVED>
> http://www.mass.gov/MassIT
>
>
- Next message: Patrick H. Lauke: "Re: WCAG criterion failed when content can be read screen reader, when it shouldn't be?"
- Previous message: Bourne, Sarah (ITD): "Re: WCAG criterion failed when content can be read screen reader, when it shouldn't be?"
- Next message in Thread: Patrick H. Lauke: "Re: WCAG criterion failed when content can be read screen reader, when it shouldn't be?"
- Previous message in Thread: Bourne, Sarah (ITD): "Re: WCAG criterion failed when content can be read screen reader, when it shouldn't be?"
- View all messages in this Thread