|
davidrandall -> RE: Don't Shoot Me! (10/5/2005 8:01:58)
|
With (x)html and CSS, they are either coded correctly or they aren't. Accessibility on the other hand is incredibly subjective. It isn't as simple as running the site through an automated checker and seeing if it passes. The guidelines laid down by the WAI are just that. Guidelines. They are open to interpretation. An automated checker is not open to interpretation. It cannot determine if your link text is appropriate in the context of the rest of the text. It cannot determine if the alt text of an image is appropriate for that image. Whenever I see a "AAA" badge I just think "yeah right". I know that's very negative of me but it's usually pretty clear to see, without viewing the code, if a site is accessible or not. quote:
why do shops, and other businesses display membership badges, and other affiliations on their shopfront They are recognisable and have meaning, which is one of the main problems with web badges: a lack of user recognition. Pretty much the only people who would understand valid (x)html, valid CSS, Bobby Approved, WAI AAA, Rediscover the Web, Get Firefox, GAWDS, UA-WG, BWDMA, etc, etc badges are those in the industry. A non techie is likely to ignore it because they don't understand it. If they do click on a badge, they are likely to be presented to a validation results screen that they don't understand. I think these type of badges are left off until there is an industry standard that actually carries some weight and is recognisable for what it is. Dave
|
|
|
|