WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: WCAG 2.0: multiple buttons with the same name accessible

for

From: Paul Adam
Date: Nov 19, 2014 10:40AM

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.
> > > messages to <EMAIL REMOVED>
>
> > >