WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Is a button that does not support space bar activation a violation of WCAG?

for

From: Birkir R. Gunnarsson
Date: May 6, 2015 7:37PM

Yeah, that is the core of my question basically.
WCAG says that all page elements have to be keyboard operable, but the
standard does not specify a manner in which they have to be keyboard
operable.
I have always recommended space bar activation for buttons (because
that is a function supported by native html button elements).
It has never really come to a head for me, but I would have stopped
short of demanding it if buttons are made keyboard accessible in a
predictable or documented manner.
Cheers





On 5/6/15, Jonathan Avila < <EMAIL REMOVED> > wrote:
>> I was asking if it was an absolute requirement of WCAG that all buttons be
>> coded so that either enter or spacebar activates them. My guess from
>> where this discussion has gone is no.
>
> It depends who you talk too -- so -- at this point there is no consensus
> that I am aware of on this being a requirement. I'd assume we all agree
> it's at least advisory though. There are many other techniques that fall
> into this category and over time techniques may move from not having
> consensus into having consensus. For example, do banner and footer content
> have to be marked as such as with HTML5 or ARIA -- do groups of links have
> to be within a nav or use navigation role, etc. My thoughts are my own and
> I'm not speaking for any working groups.
>
> Jonathan
>
> --
> Jonathan Avila
> Chief Accessibility Officer
> SSB BART Group
> <EMAIL REMOVED>
>
> 703-637-8957 (o)
> Follow us: Facebook | Twitter | LinkedIn | Blog | Newsletter
>
>
>