Need help? Check out our Support site, then


W3C Validation Help!

  1. Hello, WordPress!

    My blog uses the Contempt theme. When I run the W3C validator on my homepage, I get 25 errors and 2 warnings. (here is a link to the results). I'm not sure why this should be. Can anyone explain how to fix this? As I understand it, as a WordPress.com blogger I can't edit the code that is showing up as erroneous. Is that right?

    Thanks!

    The blog I need help with is lettersblogatory.com.

  2. As I understand it the standards have changed and Theme Staff are currently busy with making all themes here compliant with the new HTML and CSS standards.

  3. Thanks, Time Thief! I take it that there's no reason to do anything other than wait, then. Any idea when this project will be completed?

  4. There are 130 themes and I have no idea when this work will be completed. I have flagged this thread this thread so it gets moved to the Themes Forum. The Theme Staff monitor that forum so they will reply to you. .

  5. Contempt was switched over to using an HTML5 doctype a while ago. I looked at the errors listed in the link you posted above, and they actually all look okay to me--while it is good to look for validation errors, not all new markup is going to match up exactly with the W3 standards specs at first (especially for things like HTML5). For example, here is an Open Graph protocol meta tag used for the Facebook Like sidebar widget which we recently added:

    <meta property="og:tag name" content="tag value"/>

    But the validator.w3.org link you sent returns an error for a line like that:

    Line 36, Column 42: Attribute property not allowed on element meta at this point.

    That error was triggered because property attribute isn't technically allowed by the spec. But in order to get the benefit the tag brings, we decide to use it anyway. There are several examples similar to this. When you read a validation report like the one you linked, you need to take into consideration what each item in the output means and whether it's proprietary but valid. It's a tradeoff to get extra functionality. What you really should be looking for in validator reports are things like syntax errors that will completely break the layout of a site or that are incorrectly nested elements.

    With regard to HTML5, tools for web standards are still be getting worked out. I noticed the link you provided has a heading "Using experimental feature: HTML5 Conformance Checker." and it mentions that it may be unreliable a times. Just something to keep in mind when using validator tools like that one.

    "The validator checked your document with an experimental feature: HTML5 Conformance Checker. This feature has been made available for your convenience, but be aware that it may be unreliable, or not perfectly up to date with the latest development of some cutting-edge technologies."

    I also checked out your site. It loads quickly for me and works properly. The Contempt theme works well from what I can see, and it doesn't have any critical mistakes in it.

  6. Thanks, designsimply! I will stop worrying about this.

Topic Closed

This topic has been closed to new replies.

About this Topic