Stuart Sherwood wrote: > >> Hi All, >> If you pass all these test, does this exhaust all accessibility >> issues or are there more? >>
Stuart, There are also the "soft" tests - often these deal with areas of cognitive issues, from dyslexia to English as a second or third language, etc. Consider the requirement for appropriate and descriptive ALT text... What is appropriate, and further, who decides? Then there is the whole issue of "readability" - test such as the Flesch-Kincaid Grade Level Score can give you an idea if your content is written in language appropriate for the site's intended audience, but it's hardly an exact science. (http://wats.ca/resources/determiningreadability/1). There are also issues surrounding appropriate use of tables, list types, etc. which require judgment calls. Here, once the appropriate container has been chosen (UL, OL, table?), you must then check to ensure that they have been constructed appropriately - for example does your table have (or even require) a summary? Scope / headers & ID, etc.? As for testing tools, in addition to the ones already mentioned, we have collected a number of other "gadgets" which can be of assistance: http://wats.ca/resources/testingtools/44 Geoff Deering wrote: > > http://www.w3.org/TR/WCAG10/full-checklist.html > http://www.w3.org/TR/WCAG10/checkpoint-list.html > > I think there are P3 checkpoints that are not covered here that you > would need to check manually. There are in fact checkpoints under all three Priorities which require "brain" intervention - they simply cannot be tested mechanically. Try running a page through something like Cynthia says (http://www.cynthiasays.com) will quickly show you what needs to be manually checked. Cynthia says also provides a fairly extensive chart of what and how their tests are run (http://www.cynthiasays.com/Standards/CynthiaVersusBobby.htm) > > Just as a side issue, there is a lot of debate in the accessibility > community about the merit of using accesskeys, tabindex, etc. Did somebody say accesskeys? Whoa-boy... Using Accesskeys - Is it worth it?: http://www.wats.ca/articles/accesskeys/19 More reasons why we don't use accesskeys: http://www.wats.ca/articles/accesskeyconflicts/37 Accesskeys and Reserved Keystroke Combinations: http://www.wats.ca/resources/accesskeysandkeystrokes/38 Link Relationships as an Alternative to Accesskeys: http://www.wats.ca/articles/accesskeyalternatives/52 The Future of Accesskeys: http://www.wats.ca/articles/thefutureofaccesskeys/66 > > IMHO, many accessibility practitioners aim for WAI-AA, whilst > incorporating the most practical of the WAI-AAA checkpoints to aid > accessibility. As a general assumption, this is a relatively fair statement. Please remember that the WCAG is now 6 years old (May 1999), and it's showing it's age. Regrettably, some developers must adhere slavishly to the checkpoints - often creating more problems than they are solving, but that is simply due to the fact that the Guidelines were never written to be Standards - but are now serving that role more often than not. If you *do* have the luxury of being flexible, shooting for a WCAG AA+ "standing" is probably your safest position, but determining that "ranking" cannot be measured by simple tools alone - a clear and experienced understanding of the issues will always be required. The clear understanding can come from hanging out in forums such as this one, the WAI-IG (http://www.w3.org/WAI/IG/), WebAIM (www.webaim.org/gettinghelp/) and GAWDS (the Guild of Accessible Web Developers - http://www.gawds.org/discuss/). Many of the regulars on these lists are only too happy to lend a hand and provide answers, etc. when asked. Experience on the other hand takes time... But it's really worth the wait. HTH JF -- John Foliot [EMAIL PROTECTED] Web Accessibility Specialist / Co-founder of WATS.ca Web Accessibility Testing and Services http://www.wats.ca Phone: 1-613-482-7053 ****************************************************** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help ******************************************************
