WCAG 2.0 and javascript
Home / Legal Issues & Web Standards / WCAG 2.0 and javascript
My hope is it doesn't become a big distraction, eating up eons of developer and other staff/managment time with little conclusive benefit.
And as an AT dev I'd now have to run around like a headless chicken triing to get on everyone's list...
_________________
creator of Talklets
Talklets ,
| Phil Teare wrote: |
| I think the notion of a list is misleading. There's never been one, and I doubt there will ever be one that is uncontravertial. |
I agree with Jack's comments. Certainly, WAI seem to be willing to leave it up to individual organisations (or even individual authors) to compile their own list.
The UK's Cabinet Office's has threatened to withdraw .gov.uk domains from any site that doesn't meet Level AA by December this year. They specified WCAG 1.0, but as version 2.0 moves towards a full recommendation, that may well change.
If it does, I think you would have to have some kind of list that designers, developers and authors could depend on. It's difficult to imagine many of the smaller public authorities having the resources to do it for themselves.
Phil is right that such a list will almost certainly be controversial. But if it were maintained or sponsored by an impartial body - the Equality and Human Rights Commission might be one - that might help. Or perhaps we need some kind of PAS 78-style collaborative effort?
I don't know what the answer is, but I think we need one.
| accessallareas wrote: |
|
Phil is right that such a list will almost certainly be controversial. |
the other controversy that i can foresee is: to simplify QA and compliance testing, there will probably (?) be some mandated techniques for councils etc to use...which flies against the idea that only the core wcag 2 guidelines are mandatory, while any techniques (even the ones listed in the official wcag 2 techniques doc) are only informative...
_________________
Patrick H. Lauke / webmaster / University of Salford
co-lead: WaSP Accesibility Task Force
take it to the streets ... WaSP Street Team
personal: splintered | photographia | redux
co-author: Web Accessibility - Web Standards and Regulatory Compliance
I think you've nailed it on a more fundamental/core level, Patrick.
The list can't be absolute, but I assume you must state it...?
But hey, the compromise may well be better than its absence in v1. In fact I'm guessing it will be.
_________________
creator of Talklets
Talklets ,
_________________
My CV type thing and my Life of Ben (Blog). Nigel Peck's Accessify Forum Requirements.
I've got to say though, you seem to be falling into the black and white trap again.
A lot of the issues I see will stem from the fact that AT devs don't know what they do and don't support. Almost all partially support x, y, and z.
Plus technologies, protocols and techniques themselves are not so clear cut.
You will find people considering "Does JAWS support AJAX?". The answer to this is obviously not yes or no.
_________________
creator of Talklets
Talklets ,
| accessallareas wrote: |
| The UK's Cabinet Office's has threatened to withdraw .gov.uk domains from any site that doesn't meet Level AA by December this year. |
Wasn't that only a consultation document? I don't believe there was ever any intention to rigorously enforce that: partly because I bet you could find a level A error (never mind a level AA error) on pretty much any site, as long as it's large enough...
Also, as you can see from Dan's tale of the COI what they were talking about was the potential that already existed to remove sites which did not meet their requirements. And obviously to date this has never been enforced..
_________________
Jack Pickard The Pickards Information Services| Blog | Twit
All times are GMT
You cannot post new topics in this forumYou cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


