WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: 4.1.2 Question

for

From: Birkir R. Gunnarsson
Date: Jan 20, 2017 12:40PM

Jim
No, 4.1.2 states that all actionable elements must have a name, a rol
and a value (though value is broad, sometimes it needs a state).

In your case the elements need role="button". If you can toggle these
elements on and off you have to use aria-pressed="true" when activated
and aria-pressed="false" when not (in which case we call them toggle
buttons).



On 1/20/17, Jim Homme < <EMAIL REMOVED> > wrote:
> Hi,
> I want to double ccheck that the logic I'm using to test something prooves
> that it is broken in applying 4.1.2. I'm saying that it fails. Below is my
> logic for testing.
>
>
> · The item is in the first row of a table
>
> · It has a role of table column header
>
> · I can tab to it
>
> · It speaks great messages that tell me what the text is, how the
> column is sorted, how to work with it, and how to use it.
>
> · It sppeaks clickable, but does not say "button," or "link," or
> something that would automatically tell me that I can use the keyboard to
> change it.
>
> · I'm failing it because I feel that the word clickable indicates
> what I can do to activate it, rather than what it is. I feel that maybe the
> developer should add a role or in some other way tell me that I can use my
> screen reader as I am trained to do. Am I being too strict here?
> Thanks.
>
> Jim
>
>
> =========> Jim Homme,
> Team Lead and Accessibility Consultant,
> Bender HighTest Accessibility Team
> Bender Consulting Services, Inc.,
> 412-787-8567,
> <EMAIL REMOVED>
> http://www.benderconsult.com/our%20services/hightest-accessible-technology-solutions
> E+R=O
>
> > > > >


--
Work hard. Have fun. Make history.