WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: WCAG 2.0: multiple buttons with the same nameaccessible

for

From: Andrew Kirkpatrick
Date: Nov 19, 2014 2:30PM


My understanding is the same as Jon's. Yes, it seems a problem if a button says "delete" and that is ok while a link that says "read more" may not be ok. I think that the WG may have been thinking about links as a type of control for one use and buttons as a different type used for another, but certainly we've seen that these control types are used interchangeably perhaps more than other pairings. The language of 2.4.4 does say links rather clearly, so I'm inclined to think that this needs to be added to the WCAG WG's list of issues that we need to keep in mind when at some future time we look at requirements for a new version or extension of WCAG. I've added this to our list.

I do think that it is a hard issue. For example, if I make a web-based rich text editor and have a button for "copy" it is very reasonable for a person to ask "copy what?", which is similar to asking "delete what?" or "read more of what?". So I do think that buttons need to be clearly identifiable, as do links, but we need to think about how to clearly identify what is required.

AWK


-----Original Message-----
From: <EMAIL REMOVED> [mailto: <EMAIL REMOVED> ] On Behalf Of Don Mauck
Sent: Wednesday, November 19, 2014 12:59 PM
To: WebAIM Discussion List
Subject: Re: [WebAIM] WCAG 2.0: multiple buttons with the same name accessible

I agree, it certainly seems that in this case buttons should be treated the same way links are. Is this an oversight from the WC3?

-----Original Message-----
From: Paul Adam [mailto: <EMAIL REMOVED> ]
Sent: Wednesday, November 19, 2014 10:53 AM
To: WebAIM Discussion List
Subject: Re: [WebAIM] WCAG 2.0: multiple buttons with the same name accessible

So it's ok if I have 10 buttons on the page that all say "Delete"? But not ok if I have 10 "read more" links?

Sent from my iPhone

On Nov 19, 2014, at 11:46 AM, Jonathan Avila < <EMAIL REMOVED> > wrote:

>> Isn't preceding heading no longer allowed for link purpose determination? Link purpose, button purpose same thing right?
>
> Yes, that is my understanding but it was also my understanding that SC 2.4.4 did not apply to buttons.
>
> Jonathan
>
> -----Original Message-----
> From: <EMAIL REMOVED>
> [mailto: <EMAIL REMOVED> ] On Behalf Of Paul Adam
> Sent: Wednesday, November 19, 2014 12:41 PM
> To: <EMAIL REMOVED> ; WebAIM Discussion List
> Subject: Re: [WebAIM] WCAG 2.0: multiple buttons with the same name
> accessible
>
> Isn't preceding heading no longer allowed for link purpose determination? Link purpose, button purpose same thing right?
>
> Sent from my iPhone
>
>> On Nov 19, 2014, at 10:40 AM, Bim Egan < <EMAIL REMOVED> > wrote:
>>
>> Hi Rob,
>>
>> In my view the situation you've described would mean that the buttons were
>> accessible under WCAG2. This is because there's a heading structure that
>> gives context for each of the same-name buttons. The purpose of the
>> button is programmatically determinable. Unfortunately, in some
>> screen readers this might mean that audible output includes the page
>> title as well as the preceding heading, but the context is there, so you've done your job.
>>
>>
>> HTH,
>>
>> Bim
>>
>>
>>
>>
>> -----Original Message-----
>> From: <EMAIL REMOVED>
>> [mailto: <EMAIL REMOVED> ] On Behalf Of Wloch, Rob
>> Sent: 19 November 2014 16:05
>> To: ' <EMAIL REMOVED> '
>> Subject: [WebAIM] WCAG 2.0: multiple buttons with the same name
>> accessible
>>
>> Hi all,
>>
>> I haven't been able to find an answer to this in the WCAG 2.0 so I
>> thought I'd ask in this forum for your opinions. Is it allowed to
>> have multiple buttons with the same name on a webpage? I'm wondering
>> if it's similar to the guidelines for links where screen readers
>> would see a list of links with multiple "click here" which isn't good.
>>
>> For example, something like below where the text between the square
>> brackets represents the button names:
>>
>> H2 Blah blah blah
>> [start]
>>
>> H2 Blah blah blah
>> [modify] [stop]
>>
>> H2 Blah blah blah
>> [modify] [stop]
>>
>> Thanks, Rob.
>> >> >> list messages to <EMAIL REMOVED>
>>
>> >> >> list messages to <EMAIL REMOVED>
> > > list messages to <EMAIL REMOVED>
> > > list messages to <EMAIL REMOVED>