W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > July to September 2011

Re: Do buttons need to follow 2.4.4 or 2.4.6?

From: Sailesh Panchang <spanchang02@yahoo.com>
Date: Wed, 3 Aug 2011 13:40:14 -0700 (PDT)
Message-ID: <1312404014.99459.YahooMailClassic@web111708.mail.gq1.yahoo.com>
To: w3c-wai-gl@w3.org
>    Sometimes there is little semantic distinction between a button and
>    a link (there are cases where something really does both an action
>    and navigation so either semantic could be appropriate). In these
>    cases the conformance requirement seems to be higher if the author
>    chooses to use a button vs choosing to use a link, when the end
>    result for the user is really the same whichever they choose.
Sailesh:
Well if the link at the end of a form  appears like a link to everyone, that's fine. But when it is coded as a link but styled to look like a button such that  people identify it as a button, then there is a problem and it fails SC 4.1.2 because the role is not conveyed right by coding the UI element as a link.
 It should be coded as a button INPUT type=image or the like. Buttons can be discovered quickly too as they are distinct from links while navigating with AT. I always flag this as an SC 4.1.2 issue. 
I have brought this up to WCAG-WG attention more than once perhaps  also by public comments suggesting it be listed as a failure.
As stated in my last email, I agree with Loretta that inadequate labelling  is a SC 1.1.1 issue.
Sailesh
Received on Wednesday, 3 August 2011 20:40:41 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 3 August 2011 20:40:43 GMT