E-mail List Archives
Re: WCAG 2.0: multiple buttons with the same name accessible
From: Paul Adam
Date: Nov 19, 2014 10:40AM
- Next message: Jonathan Avila: "Re: WCAG 2.0: multiple buttons with the same nameaccessible"
- Previous message: Bim Egan: "Re: WCAG 2.0: multiple buttons with the same name accessible"
- Next message in Thread: Jonathan Avila: "Re: WCAG 2.0: multiple buttons with the same nameaccessible"
- Previous message in Thread: Bim Egan: "Re: WCAG 2.0: multiple buttons with the same name accessible"
- View all messages in this Thread
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
>
>
>
>
>
- Next message: Jonathan Avila: "Re: WCAG 2.0: multiple buttons with the same nameaccessible"
- Previous message: Bim Egan: "Re: WCAG 2.0: multiple buttons with the same name accessible"
- Next message in Thread: Jonathan Avila: "Re: WCAG 2.0: multiple buttons with the same nameaccessible"
- Previous message in Thread: Bim Egan: "Re: WCAG 2.0: multiple buttons with the same name accessible"
- View all messages in this Thread