4 {{ upvoteCount | shortNum }}
4 {{ upvoteCount | shortNum }}

W3C validity, do you worry?

by Scott Ames
3 replies
I checked one of my sites and this is what I got:

W3C validity Invalid (69 errors, 1 warnings)

The thing is I use a WordPress blog. I would have hoped that they coded the Theme, plugins, etc. to be valid with W3C, but I guess not.
#validity #w3c #worry
  • Profile picture of the author webfighter
    I just checked and got "14 Errors, 1 warning(s)" for one of my websites. Personally, I do not care about w3c validity. Maybe if I get my hands into html and css - I might find the idea of a w3c valid website fascinating.

    And if w3c validity helps you in promoting your website in serps.
    Signature
    Generate Long Tail Keywords!
    {{ DiscussionBoard.errors[4575247].message }}
  • Profile picture of the author V8200T5
    I think W3C validity is not very important, but I try to keep it below 20 or 10 errors. Sometimes you can't avoid errors that are created by third party scripts or widgets.
    {{ DiscussionBoard.errors[4575263].message }}
  • Profile picture of the author Istvan Horvath
    Originally Posted by Scott Ames View Post

    The thing is I use a WordPress blog. I would have hoped that they coded the Theme, plugins, etc. to be valid with W3C, but I guess not.
    In my experience every empty WP blog is valid code - unless the theme was coded by some idiot

    As soon as you start using it, a lot of stuff is getting "invalid" by the standards of W3C... E.g even WP's own gallery display with captions.

    I have never really seen anybody around here worrying about the valid XHTML.
    That's another type of crowd: the purist geeks
    Signature

    {{ DiscussionBoard.errors[4575280].message }}

Trending Topics