[_] priority 3 asp.net sites anybody?
Tim Beadle
tim.beadle at gmail.com
Wed Nov 7 12:50:05 GMT 2007
On 07/11/2007, Jaya Chakrabarti <jayacg at gmail.com> wrote: > I've specified Priority 3 primarily because of the requirements within the > specification and we're not contesting it because we rather agree with the > sentiment. We all know that achieving priority 3 on launch and maintaining > priority 3 when clients have control over the content are two different > things, but are you asking because priority 3 (even just on launch) is not > achievable within an ASP.NET 2 framework? Wikipedia says its possible so it > must be true :-). I'm sure it's possible, I just think that it might be a case of "the perfect being the enemy of the good"; i.e. it's better to shoot for AA and get it rather than going for AAA and missing. Plus, the law of diminishing returns kicks in: if you go for AAA you're into quite esoteric and (as Laura says) non-auto-testable stuff that (IMHO) may make no practical difference to the people you're ostensibly trying to help. There are some things in WCAG 1.0 (e.g. Accesskeys) that, if implemented in order to gain conformance, actually make things *worse* for the user. Take a look at this, from Patrick "Redux" Lauke, of Salford Uni and a leading Accessibility advocate: http://www.accessifyforum.com/viewtopic.php?p=56277#56277 Also in that thread: "I've publicly said that I think the UK public sector ought to have its own standards body which shouldn't just blindly follow WCAG: but if that's not to be the case, then we are better off with WCAG 2.0 which now is focussed much more around the user experience, which is thing that is of critical importance. I'd love it (as Keegan would say) if we could convince people in the UK to move away from WCAG 1.0 as soon as possible and to either our own set of guidelines, or to something based on WCAG 2.0 (although obviously that's dependent on progress with wcag 2.0!)" -- Jack Pickard, http://www.accessifyforum.com/viewtopic.php?p=56273#56273 There's also the WCAG Samurai, which is Joe Clark's bringing of WCAG 1.0 up-to-date. Ultimately, test with real users of Assistive Technology if you can. Tim