E-mail List Archives
Re: Is a button that does not support space bar activationa violation of WCAG?
From: Jonathan Avila
Date: May 6, 2015 8:12PM
- Next message: Paul J. Adam: "Re: Is a button that does not support space bar activationa violation of WCAG?"
- Previous message: Sean Curtis: "Re: Is a button that does not support space bar activation a violation of WCAG?"
- Next message in Thread: Paul J. Adam: "Re: Is a button that does not support space bar activationa violation of WCAG?"
- Previous message in Thread: Sean Curtis: "Re: Is a button that does not support space bar activation a violation of WCAG?"
- View all messages in this Thread
> Things I'd consider a fail would be using an ARIA role that implies spacebar, arrow key, or escape key behavior without actually implementing that behavior. Seems like a 4.1.2 failure, i.e. you are using the incorrect role for this element since the behavior does not match the standard native element.
Then you might also say if something looks like a button but is implemented with a link then it's also a failure. These are all good discussions -- but we would really need consensus and then corresponding WCAG failure techniques to assist the wider community in determining conformance.
Jonathan
--
Jonathan Avila
Chief Accessibility Officer
SSB BART Group
<EMAIL REMOVED>
703-637-8957 (o)
Follow us: Facebook | Twitter | LinkedIn | Blog | Newsletter
- Next message: Paul J. Adam: "Re: Is a button that does not support space bar activationa violation of WCAG?"
- Previous message: Sean Curtis: "Re: Is a button that does not support space bar activation a violation of WCAG?"
- Next message in Thread: Paul J. Adam: "Re: Is a button that does not support space bar activationa violation of WCAG?"
- Previous message in Thread: Sean Curtis: "Re: Is a button that does not support space bar activation a violation of WCAG?"
- View all messages in this Thread