Web Accessibility?

conJunk asks: "With Slashdot recently becoming HTML 4.01 compliant, my thoughts now drift to the subject of web accessibility. We all know that the Section 508 requirements are legally binding to those who work for or with the U.S. government, but it's still unclear whether or not U.S. companies are required to have accessible sites (unlike England, where it's very clear). How important are web accessibility and the W3C Accessibility Guidelines to you and/or your company? Where do you see this issue going in the next 10 years?"

Comments

Slashdot is not w3c compliant SEE BELOW

[polyp2000]

W3C QA Markup Validation Service
v0.7.0

* Skip Navigation | Home
* About...
* News
* Docs
* Help & FAQ
* Feedback
* Link Checker

Jump To:

* Results

Result: Failed validation, 56 errors
File: upload://Form Submission
Modified:
Server:
Size:
Content-Type:
Encoding: iso-8859-1
Doctype: HTML 4.01 Strict
This page is not Valid HTML 4.01 Strict!

Below are the results of attempting to parse this document with an SGML parser.

1. Error Line 21 column 40: there is no attribute "LANGUAGE". /. ! At least with the old design the font wa

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 "" element),
* by using vendor proprietary extensions such as "" or "" (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.

3. Error Line 543 column 27: element "WBR" undefined.

Great design, /. ! At least with the old design the font wa

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 "" element),
* by using vendor proprietary extensions such as "" or "" (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.

4. Error Line 543 column 324: element "NOBR" undefined. ... default font for the benefit of /. Serif and sans-serif do

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 "" element),
* by using vendor proprietary extensions such as "" or "" (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.

5. Error Line 543 column 330: element "WBR" undefined. ...lt font for the benefit of /. Serif and sans-serif do not w

You have used the element named above in your document, but the document ty