Web Accessibility

From WolfTech
Revision as of 12:36, 4 December 2006 by Ebndelo (talk | contribs)
Jump to navigation Jump to search

To be effective a website must be usable by the visitor so that they can easily and quickly find the information they need and efficiently complete all necessary transactions. It is therefore essential that all websites be made accessible in order to provide equal access to people with special needs. This includes but is not limited to, the blind and hearing impaired. The overall goal is to provide people with disabilities similar user-experiences as their peers.

NC State's Web Accessibility Regulations

North Carolina State University is required to provide reasonable access to its educational services, programs and activities in accordance with Section 504 of the Rehabilitation Act of 1973, the Americans with Disabilities Act (ADA) of 1990, and North Carolina state law (N.C. Gen. Stat. § 168A-7). Accordingly, official NC State web pages and online instructional material should be accessible to disabled persons where possible, or a reasonable alternative accommodation should be offered.

Non-compliance with the Regulations

If the NC State Web Developer fails to provide a response to the Information Technology Division's inquiry or does not address accessibility problems in a timely fashion, the Provost and Executive Vice Chancellor, in consultation with an accessibility compliance team if necessary, may direct the removal of non-exempt inaccessible Web content from service.

Making Web Accessibility Easy

While the Regulation requires that web pages meet the technical Section 508 standards, they are minimum requirements to make the pages become "technically" accessible and may not necessarily be functionally usable by people with disabilities. To be usable, websites must provide people with disabilities similar user-experiences as their peers.

Below you will find a list of best practices that will allow your site to be usable by everyone regardless of their individual functional capabilities. When applied to web, these best practices integrate well with assistive technology (AT) used by a person with a disability and provide equivalent access to all content including audio and visual material.

Most Common Web Accessibility Errors

1. Missing "alt tags"

    alt tags: an HTML tag that provides alternative text when non-textual elements, typically images

- make sure that every "img src" has a relevant "alt text"

    example: <img src="your_file.jpg" alt="This is my file" width="180px height="180px" />

2. missing "table summaries": SUMMARY sets a summary description for the table. SUMMARY is not recognized my most graphical browsers. It is primarily intended for use by non-graphical browser for web accessibility. - make sure that every table has a relevant summary

- ex.

3. using appropiate doctype (DTD) missing doc types (doesn't have to be XHTML) - HTML - <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> - <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> - <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Frameset//EN" "http://www.w3.org/TR/html4/frameset.dtd"> - XHTML - <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> - <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> - <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Frameset//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-frameset.dtd"> - When using the HTML doctypes all tags need to have opened and closed - ex.
[open tag:
, closed tag:
] - When using the XHTML doctypes some tags can be self-closed - ex.
4. making sure all tags are closed or self-closed 5. nest tags correctly [1]Software Tools for Validation, Repair and Authoring of Accessible Content

Non-Textual Content