Re: Taking another round at @summary

Le 6 janv. 2010 à 07:15, Lachlan Hunt a écrit :
> This should be a clear lesson that government policies should avoid mandating specific technical solutions to problems, as opposed to simply requiring that, for example in this case, complex tables be accompanied by some solution that adequately addresses the accessibility issues, without specifying what that solution must be in all cases.

Right now, I'm deep knees into this in a Web agency.

The constraints:

* A website for an organization under the regulation laws of Canada for accessibility. (WCAG AA)
* A Web agency making the Web site which has to be WCAG AA (where I am).
* The organization having at least two other agencies (marketing and design) for creating wireframes, design (photoshop mockups), and  sometimes content.
* A CMS with its own flaws

The Web developers team inside our Web agency has to follow a certain number of rules for making the Web site accessible. Sometimes, it requires many back and forth meetings for explaining people participating into that what is accessibility and why the sexy design will create big issues. This costs money and usually nobody wants to pay.

The Web agency being at the end of the production chain if a mistake is done, it will be its responsibility. Specific technical solutions are a must. We do not have the luxury of discussing for months about the best way of doing things (be "some solution that adequately addresses the accessibility issues"). This is reality.

That creates a lot of interesting issues with consequences on responsibilities, budget, expertise, etc.


The real world right is that a series of technical requirements are implemented in legal systems all over the planet.

-- 
Karl Dubost
Montréal, QC, Canada
http://www.la-grange.net/karl/

Received on Thursday, 7 January 2010 02:55:16 UTC