W3C Compliance - What’s the point

I’m taking down the links to W3C compliance from my site. Why?, one might ask. Because i’m not sure what I put them there for in the first place. I don’t think that I gain anything from its inclusion and it’s a major headache to comply, anyway. I give up. I just checked it a couple of minutes ago and is an unknown. It’s a mess. Here’s a sampling of my errors

  • Error
    Line 120 column 29:
    element “SCRIPT” undefined.
    <SCRIPT LANGUAGE="JavaScript">

    You have used the element named above in your document, but the
    document type you are using does not define an element of that name.
    This error is often caused by:

    • incorrect use of the “Strict” document type with a document that
      uses frames (e.g. you must use the “Frameset” document type to get
      the “<frameset>” element),
    • by using vendor proprietary extensions such as “<spacer>”
      or “<marquee>” (this is usually fixed by using CSS to achieve
      the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements
      must be all lower-case.

  • This one is complaining because the word ’script’ isn’t all lowercase. I also got an error because the opening tag is SCRIPT and the end one is script. Consistency is key when developing code, but
    some mistakes are simply too small to pay attention to. I don’t find the worth of it anymore.

  • Error
    Line 240 column 17:
    there is no attribute “style”.
    	<p><embed style=width:400px; height:326px;border:5px solid #567;” 

  • This one is because the Google Video in my blog has a style attribute. This is ridiculous. Cascading Style Sheets(CSS) are a wonderful tool, no doubt, but they are not always supported. And in this particular case, Google wants to make sure that when I’m posting their content, it looks how they want it to look. I support that. If I had content that might be posted all over the internet, I would want to take steps to make sure that the users of said content would not change the style and sully my reputation. It’s a perfectly reasonable use of inline style. This is similar to XHTML complaining if I put a “name” attribute in something that usually doesn’t have a name attribute (such as a table cell) I had to rewrite an entire function using the HTML DOM object, once and it wasn’t pretty nor a very effective use of my time. On a side note, Microsoft has finally released a “DOM Inspector” for Internet Explorer called “DevToolbar” which is integrated reasonably well into the browser. It can be found here:
    Internet Explorer Developer Toolbar
    .
    Another third party tool is here:
    AIS Web Accessibility Toolbar

    Granted these are very small things, i’ll probably fix them later, but i’m not feeling the use of making such small changes. It’s just silly and its hard to me to really WANT to fix these “problems”

    One Response to “W3C Compliance - What’s the point”

    1. vanna Says:

      Mark this point.

      I think this article was interest for you.

    Enter Your Thoughts

    *
    To prove you're a person (not a spam script), type the security word shown in the picture.
    Anti-Spam Image