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