Slashdot Mirror
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?"
Rather than spam us with this, please read the post the /. team made regarding this. They said they weren't fully W3C compliant yet, but they would be fixing it in the next couple of days. Mkay? Mkay.
I'll subscribe to Slashdot when I see a month without a dupe, a typo, or an article the "editors" didn't read.
But a screen reader isn't the same thing as an aural user agent. A screen reader is an attempt to convey visible information via sound, whereas an aural user agent reads what is available. It's kinda like the difference between closed captioning and subtitles. One just represents who said what, and the other represents that plus environmental sounds that are pertinent to the reader.