W3C home > Mailing lists > Public > public-wai-evaltf@w3.org > June 2012

Re: Step 1.e: Define the Techniques to be used

From: Aurélien Levy <aurelien.levy@temesis.com>
Date: Fri, 01 Jun 2012 12:15:47 +0200
Message-ID: <4FC89653.9070104@temesis.com>
To: Eval TF <public-wai-evaltf@w3.org>
Hi

It's not their job to know accessibility in term of wcag conformance 
with WCAG vocabulary, it's their job to know how to make and design 
accessible code with the technology they use. At this time I don't WCAG 
techniques is very helpfull for that. It's a point I already discuss 
with shady and one of the reason I work on Accessibility Steps 
http://blog.temesis.com/post/2012/05/14/Accessibility-steps

Aurélien
> Hi,
>
> I don't presume to know all the web developers in the world - or those you work with.  Personally, I think what you say does a great disservice to the great many web developers out there who take accessibility very seriously and work very hard to follow WCAG 2.0 Techniques (or other techniques) in order to produce accessible web content.
>
> Just to clear - in your opinion, who's job do you think it is to know web content accessibility techniques - if not the web developer?
>
> Alistair
>
> On 1 Jun 2012, at 11:42, Aurélien Levy wrote:
>
>> Hi again
>>> 2) It would not have been missed if the web developer had specifically told you that they intended all elements attached to functions to be in the tab order. And, you had checked what they said.
>> So you presume that web developer know witch wcag techniques he implement, this is not the case for most of developer I work with most of them doesn't know techniques at all (and it's not their job the know it in my opinion, at least no in term of wcag conformance)
>>
>> Aurélien
>>
>


-- 
Aurélien Levy
----
Temesis
Received on Friday, 1 June 2012 10:16:12 GMT

This archive was generated by hypermail 2.3.1 : Friday, 8 March 2013 15:52:14 GMT