- From: Jesse McCarthy <w3c@jessemccarthy.net>
- Date: Thu, 23 Feb 2006 04:31:44 -0800 (PST)
- To: 'CSS validator list' <www-validator-css@w3.org>
I think that applying CSS in ways that foster accessibility is worthwhile, and that tools that assist developers in doing so are also worthwhile, but I agree with Peter that the CSS validator is not an appropriate venue for an accessibility review. I probably never would think that the CSS validator should be addressing accessibility -- as Peter suggested, it seems more appropriate to have a separate tool do that -- but it really seems misguided to me that any effort would be put into that kind of development now while there are serious accuracy / reliability problems with actual validation nagging the software, like serious conformance-related bugs that take months to be addressed after being reported (e.g. http://www.w3.org/Bugs/Public/show_bug.cgi?id=2272 ). Like Peter I also care about the quality of my code and worry about the impression misleading validation results will have on clients and others. Falsely reported errors like those caused by the bug are much worse yet than questionable warnings. I realize that this issue relates to functionality that is already incorporated into the validator and is triggering a warning -- I'm just suggesting that it would be worthwhile for future effort on the development of the validator to concentrate on improving the quality of actual validation. Jesse McCarthy
Received on Thursday, 23 February 2006 13:05:48 UTC