Background information: There are many different types and levels of disabilities and the way in which a web page or online resource is written affects the quality and quantity of information retrieved. Challenges can include, all types of visual impairments, hearing impairments, motor impairments, and cognitive impairments, both permanent and temporary. Many times disabilities are not Creating web pages with accessibility issues in mind, allows every user to achieve a level of independence, a basic educational goal for all learners (more info).

It is also important to remember that html is an interpreted code; all browsers and computer platforms do not "read" the code and turn it into a web page exactly the same way. Older browsers, most notably Netscape 4.61 and Internet Explorer 4.5 and below, can not read many accessibility accommodations consequently they should no longer be used. "Modern" browsers are considered to be Netscape 6.0 or Internet Explorer 6.0 and above. Graphics, tables and forms cause the majority of accessibility issues for users with disabilities.

Visually impaired users frequently use screen reader software to read the contents of a web page out loud. These readers read the words line by line and can not describe images or animating unless they are accompanied by alternative text, or "alt" tags (more info), in the html source code. Tables may also cause problems if not coded correctly because the screen reader will not know when the line for one cell ends and the next cell begins (more info). Note, Netscape 4.61 and Internet Explorer 4.5 and below can not interpret alt tags or table definitions for screen readers.

Color blind users may not be able to see red and green hues or blue and yellow hues. It is very rare for an individual not to see any colors at all (more info).

Mobility impaired users may use touch screens or head pointers to take the place of a mouse. To facilitate these tools, it is very important that all important parts of the web page work without a mouse. Drop-down menus in forms, many interactive simulations, and rollovers are all examples of mouse-dependent web page elements (more info). Testing a page for usability without a mouse is easy if using Netscape 6.0 or Internet Explorer 5.0 or above; simply press the "Tab" key to move between the elements on the web page and press the "Enter" key to activate hot links. If the the Internet browser is an earlier version, then the "Tab" and "Enter" key will not allow the user to move through the page at all. However, if using the "Tab" and "Enter" key allows the user some actions but not others, the fault usually can be attributed to the way in which the web page is written.

Click here to return to the top of this page!

---

Online Resources & Tutorials:

The Access Board: Web-based Intranet and Internet Information and Applications, information and examples:
http://www.access-board.gov/sec508/guide/1194.22.htm

Colors for the Color Blind:
http://www.toledo-bend.com/colorblind/

Tarleton State University, Web Page design Guidelines, Tips & Tutorials:
http://www.tarleton.edu/~library/webpgaccount_lh.html#DESIGN

University of Maryland, Office of Information Technology; Quick Tips for Web Accessibility: http://www.oit.umd.edu/webclinics/quicktip.html

W3C Web Accessibility initiative (WAI):
http://www.w3.org/WAI/

WebAIM - How to create accessible tables: http://www.webaim.org/howto/tables

WebAIM - How to create accessible forms: http://www.webaim.org/howto/forms

WebAIM - "How to" resources, handbooks and tutorials: http://www.webaim.org/howto/

Click here to return to the top of this page!

---

Check Web Page Accessibility
Tools:

A-Prompt toolkit: http://aprompt.snow.utoronto.ca/

WEBxact (formerly Bobby from CAST): http://webxact.watchfire.com

WAVE 3.0 Web Accessibility Tool: http://wave.webaim.org/index.jsp

W3C HTML Validation Service: http://validator.w3.org/

Click here to return to the top of this page!

---

Write accessible web pages
Supporting information:
For an informative overview see the online journal article from Educational Technology Review, "Web Design for Accessibility: Policies and Practice" by Mr. Alan Foley, North Carolina State University, and Mr. Bob Regan, University of Wisconsin, Archived Issues, Volume 10, Number 1: http://www.aace.org/pubs/aacej/

The regulation: Section 508, Subpart B - Technical Standards
§ 1194.22 Web-based intranet and Internet information and applications: http://www.section508.gov/index.cfm?FuseAction=Content&ID=12#Web

National Center for Accessible media:
http://ncam.wgbh.org/

MAGpie (Media Access Generator): http://ncam.wgbh.org/webaccess/magpie

Click here to return to the top of this page!

---

Vendor Information:

Adobe Acrobat, Acrobat Solutions for Accessibility: http://www.adobe.com/products/acrobat/solutionsacc.html