Css Globe

Community News

(X)HTML - CSS Validation: Why validate your webpages?

Delicious | Digg | Stumble | Reddit | Float | Subscribe to RSS Feed

Visit

Need more? Read these related posts:

• Building better web forms: Validation best practices
• XHTML Strict validation is a tool, not a way of life
• Rock Solid Form Validation With xHTML, CSS and jQuery
• An html form validator that will really do your validation
• Creating CSS Layouts: The Best Tutorials on Converting PSD to XHTML
• Build an American Flag out of XHTML and CSS
• When Validation Becomes Unimportant
• Popular Websites and XHTML Validation Errors
• xHTML - Wordpress - Contest
• Convert your XHTML to CSS in a flash
• XHTML/CSS Markup Generator
• XHTML 2 vs. HTML 5

View All Community News

Don't miss our updates

Stay up to date with our daily updates and subscribe to our RSS feed.

Comments

• Dave on 28 May, 2008 wrote:

  The article's reasons are odd. The idea that validating won't guarantee that there are no errors is true, but not a negative. Me making the site doesn't guarantee anyone will visit it, but that doesn't mean I shouldn't make any sites. Most visitors won't care, but most visitors don't care whether you use HTML 3 or HTML 4.01 and that's still an important decision.
  
  Validating your code has lots of 'sometimes' benefits: it will sometimes help you fix errors in your site, it will sometimes make it easier for a team to work together on a site (or for you or anyone to make future changes), it will sometimes help with browser compatibility and future-proofing (but IE will always throw a wrench in). It also has one negative: it takes resources. It's your responsibility to understand the benefits and costs and make an informed decision.

• tommylogic on 28 May, 2008 wrote:

  Fair enough.. but I think my next article will make make some of the reasonings a bit more apparent, as semantic markup becomes more and more important in tomorrow's design principles.