E-mail List Archives
Re: WCAG 2.0: multiple buttons with the same name accessible
From: Sailesh Panchang
Date: Nov 20, 2014 6:49AM
- Next message: deborah.kaplan@suberic.net: "Re: Google Automatic Alts?"
- Previous message: Mallory van Achterberg: "Re: Google Automatic Alts?"
- Next message in Thread: Jason Kiss: "Re: Preceding headings and link context [wasWCAG 2.0: multiple buttons with the same name accessible]"
- Previous message in Thread: Wloch, Rob: "Re: WCAG 2.0: multiple buttons with the samenameaccessible"
- View all messages in this Thread
Rob,
This will be a violation of SC 2.4.6 (AA). The intent is "Descriptive
labels help users identify specific components within the content".
I have always failed this under SC 2.4.6.
Perhaps the following example will help you
http://mars.dequecloud.com/demo/form-markup.htm#tech9
Thanks,
Sailesh Panchang
On 11/19/14, Wloch, Rob < <EMAIL REMOVED> > wrote:
> Thank you everyone for your comments on this. My take from what I've read
> everyone say is that it technically passes based on the current WCAG 2.0 but
> probably isn't really a good thing to do. Technique H80 seems to be the
> closest thing that the WCAG 2.0 has for this scenario but for links rather
> than buttons.
>
>
- Next message: deborah.kaplan@suberic.net: "Re: Google Automatic Alts?"
- Previous message: Mallory van Achterberg: "Re: Google Automatic Alts?"
- Next message in Thread: Jason Kiss: "Re: Preceding headings and link context [wasWCAG 2.0: multiple buttons with the same name accessible]"
- Previous message in Thread: Wloch, Rob: "Re: WCAG 2.0: multiple buttons with the samenameaccessible"
- View all messages in this Thread