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

RE: Let's add an approved date field to Failures and Techniques

From: Jonathan Avila <jon.avila@ssbbartgroup.com>
Date: Tue, 3 May 2016 17:36:30 +0000
To: IG - WAI Interest Group List list <w3c-wai-ig@w3.org>, "GLWAI Guidelines WG org" <w3c-wai-gl@w3.org>
Message-ID: <BY2PR03MB272610F03FE5C5C2FB575459B7A0@BY2PR03MB272.namprd03.prod.outlook.com>
> 2. Best practices  (common ways to pass)

Currently common ways to pass are sufficient techniques and I like that term.  Best practices like advisory techniques in the WCAG context as I understand them may go above a success criteria and may not always fully address a success criteria in all situations.


-----Original Message-----
From: White, Jason J [mailto:jjwhite@ets.org] 
Sent: Tuesday, May 03, 2016 1:27 PM
To: Alastair Campbell; Gregg Vanderheiden
Cc: IG - WAI Interest Group List list; GLWAI Guidelines WG org
Subject: RE: Let's add an approved date field to Failures and Techniques

>-----Original Message-----
>From: Alastair Campbell [mailto:acampbell@nomensa.com]

>Perhaps with a little more obvious structure? On the call just now I 
>suggested we could have four levels:
>1. Techniques (definitely passes, quite specific) 2. Best practices 
>(common ways to pass) 3. Warnings (common ways that pages don’t pass, 
>but don’t automatically fail.) 4. Failures (common ways that pages 
>definitely fail, quite specific).

I like the proposal.

>I’m not sure there’s much we can do about Governments requiring 
>techniques or seeing every non-pass as a failure, that would be best 
>tackled by pushing the idea of functional performance vs requirements.

I also think there's a definite limit to the extent to which this working group should design documents in ways that seek to prevent misinterpretation or misapplication. Clarity and precision are important, but beyond those measures, I think the task of educating people (governments included) lies outside our scope.


This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited.

Thank you for your compliance.

Received on Tuesday, 3 May 2016 17:37:04 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 3 May 2016 17:37:05 UTC