- From: Charles McCathieNevile <charles@w3.org>
- Date: Sat, 23 Aug 2003 21:31:59 -0400 (EDT)
- To: Roberto Scano - IWA/HWG <rscano@iwa-italy.org>
- Cc: Doyle Burnett <dburnett@sesa.org>, W3C Web Content <w3c-wai-gl@w3.org>
There are some tools around that allow the user to validate manually - this feature is starting to be integrated into automatic testing toools as well. I know that it is a part of HiSoftware's tools, and supervised some students integrating it into the Open source WAI-Nu evaluation tool. I got "not found" trying to follow the link below, but I also have produceed a tool for declaring point by point which checkpoints are met. It uses Xforms, so you need a browser capable of handling them - there are plugins avaiable for "current" browsers, and there are browsers that handle them natively such as DENG and Xsmiles. http://www.w3.org/2001/sw/Europe/200305/axforms - there is a readme that explains what I am doing, and there are several development versions with more interesting features that don't necvessarily work yet. cheers Chaals On Tue, 19 Aug 2003, Roberto Scano - IWA/HWG wrote: >For personal experience (I represent inside W3C IWA/HWG, the world >biggest association of web professional), web develpers that don't work >directly in accessibility initiatives, for reach the "minimum level of >accessibility" only made the "Bobby" or other automatic testing tool >validation. >This is wrong also because these tools are not the "panacea" for the >validation: for eg. a lot of these don't validate CSS so there is the pr >oblem that if I use fixed size font the validator said me "xxxx approved >for level AA" but if the font are fixed size i cannot declare level 2. >The best to do is to create a policy maker (like this one: >http://www.prato.linux.it/~gbartolini/it/wcag/) where the developer in >good faith declare what points its work reached.
Received on Saturday, 23 August 2003 21:34:13 UTC