Validation is less important these days. As long as the output is solid, you shouldn’t have anything to worry about.
Here’s a good rule of thumb that I’ve adopted over the years. Does your site look fine in all browsers? Are there errors on your site? If so, then validation is one place to start. If not, don’t worry about it.
If you think it’s that important, check out Facebook, Twitter, Google, Microsoft, and even Apple. All of these sites have validation errors somewhere. They seem to be doing okay.
Thank you for the quick response and solid advice. The plugin works perfectly in all browsers I have tested, so I am not too concerned about that. I was just curious if the minor reference error could be fixed or not (I’m an irrational perfectionist at times). Not a big deal, though.
Again, great plugin!
Validation is important to someone like me, building a site for a program sponsored by a US government agency. The agency requires that the site meet accessibility and XHTML 1.0 transitional standards and pass the WC3 Validator.
This page
http://nusd2013.org/contact/
gets eight W3C Validator errors. Errors include:
— form tag must have an “action” attribute.
— input type=”email” isn’t recognized.
— text area requires rows and columns values.
— the “vfb-item-secret” list item has no closing “/li” tag.
— the “vfb-item-submit” list item and “vfb-submit” input use the same ID.
Yes, the form looks and works great in all browsers, but it doesn’t meet spec. Can any of these be cleaned up?
