Help Lower the Cost of CSS Validation
Jens O. Meiert, September 22, 2011 (↻ August 16, 2013).
This entry’s been written by Jens the Web Developer.
Validation is a baseline quality attribute. I have emphasized this in the past and recently shared a bit more about the reasons and how you can use validation on Google’s Webmaster Central blog.
So when all of us throw our CSS validation experience into one bucket, what do we get?
The W3C validator (typically to be used with the “CSS level 3” profile) may or may not report any issues. We get that.
If it does, some of the issues are false positives.
Some of the issues are “real” issues.
The impact of these issues varies, and may be relatively low assuming proper use of style sheets, especially if they are maintained centrally.
When we look at our current situation we may not want to conclude that there is no value in validating style sheets: it’s that the price for validating and catching real issues in a properly set up environment is rather high.
For CSS validation to become more useful the cost for it needs to go down: the noise generated by false positives and proprietary code will need to disappear.
Enjoy the most popular posts, perhaps including:
Leave a Comment
Unfortunately, comments are closed.