E-mail List Archives
Re: WCAG criterion failed when content can be read screen reader, when it shouldn't be?
From: Moore,Michael (Accessibility) (HHSC)
Date: Dec 18, 2015 8:48AM
- Next message: Andrew Kirkpatrick: "Re: WCAG criterion failed when content can be read screen reader, when it shouldn't be?"
- Previous message: Patrick H. Lauke: "Re: WCAG criterion failed when content can be read screen reader, when it shouldn't be?"
- Next message in Thread: Andrew Kirkpatrick: "Re: WCAG criterion failed when content can be read screen reader, when it shouldn't be?"
- Previous message in Thread: Patrick H. Lauke: "Re: WCAG criterion failed when content can be read screen reader, when it shouldn't be?"
- View all messages in this Thread
Sarah,
I really like your reasoning. Perhaps, as accessibility specialists we are overly focused on trying to relate every problem that we find to a specific accessibility standard not being met. I would imagine that the functional requirement of the application specified that the message is hidden after it is dismissed. That functional requirement was not met.
This is more ammunition for me to use in my efforts to make accessibility testing part of the unit, QA, and UAT/regression testing cycles and not a separate activity.
Thanks,
Mike Moore
Accessibility Coordinator
Texas Health and Human Services Commission
Civil Rights Office
(512) 438-3431 (Office)
-----Original Message-----
From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf Of Bourne, Sarah (ITD)
Sent: Friday, December 18, 2015 7:40 AM
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: Re: [WebAIM] WCAG criterion failed when content can be read screen reader, when it shouldn't be?
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
-----Original Message-----
From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf Of Maxability Accessibility for all
Sent: Thursday, December 17, 2015 12:01 PM
To: WebAIM Discussion List
Subject: Re: [WebAIM] WCAG criterion failed when content can be read screen reader, when it shouldn't be?
I am confused, 1.3.2 or 4.1.2? Both of them seems convincing to me though I am leaning towards 1.3.2 Meaningful sequence.
Thanks & Regards
Rakesh
On Thu, Dec 17, 2015 at 8:54 PM, Birkir R. Gunnarsson < <EMAIL REMOVED> > wrote:
> 4.1.2 (name, role, value, and technically state also) If it should be
> hidden to all users, it should to be hidden to a screen reader user as
> well.
>
>
>
> On 12/17/15, Robert Fentress < <EMAIL REMOVED> > wrote:
> > Can anybody tell me what WCAG criterion would be failed if there was
> > content that was readable to a screen reader that shouldn't be, for
> > instance, if one dismisses a modal dialog, but it is still readable
> > by
> the
> > screen reader at the end of the page? Thanks.
> >
> > Best,
> > Rob
> >
> > --
> > Robert Fentress
> > Senior Accessibility Solutions Designer
> > 540.231.1255
> >
> > Technology-enhanced Learning & Online Strategies Assistive
> > Technologies
> > 1180 Torgersen Hall
> > 620 Drillfield Drive (0434)
> > Blacksburg, Virginia 24061
> > > > > > archives at http://webaim.org/discussion/archives
> > > >
>
>
> --
> Work hard. Have fun. Make history.
> > > archives at http://webaim.org/discussion/archives
> >
- Next message: Andrew Kirkpatrick: "Re: WCAG criterion failed when content can be read screen reader, when it shouldn't be?"
- Previous message: Patrick H. Lauke: "Re: WCAG criterion failed when content can be read screen reader, when it shouldn't be?"
- Next message in Thread: Andrew Kirkpatrick: "Re: WCAG criterion failed when content can be read screen reader, when it shouldn't be?"
- Previous message in Thread: Patrick H. Lauke: "Re: WCAG criterion failed when content can be read screen reader, when it shouldn't be?"
- View all messages in this Thread