Skip to main content

A List Apart: Articles: Where Our Standards Went Wrong

Popularity Report

Total Popularity Score: 0

Loading...
Loading...
Loading...
Loading...
Loading...
Loading...

Rank

Bookmark History

Saved by 3 people (0 private), first by anonymouse user on 2007-03-18


Public Sticky notes

  • shorten development cycles, as we no longer have to slog through through six layers of nested tables to build site templates.
  • lower maintenance costs, as the CSS Zen Garden showed us.
  • decrease page weight, which in turn reduces page load times and dramatically lowers bandwidth costs (we’ve Mike Davidson’s excellent ESPN.com interview to thank for those metrics).
  • Highlighted by meratspain

  • A proven increase in a site’s accessibility,
  • The promise of device independence,
  • The presence of a metric against which an individual or a team’s production can be measured, and
  • The knowledge that your site is future-proof, displaying in any standards-compliant browser yet to be invented.
  • Highlighted by meratspain

    Toward the end of my first year in business, I noticed that more and more of my time was spent working around invalid code. Layout issues that would have been trivial to fix in a valid, error-free template would take significantly longer to debug in a live page that had a few hundred validation errors. It was a matter of figuring out which parts of the page weren’t causing the errors, so I could focus on fixing the problematic section. But when the page’s markup has three or four hundred validation errors, this process quickly becomes a time sink. A necessary one, but a sink nonetheless.

    So by year’s end, I found that approximately fifteen percent of my time was spent mired in invalid code

    Highlighted by egonbianchet