As has already been noted on previous occasions, automated accessibility testing tools can be useful … but only if their results are not merely taken at face value, but backed up by human testing and plain common sense.

All too often these tools simply follow accessibility guidelines by the letter, adding their own arbitrary (and often secret) heuristics to test what can’t be tested programmatically, and give a report containing false positives or false negatives (see for instance Isofarro’s excellent article on SiteMorse).

In this light, I find the accessibility check carried out as part of SilkTide’s sitescore quite amusing.

Testing one of my sites, the tool came across a single invalidly encoded character (an em dash from a copy/paste straight out of a Word document). Yes, this makes the page’s markup invalid, which in turn makes it fail WCAG 1.0 checkpoint 3.2 "Create documents that validate to published formal grammars".

Now, an automated tool would indeed be correct to flag this up as an issue (and fail the page for level AA and AAA), but SilkTide’s choice of words leaves a lot to be desired (and, to the cynic in me, sounds a lot like fear mongering intended to sell their consultancy services).

Under the ominous "British legal requirements" heading, the sitescore report states that the site:

… is probably unlawful in Britain from the 1st October 2004. The British Disability Discrimination Act makes it unlawful to discriminate against a disabled person by refusing to provide any service provided to members of the public - including websites.

This is wrong on at least three levels:

1. although the markup is invalid, in this instance the error is relatively minor; I would be very surprised if this single badly encoded character constituted a real access barrier to anybody;
2. the DDA does not specify any particular level of compliance, or indeed any set of guidelines at all; neither the DDA itself nor the related Code of Practice - Rights of Access - Goods, Facilities, Services and Premises mention WCAG or which level to aim for (although yes, WCAG will most certainly be taken into consideration once a case is brought to court, though it’s doubtful that an automated check against WCAG 1.0 will be the deciding factor in deciding on a site’s real accessibility);
3. the text perpetuates the false belief that October 2004 was the "cut-off" date for inaccessible web sites; the final part of the DDA, which indeed came into force in October 2004, only relates to physical adjustments to service providers’ premises - section III of the DDA, which relates to accessible web sites (as per the CoP), already came into force on 1 October 1999.

But, overall, it’s nice to know that an automated tool can now also give us such valuable legal advice…who needs lawyers anymore?

It’s an online advent calender, and behind each door you’ll find a web development tip/tutorial to impress your friends - 24 of them, to be precise. I’d prefer that to a piece of chocolate any day. 24 ways to impress your friends kicks off with some easy ajax prototyping.