WebAIM - Web Accessibility In Mind

E-mail List Archives

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

for

From: Lucy Greco
Date: Nov 19, 2014 12:09PM

hello:
forget about the rules for a second here. no its not OK to have buttons
with the same name!!
if they do different actions or take the same action on different elements.
yes a list of buttons can be used to move through the page and heading or
no heading before the button, in that list if the buttons do not do the
same thing the same name would drive me nuts.
yes if the button does the same thing to the same element its OK like the
example of save at the top and the bottom but save for ten different parts
of the page should not and would not be accessible .
some times we focus so much on the standered that we are forgetting its
reel users we are afecting here and we need to remember users come at every
thing in a diferent way. even in the table example given here i disagree if
there is no way to know witch item your removing or paying $10000 for the
button is a waist of web space. Lucy



--
Lucia Greco
Web Accessibility Evangelist
IST - Architecture, Platforms, and Integration
University of California, Berkeley
(510) 289-6008 skype: lucia1-greco
http://webaccess.berkeley.edu
Follow me on twitter @accessaces


On Wed, Nov 19, 2014 at 9:59 AM, Don Mauck < <EMAIL REMOVED> > wrote:

> 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?
>
>