W3C Validation Shows Errors: How Concerned Should I Be? + Request

[mnichols]

In his reply to a person re: category display and IE, Rick mentioned that the W3C validation listed some errors, here. As an experiment, I ran my site through the validator and got lots of errors.

I'm confused because a couple of the errors listed involve text widgets and a couple of mods I've made. When I looked at the code I wrote, what is listed as missing in the verification is there in the code! For example, it says that I left out some ">" symbols, but I didn't (though I do admit to non-expertise as far as HTML, CSS etc go). Or it shows errors of omission and commission that are nowhere close to my code and must have been added when the HTML was generated.

In addition, there are a slew of errors that are unrelated to my mods and which I have no control over. The only thing I can think of is the way WordPress generates the HTML is what causes the errors.

The question: How concerned should I be about the errors listed? Is W3C just being nitpicky? Is WordPress to blame? Should I just go get a beer and forget about it?

The request: My blog displays well on the Mac with Safari, Firefox and DEVONAgent. I don't know what it looks like on a PC, especially with IE. Could some generous soul with a PC take a look at it with IE and Firefox and let me know?

[kingdomgeek]

In order to ensure that your site renders properly across the widest possible assortment of user-agents, valid HTML is important. I prefer to view the error messages grouped, and I would definitely look into those errors classed as parsing errors.

Many user-agents are very forgiving regarding invalid markup; others may not be. IE is a train wreck no matter what, in my opinion. :P

As a pro-tip, though, I would say that nitpicking your site until it has valid markup is a fantastic way to learn HTML & CSS; that's how I learned a few years ago.

Likewise, WordPress -- despite their mantra that "Code Is Poetry" -- outputs all sorts of weird code, so some of the errors may not be easily fixed (and could probably be ignored).

[mnichols]

Thank you for your quick reply, Rick. I'll do as you advise and check out the code, particularly the parsing errors. I'm trying to learn HTML, CSS et al as fast as I can. Maybe one of these days I won't have to keep hassling you!

As a silly sidelight: Have you tried to say "Better Blogging Basics" fast 10 times?

[kingdomgeek]

Try "Beckman's Better Blogging Basics."

[carbonoffsetsdaily]

When I checked our site for HTML and CSS Validity with W3C I got TONS of errors and not sure how to even get started... here are the error pages:

[Invalid] Markup Validation of http://www.carbonoffsetsdaily.com/ - W3C Markup Validator
W3C CSS Validator results for http://www.carbonoffsetsdaily.com (CSS level 2.1)

Any suggestions on how to even get started would be highly appreciated

[mnichols]

I'm only getting started doing so. As per Rick's instructions to check the parsing errors first, I clicked the "Group Error Messages by Type" button and revalidated.

I found an error in my code right away.

Unfortunately, the rest of the lines were generated by WordPress and I don't know where to begin fixing them.

[kingdomgeek]

Problems with WordPress' code would be better reported to trac.wordpress.org so that hopefully the code will be improved in the core. You shouldn't have to hack or otherwise alter your WordPress installation to get truly "poetic" code. :P

carbonoffsetsdaily, it looks like the <p> tag at the end of this chunk of code is wholly superfluous and is causing a good deal of your errors:

<!--start mindbodygreen submit button in left corner-->
<div style="float:left; margin: 0px 10px 0px 0px;">
<!--begin MindBodyGreen button-->
<script type="text/javascript">
mbg_url = 'http://www.carbonoffsetsdaily.com/carbonmarketnews/carbon-reduction-commitment-to-bring-cash-flow-problems-kpmg-1036.htm';
mbg_title = 'Carbon Reduction Commitment to Bring Cash Flow Problems: KPMG';
mbg_energy = true;
</script>
<script type="text/javascript" src="http://mindbodygreen.com/js/mbg.js"></script>
<!--end MindBodyGreen button-->
</div>
<p>
<!--end mindbodygreen submit button in left corner-->

(Ignore the line numbering; I copied from the validator site; the line that should be removed is #12.)

Likewise, I've noticed many sites using the TARGET attribute of links, which is invalid HTML at this point. More modern solutions for opening links in new windows could probably be found in Windows. Unfortunately, WordPress still adds the TARGET attribute to links added via posting, which I hope is nothing more than a gross oversight on the dev team's part, but I wouldn't be surprised if it stayed in there a while.

I'm getting off my soap box now before I open even larger cans of worms, so to speak.