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

Re: F68 forbids WAI ARIA to replace label element

From: Chris Beer <chris@codex.net.au>
Date: Thu, 30 Jun 2011 12:40:48 +1000
Message-Id: <B1CE7DB1-FE2B-4BC5-AAC8-52A3E96FE65F@codex.net.au>
Cc: WCAG <w3c-wai-gl@w3.org>
To: Sailesh Panchang <spanchang02@yahoo.com>
Very true - and in part that is what I mean by conflicts - identifying where explicit reference is needed to be made to ARIA in order to make it clear to the ST audience when reliance on ARIA will or will not constitute a failure or success.

Chris Beer (iPhone)

On 30/06/2011, at 12:31, Sailesh Panchang <spanchang02@yahoo.com> wrote:

> I think one needs to take a step back and look at the WAI-ARIA  specs. The intro clearly states that one should use standard HTML elements wherever possible because these are natively supported and role, state etc is exposed to browsers and AT. ARIA  is designed to improve the accessibility of dynamic content generated by scripts including custom elements / widgets. It is referred to as a bridging technology by the specs.  HTML works just fine with browsers and AT. Use technology for purpose it is designed and intended and documented.    
> I quote, "It is not appropriate to create objects with style and script when the host language provides a semantic element for that type of objects".
> So it is indeed a failure if one uses aria-labelledby on a standard HTML INPUT element without using HTML LABEL element. Use ARIA where standard HTML is not designed to work.  
> Refer to 1.3 and 1.4 on
> http://www.w3.org/TR/wai-aria/introduction
> Thanks,
> Sailesh Panchang
> www.deque.com
> Tel 571-344-1765
> --- On Wed, 6/29/11, Chris Beer <chris@codex.net.au> wrote:
> From: Chris Beer <chris@codex.net.au>
> Subject: Re: F68 forbids WAI ARIA to replace label element
> To: "WCAG" <w3c-wai-gl@w3.org>
> Date: Wednesday, June 29, 2011, 6:12 PM
> Agreed. Furthermore it will need an careful genericising rewrite to account not only for the fact that ARIA labelledby can be applied to more than simply form/input controls, but also to make it HTML5 applicable as well as 4.0x and XHTML.
> If no one gets to it, its on my to do list with HTML5 STs, (yeah yeah, I know) but that said, we'll need to look at all the techniques after they move to generalized (X)HTML for ARIA conflicts and impacts.
> Chris Beer (iPhone)
> On 30/06/2011, at 3:24, David MacDonald <david100@sympatico.ca> wrote:
> http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F68   As we ramp up for the introduction of WAI ARIA, we may need to fix some of our failures. F68 is a binary check that requires a <label> element. If not there is a failure of 4.1.2  I think we’ll need to allow for wai-aria (labelledby), while acknowledging the preference to native code.  David MacDonaldwww.eramp.com 
Received on Thursday, 30 June 2011 02:40:51 UTC

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