W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > July to September 2011

Re: Do buttons need to follow 2.4.4 or 2.4.6?

From: Sailesh Panchang <spanchang02@yahoo.com>
Date: Wed, 3 Aug 2011 12:25:39 -0700 (PDT)
Message-ID: <1312399539.11837.YahooMailClassic@web111711.mail.gq1.yahoo.com>
To: WCAG <w3c-wai-gl@w3.org>
I agree with your reasoning. So 1.1.1 should apply to all buttons. Flash should not be an exception.

--- On Wed, 8/3/11, Loretta Guarino Reid <lorettaguarino@google.com> wrote:

From: Loretta Guarino Reid <lorettaguarino@google.com>
Subject: Re: Do buttons need to follow 2.4.4 or 2.4.6?
To: "adam solomon" <adam.solomon2@gmail.com>
Cc: "WCAG" <w3c-wai-gl@w3.org>
Date: Wednesday, August 3, 2011, 2:47 PM

As James said, 4.1.2 is about the "how". There is no requirement in 4.1.2 about the quality of the name.

I believe Flash27 is listed for 2.4.4 because there is no "link" element in Flash, and buttons are used for this purpose. Andrew, is this right?

I think button naming is covered by this part of SC 1.1.1:
  " If non-text content is a control or accepts user input, then it has a name that describes its purpose."

On Wed, Aug 3, 2011 at 12:39 AM, adam solomon <adam.solomon2@gmail.com> wrote:

Although links have their own technique regarding descriptive text, such a technique for buttons seems to be absent. Considering this absence, however, 4.1.2 does, in my opinion, address the issue by implication. When one uses nondescriptive text for an button, the result is an inherent and complete lack of  programmatic determination for the name property (since an erroneous name is tantamount to an absent one), thus failing the success criterion.

On Tue, Aug 2, 2011 at 5:36 PM, James Nurthen <james.nurthen@oracle.com> wrote:

4.1.2 addresses the technical "how". It does not address the quality of the text which is addressed for other control types by 2.4.4 or 2.4.6 respectively.

On Aug 2, 2011, at 12:49 AM, adam solomon wrote:
http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/H91 would seem to indicate that it is a problem of 4.1.2. You have brought up a good point - 2.4.4 speaks specifically about links, not buttons, though the spirit of it could certainly pertain to buttons. We should really clarify this point and decide if that flash technique is really in the right place.

On Tue, Aug 2, 2011 at 9:51 AM, James Nurthen <james.nurthen@oracle.com> wrote:

Button labels (whether from the text of the button element or the value of button input elements) don't seem to fit into either 2.4.4 (link purpose in context) or 2.4.6 (Headings and Labels).

Does the button text need to fully identify the purpose of the button (for example when buttons are repeated on multiple rows of a table to perform an action on the row) or is it sufficient for the button to identify the purpose within the context of the correctly marked up row header?

Note that FLASH27 (FLASH27: Providing button labels that describe the purpose of a button ) is explicitly stated as being a sufficient technique for 2.4.4. Can I extend this to imply that HTML buttons are covered by 2.4.4 too?


Received on Wednesday, 3 August 2011 19:26:11 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 16 January 2018 15:34:08 UTC