Web Accessibility
What is Accessibility?
Accessibility is the ability to use a product (service or system) under limiting conditions resulting from functional or situational limitations. Functional limitations can be physical or mental (cognitive) and are usually associated to individuals with disabilities. Blindness, carpal tunnel syndrome, and arthritis are examples of functional limitations. Situational limitations arise from the need to use some resource under unfavorable conditions and affect us all. The need for eyes and hands free operation of a cellular phone while driving is an example of a situational limitation.

Accessibility makes resources that are well designed and implemented usable for individuals with disabilities. A person with disabilities uses some form of assistive technology to access the resource. For example, when a blind person is using a screen reader.

Usability
Assistive technologies, accessibility, and usability are three components that work together. For example in navigating the web, a person with a disability uses assistive technology to access information that is accessible. Beyond the resource being accessible to the disabled user, the information must be usable. A usable site is one that can be used effectively and efficiently and leads to user satisfaction. Accessibility and usability are best implemented when considered holistically and early in the design of the resource.

Why Consider Accessibility?
As a result of federal regulations (Section 508) accessibility is in the forefront of interface design for organizations dealing with the production of hardware, software and websites. There are however better reasons to develop accessible resources other than complying with the law. In particular, the resources become available to a broader group of people and in situations where use of the resource may have been limited. Resources designed with accessibility and usability in mind result in more effective access to information and higher levels of user satisfaction. Accessible sites often result in cost savings, and increased revenue from eCommerce transactions. Most importantly, there are ethical considerations, accessibility is not only the law, it's the right thing to do!
According to South Carolina and Federal requirements our educational websites must be compliant as of July 2006.
  1. A text equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc", or in element content).
  2. Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation.
  3. Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup.
  4. Documents shall be organized so they are readable without requiring an associated style sheet.
  5. Redundant text links shall be provided for each active region of a server-side image map.
  6. Client-side image maps shall be provided instead of server-side image maps except where the regions cannot be defined with an available geometric shape.
  7. Row and column headers shall be identified for data tables.
  8. Markup shall be used to associate data cells and header cells for data tables that have two or more logical levels of row or column headers.
  9. Frames shall be titled with text that facilitates frame identification and navigation.
  10. Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz.
  11. A text-only page, with equivalent information or functionality, shall be provided to make a web site comply with the provisions of this part, when compliance cannot be accomplished in any other way. The content of the text-only page shall be updated whenever the primary page changes.
  12. When pages utilize scripting languages to display content, or to create interface elements, the information provided by the script shall be identified with functional text that can be read by assistive technology.
  13. When a web page requires that an applet, plug-in or other application be present on the client system to interpret page content, the page must provide a link to a plug-in or applet that complies with §1194.21(a) through (l).
  14. When electronic forms are designed to be completed on-line, the form shall allow people using assistive technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues.
  15. A method shall be provided that permits users to skip repetitive navigation links.
  16. When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.
Other Resources
Information about the Web Accessibility Initiative provided by W3C (The World Wide Web Consortium).
http://www.w3.org/WAI

A great collection of information available on the Clemson University website.
http://dcit.clemson.edu/resources/accessibility

This toolbar assists in the developmnent of accessible websites. There are many others available and you are free to find the one that suits you best.
http://www.visionaustralia.org.au/toolbar/1.2/versions/en/documentation/WCAG_checklist.html

All the information you could ever want to know about Web Accessibility provided by Wikipedia.
http://en.wikipedia.org/wiki/Web_accessibility