Well, not quite. As Jeffrey Way perfectly explains in his article But it Doesn’t
Validate, validation is not irrelevant, but the final score of the CSS validator
might be. As Jeffrey says,
“This score serves no higher purpose than to provide you with feedback. It
neither contributes to accessibility, nor points out best-practices. In fact,
the validator can be misleading, as it signals errors that aren’t errors, by
any stretch of the imagination.[...] Validation isn’t a game, and, while it might be fun to test your skills to
determine how high you can get your score, always keep in mind: it
doesn’t matter. And never, ever, ever compromise the use of the latest
doctype, CSS3 techniques and selectors for the sake of validation.”— Jeffrey WayHaving our work validate 100% is not always the best for the project. If we
make sure that our code is clean and accessible, and that it validates
without the CSS3/HTML5-properties, then we should take our work to the
next level, meanwhile sacrificing part of the validation test results. We
should not let this factor keep us back. If we have a chance for true
innovation, then we shouldn’t allow ourselves to be restrained by
unnecessary boundaries.
All in All...
Whatever the factors that keep us from daring into these new CSS3 styles
or new HTML5 coding techniques, just for a tangible example, need to be
gotten over. Plain and simple. We need to move on and start using CSS3
and HTML5 today. The community will become a much more exciting and
innovative playground, which in turn will improve experiences for as well as