Skip to the content of this page.

Note: This site will look much better in a browser that supports web standards, but is accessible to any browser or internet device.

Home > Meetings > November 2001

Accessible Web Design

Greg Bumpus (geebump@yahoo.com)
Human Factors Specialist, Novell

November 15, 2001 — Novell, Provo

Meeting Summary

Greg guided us through section 508 requirements by sharing the checklist he has developed to guide web page authors throughout Novell.

  1. Provide a text equivalent for every non-text element.
  2. Ensure that all information conveyed with color is also available without color.
  3. Ensure that documents are readable without requiring style sheets.
  4. Avoid causing any part of the screen to flicker or blink.
  5. Provide a method for users to skip repetitive navigation links.
  6. If you require a timed response, give the user a means to indicate that they need more time.
  7. Make sure that users of assistive technology can access and understand the information contained in and requested by browser-based forms.
  8. Identify your frames with names that describe the purpose and functionality of each frame's contents.
  9. Markup data tables to permit users to identify cell contents with column and row headers. If formatting text in tables, be sure the page reads correctly when linearized.
  10. Use client-rather than server-side image maps whenever possible. Server-side maps must include redundant text links.
  11. Applets and Plug-ins must comply with all of the Section 508 requirements specified for "Software Applications and Operating Systems."
  12. Client-side scripts should not alter the user interface dynamically without providing associated functional text that can be read by assistive technology. Device specific event handlers should be avoided.
  13. Clearly identify the target of all hyperlinks.
  14. Validate your code using available tools, checklists, and guidelines.
  15. If there is really, truly no way to accommodate all of the above requirements, create "text-only" equivalent pages and ensure their content is updated along with the main pages.

Thanks to Greg for presenting and Novell for hosting.

Original meeting invitation:

Accessibility is about ensuring that physical disabilities are not obstacles to participation in society, including the use of technology. When it comes to developing for the browser, it means web sites and application interfaces that are accessible by design — available to everyone regardless of disability.

The industry's attention has been drawn to accessibility following the passage of Section 508 of the Rehabilitation Act, which requires equal access to electronic and information technology procured by Federal agencies. The federal Access Board developed accessibility standards for the various technologies covered by the law, and these standards have been folded into the U.S. government's procurement regulations.

508 is important not simply because it is "the right thing to do," although certainly that is true; in very practical terms, we should do it because it improves our products for everyone, regardless of disability. Fortunately, there are techniques for developing web content that make accessibility a reality without adding an extra burden. Accessible interfaces need not be spartan or unattractive -- one benefit of studying accessible design is that helps us come to grips with compliant web design methods which improve many aspects of our interface and interaction work. Accessible design is good design.

"The power of the Web is in its universality. Access by everyone regardless of disability is an essential aspect."
— Tim Berners-Lee, W3C Director and inventor of the World Wide Web

Agenda:

1) background on accessibility issues leading to 508
2) checklist of web UI accessibility issues and related techniques
3) how does this help improve design overall?
4) scope (how big is this really?) and prospects