• Tweet
• Sharebar

When the W3C speaks of Web Accessibility they may be referring to the design of browsers and media players and such. The W3C says that to be compliant, such devices “should support accessibility for people with disabilities and work with assistive technologies”. When we, the designers, writers, and purchasers of web sites, say Web Accessibility, we probably are talking about the code.

The W3C cares about the code too. Compliant code is likely to be accessible code, because they are thinking about web accessibility while setting the standards for compliance. If you are a writer of web sites or a purchaser of web site design, you should care about web accessibility and W3C compliance too.

The web is used by everyone. People working with any sort of disability you care to consider use the web. They work, browse, shop, and buy. As we get into the era of aging Baby Boomers, we will have more and more people that are using the Internet to extend their lives. Many will be dealing with some level of disability, like vision impairment or mobility and dexterity issues. But they will still be on the Web, shopping and buying. A mighty big market that is, and very Web Accessibility related.

I have been a critic of the W3C at times, and still grumble a bit. I think there should be support for a simpler form of coding, more like plain old HTML, and not requiring a degree. I don’t expect it to happen, and have almost ceased to mumble about it. But the W3C has done a fine job of the Web Accessibility Initiative thing, I must say. They consider the use of screen readers, for those who cannot read due to impairment, and magnifiers, for those who need enlargement to be able to read, and voice recognition implementation, for those who cannot use a keyboard or pointing device due to limb dysfunction or other disability. These things require a coder that knows how to use CSS, keeping the page focused on the content and not the code. It is another example of how W3C compliance tends to encourage web accessibility.

The W3C, tending to dryness in their text, if not outright gobbledygook, has issued an enlightening statement. On their Web Accessibility Initiative page they head a small paragraph with:

“Want to know how people with disabilities use your Web site? Ask.”

Brilliant! Who would have thought of it? Really, it’s a good idea, and one that your coder could implement for you. That is the kind of thing we should be doing, as writers and buyers of web sites. First, we either write or have written W3C compliant code, paying attention to the requirements of the Web Accessibility Initiative. Then, we ask nicely, saying: “How did that work for you, and how can we improve our site for your convenience”? That would be nice of us. And, not a bad thing, it would lead to higher traffic and higher profits as well. W3C compliance and adherence to the Web Accessibility Initiative standards isn’t just good conscience, it’s good business.