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

Re: Using HTML form controls and links (Success Criterion 4.1.2 (Name, Role, Value))

From: Christophe Strobbe <christophe.strobbe@esat.kuleuven.be>
Date: Tue, 02 Jun 2009 14:19:24 +0200
Message-Id: <6.2.5.6.2.20090602140345.03edfd90@esat.kuleuven.be>
To: <wai-xtech@w3.org>
Cc: <w3c-wai-gl@w3.org>
Hi Stefan,

At 10:16 2/06/2009, Schnabel, Stefan wrote:
>Hi Rich, Michael,
>
>is
>
><http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/H91>http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/H91
>
>absolutely NORMATIVE regarding 
><http://www.w3.org/TR/2008/REC-WCAG20-20081211/#ensure-compat-rsv>Success 
>Criterion 4.1.2 (Name, Role, Value)?

None of the techniques is normative. Developers are always allowed to 
use other techniques that meet the success criteria.


>For instance, do I violate WCAG 2.0 when I decide NOT to use a 
><select> statement for a combo in my application,
>and choose instead an input with an associated button and ARIA-Markup?
>
><strong>
>  With other words, is applied ARIA an 1:1 alternative to 
> <http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/H91>http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/H91?
></strong>

The above technique is just an HTML technique; it does not assume WAI-ARIA.
If you don't use a select element but something else combined with 
WAI-ARIA markup, that construct can only pass WCAG 2.0 if it can be 
shown that it is accessibility supported
(<http://www.w3.org/TR/2008/REC-WCAG20-20081211/#accessibility-supporteddef>) 
in the human language of the content. If that condition is not 
fulfilled, the construct can never meet SC 4.1.2.
The note to SC 4.1.2 (Name, Role, Value) says: "This success 
criterion is primarily for Web authors who develop or script their 
own user interface components. For example, standard HTML controls 
already meet this success criterion when used according to specification."
If you create your own user interface components, you end up at 
situation D in "Understanding SC 4.1.2" 
<http://www.w3.org/TR/UNDERSTANDING-WCAG20/ensure-compat-rsv.html>, 
which has one general technique:
<http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/G10>.

Does that help?

Best regards,

Christophe

>
>Anything else will lead to BIG discussions. This is a serious question.
>I think industry wants questions like these covered and clarified 
>because you can easily derive legal implications from this.
>
>In case you are NOT the right persons to ask: Who will that be?
>
>Also, it would help if in the ARIA spec a respective clarification 
>could be added.
>
>Best Regards
>Stefan

-- 
Christophe Strobbe
K.U.Leuven - Dept. of Electrical Engineering - SCD
Research Group on Document Architectures
Kasteelpark Arenberg 10 bus 2442
B-3001 Leuven-Heverlee
BELGIUM
tel: +32 16 32 85 51
http://www.docarch.be/
---
"Better products and services through end-user empowerment" 
http://www.usem-net.eu/
---
Please don't invite me to LinkedIn, Facebook, Quechup or other 
"social networks". You may have agreed to their "privacy policy", but 
I haven't.
Received on Tuesday, 2 June 2009 12:20:15 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:47:56 GMT