Slashdot Mirror

← Back to Stories (view on slashdot.org)

Return of the WaSP

Posted by michael on from the nesting-under-your-eaves dept.

No_Weak_Heart writes "After a brief hiatus, the Web Standards Project (WaSP) has returned. Here's the story at Wired about this grassroots coalition which works to promote the adoption of web standards by authors, tool makers and in browsers. In a related vein, the Boston Globe has a comfy chat with Tim Berners-Lee, the guiding force behind many of those standards."

2 of 173 comments (clear)

  1. Well yes .. but ... by Mr_Silver · · Score: 5, Interesting
    The most popular browser in the world is pretty good at following the rules, the permutations of the Gecko engine (here are some: N M C) are all praiseworthy, and on top of that virtuous standards oatmeal is some pretty tasty rendering brown sugar; anti-aliased fonts are here to stay!

    Well, yes, I don't think many people but the most hardcore of standards purists could claim that IE isn't pretty good at following the rules. Thats not the issue.

    The issue is that it's not very good when the code doesn't follow the rules. The problem here is that IE "guesses" what you're trying to do.

    This in itself isn't a bad thing and from an end user perspective is a damn good idea. If I go visit a site that someone has made a basic error then at least I can still view the content, their mistake doesn't prevent me from getting what i want.

    The problem comes when people start getting used to writing sloppy HTML because it works on IE (yes, I made that mistake before I found the w3 validator and Opera) and when Microsoft products start producing sloppy HTML (Words and Powerpoint being two apparant examples, although I've not looked personally).

    So yes, web-standards great idea. But there should be a standard on what to do with badly formed HTML too.

    --
    Avantslash - View Slashdot cleanly on your mobile phone.
  2. Re:Slashdot by Lysander+Luddite · · Score: 5, Interesting

    well...

    Slashdot relies on tables for layout which is a big sin for WaSP. Not only do table-based layouts violate the structural markup that is the basis of HTML (and XML derivatives) it causes problems in browsers designed for the sight impaired (and therefore violates Section 508).

    Slashdot also uses deprecated tags such as (font) and (b) rather than use CSS to change text presentation. I also don't see any structural flow such as using (H)eader tags to enable things like search bots to more accurately determine page content and weighted analysis.

    So no, I would suspect Slashdot wouldn't stand up to WaSP scrutiny.