Does this page look plain and unstyled?

Tools, wizards, articles and tutorials on Web Accessibility for the conscientious web developer

Subscribe to Accessify's RSS Feed   

Copying 508 vs. raising the bar

On Friday, IBM Worldwide Accessibility Director Frances West wrote an op-ed piece in News.com raising what IBM sees as a red flag: the numerous new accessibility policies in development within Europe.

Titled “Accessibility could take a step backward”, one is lulled into a sense that West is advocating advances in accessibility policy, raising the bar from Section 508, passed in the United States in 1998. However, read closer and you’ll see the real message here: IBM wants 508 to be adopted around the world, as is.

It is true that a different accessibility policy in each country in Europe would result in a terrible mess. It would mean that software companies would need to ensure that each feature meets the different requirements of each government, paralyzing the development of even the simplest applications, and fragmenting the meaning of accessibility to the point of irrelevancy. Software developed today and delivered via the Internet is, by default, international in nature.

However, it is important not to fall into the trap West lays with this argument. Standards harmonization does not mean sticking to the first thing that came along, that being 508. Accessibility laws must evolve to meet the needs of modern software development. Section 508 itself requires the Access Board to review and update the standard as necessary.

In the interest of harmonization, IBM should be urging the numerous accessibility bodies in Europe, as well as those in technology leaders such as Japan and the United States, not to settle on the least common denominator. Section 508 has in some senses been a big success, but in other areas it has failed people with disabilities, and as it becomes more dated, it is destined to fail more often. Its greatest benefit is that it sets a single benchmark with a relatively low degree of subjectivity. But that alone doesn’t mean it’s perfect; it merely makes it measurable.

We as advocates of accessibility should be aware of the dynamic between software companies, their consumers, and the regulations set forth to benefit accessibility. IBM is calling for a worldwide baseline of Section 508. What they and other vendors really need is one unified, measurable standard applicable to all of their markets. And it is to everyone’s advantage to work toward such a standard, provided it is as rigorous as necessary to fully meet the access needs of users with disabilities. Settling for the aging 508 is not a victory for international accessibility. For large companies like IBM, whose software already complies with 508, it merely enforces the status quo.

Comments (1) left to “Copying 508 vs. raising the bar”

  1. Richard Rutter wrote:

    I’m not of the opinion that laws should dictate how developers should make sites accessible. For a start, technology marches far more quickly than the legal system.

    I believe the approach of Disability Discrimination Act in the UK has a more realistic approach, wherein websites are simply required to not discriminate against those with disabilities. It doesn’t say how that should be accomplished, which is as it should be.

    The onus is on the site owner to hire developers to make their site accessible, preferably before the fact, but failing that, upon receiving a complaint.

Post a Comment

(Never published)
 

Site Navigation

Outside reading

Migrating from WCAG 1.0 to WCAG 2.0
Roger Hudson provides a through transition guide from WCAG 1 to WCAG 2
Beyond CAPTCHA: No bots allowed
James Edwards (aka Brothercake) provides a useful run-down of the problems posed by using CAPTCHAs
Jeremy Keith does an excellent write-up of the Accessibility 2.0 conference (which I was unable to attend)
Sharepoint and Web Accessibility
Bruce Lawson describes the disparity between Sharepoint/MOSS developed web sites and the level of accessiblity that the tool offers to users (summary - it really is not good!)
How does a screen reader user really hear your web site?
Interesting post on Beast Blog about how a screen reader user - a real one! Not one of those fake web developer tester types! - uses the tool to read a web page. A few surprises were waiting in store for author Mike Cherim.
Web Accessibility Toolbar now available in simplified Chinese
The Web Accessibility Tools Consortium (WAT-C) release a simplified Chinese version of the Web Accessibility Toolbar.
Web 2.0 vs Web Accessibility
1-day seminar in London, 25th April, brings together experts in the field to discuss/demonstrate the accessibility issues faced by web 2.0.
Leading accessibility technologists form new alliance to fix problems
The Accessibility Interoperability Alliance (AIA), comprising (among others) Adobe, HP, Microsoft, Novell, and from the assistive tech industry Dolphin, GW Micro and HiSoftware forms to work together "to create and harmonize standards for accessible techn
Fieldsets, legends and screen readers
An excellent run-down of how fieldsets and legends can improve accessibility and how the various screen readers cope with this useful markup.
CAPTCHAs explained - WacBlog
Another really good post on the RNIB\'s Web Access Centre blog explaining captchas, why they\'re bad for accessibility and what the alternatives may be.
Making WCAG easier to read
Derek Featherstone has created some fancy style sheets to make reading WCAG documents a little easier on the eye.
Top Tips for the title attribute
Ann McMeekin provides a set of simple tips regarding when - or rather when not to - use the title attribute. \'Cos sometimes you can try *too much* to be helpful
California court tilts towards mandating web accessibility
Outlaw.com reports (on behalf of The Register) on the Target California class action lawsuit, digging a little deeper into what Target have been doing of late to address matters.
Screen Readers and display:none
Juicy Studio, aka Gez Lemon, investigate some quirks whereby screen readers announce content that they should not be. Perhaps this could be used for good rather than evil?
Google Developer Podcast: The status of accessibility on the Web
An interview with Google research scientist TV Rahman (and Hubbell, his seeing-eye dog!). Lots of talk about CAPTCHAs and accessibility, but no sign of a transcript for this interview as yet.

View all Accessify bookmarks on del.icio.us



This page is styled using Cascading Style Sheets (CSS). If you can read this message, the chances are that your browser does not properly support CSS or you have disabled this yourself. The content on this site is perfectly readable without style sheets, though; it just doesn't look quite so fancy.

site statistics

This site is partnered with MIS Web Design and Top4Office for Copiers and Digipro for Photocopiers. Web design by Swindon Internet & PR Services.

How you can help support this site: Learn web design from the creator of this site, or help him by requesting some PR Photography