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