Commentary

Peter Hagopian
 

Making The Web - And Your Content - More Accessible

Last week, after a long process of drafting and refining the documents, W3C's Web Accessibility Initiative released the Web Content Accessibility Guidelines 2.0 (WCAG 2.0). It's been nine years since the guidelines have been updated, and while the technology behind Web sites has vastly changed, the basic need for accessibility hasn't.

Last week, after a long process of drafting and refining the documents, W3C's Web Accessibility Initiative released the Web Content Accessibility Guidelines 2.0 (WCAG 2.0). It's been nine years since the guidelines have been updated, and while the technology behind Web sites has vastly changed, the basic need for accessibility hasn't.In a nutshell, WCAG 2.0 is a series of guidelines around making Web sites accessible to older users, the vision impaired, and other people with disabilities. From the World Wide Web Consortium's (W3C) blog post announcing the new guidelines:

WCAG 2.0 is a significant improvement. It's better for Web site creators, it's better for people with disabilities, and many others, too. WCAG 2.0 met its goals: to apply to more advanced technologies; to be more precisely testable (with automated testing and human evaluation); and to be easier to use and understand.

More Business Intelligence Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

While the guidelines themselves are extremely detailed, W3C has provided an excellent quick reference guide on how to meet the guidelines, running through both technical best practices and pitfalls to avoid as well as the different levels of success criteria.

While many content management tools already have functionality to assist with making sites more accessible, a new set of Authoring Tool Accessibility Guidelines (ATAG 2.0) also is being developed.

The goal of ATAG 2.0 is twofold -- offering recommendations on how the tools can help make content more accessible, while at the same time making the tools themselves more accessible to those with disabilities. A working draft of the ATAG 2.0 guidelines has been made available and the Authoring Tool Accessibility Guidelines Working Group is currently gathering feedback.

Unless your organization is federally funded or has government contracts (in which case you must adhere to Section 508 regulations), there's no legal mandate that your site must be accessible. But thanks to the efforts of dozens of volunteers putting in hundreds of hours of work, WCAG 2.0 makes it easier than ever to understand how to do the right thing.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links