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: Loretta Guarino Reid <lorettaguarino@google.com>
Date: Wed, 3 Aug 2011 11:47:40 -0700
Message-ID: <CAHu5OWZ0T-DvtKcb53xUS=YABWPmQQ0wWHVX9_pmuSimjs0MQA@mail.gmail.com>
To: adam solomon <adam.solomon2@gmail.com>
Cc: WCAG <w3c-wai-gl@w3.org>
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 <http://www.w3.org/TR/2008/REC-WCAG20-20081211/#namedef> 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?
>>> Regards,
>>> James
Received on Wednesday, 3 August 2011 18:48:05 UTC

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