Web Accessibility

From AccessGA Wiki
Jump to: navigation, search

About

Web Accessibility refers to the practice of making websites usable by people of all abilities and disabilities by incorporating accessibility standards into website design and development. Many individuals with disabilities use screen readers and other assistive technology to access the Internet and may encounter barriers to access if a website is not designed and developed with appropriate structure and adequate navigation. Incorporating the use of web accessibility guidelines with the principles of universal design and web usability best practices can maximize the user experience and ensure content is available to all users. Accessible websites improve the experience of all users.

"Web accessibility means that people with disabilities can perceive, understand, navigate, and interact with the Web, and that they can contribute to the Web," (W3C, Introduction to Web Accessibility).

(See also Universal Design, Assistive Technology, Section 508 Requirements)

Principles

Key groups have developed web accessibility guidelines and standards, including:

  • The U.S. Access Board, which developed the Telecommunications Act Accessibility Guidelines and Section 508 Standards
  • The World Wide Web Consortium (W3C) an international consortium, which develops protocols and guidelines to ensure the long-term growth of the Web.


W3C Web Content Accessibility Guidelines WCAG 2.0

  • Content must be perceivable.
  • Interface components in the content must be operable.
  • Content and controls must be understandable
  • Content should be robust enough to work with current and future user agents (including assistive technologies).

Techniques

Key Techniques for Web Content Accessibility

  • Provide document structure by using appropriate headings (<h1>, <h2>, <h3>).
  • Screen readers rely on document markup language for navigation.
  • Use CSS Style sheets to apply styles to your document.
  • Provide logical reading order.
  • Add appropriate alt text to all meaningful images.
  • Add appropriate alt text to charts and graphs.
  • Consider adding long description alt text when a longer description is required.
  • Provide synchronized captions for multimedia content.
  • Add the functionality to skip to the main content.
  • Add appropriate labels to forms.
  • Provide sufficient color contrast between text and background colors.
  • Do not use color as the sole means of communicating information such as required fields and error messages.
  • Explain all acronyms.
  • Use checklists for evaluation.
  • Navigate your website without a mouse, using only the keyboard.
  • Evaluate your website using a screen reader.
  • Add an accessibility statement to your website.
  • Provide users with the means to report inaccessible content.

Recommendations for Automated Website Checkers

Modern web hosting environments demand modern tools. An automated assessment tool is one of the key, critical components of a comprehensive approach to Section 508 compliance. It is important to note that automated testing alone cannot ensure compliance of websites or web-based content. Manual (subjective) tests and testing by individuals experienced with assistive technologies are integral components of the overall testing process. With this in mind, automated tools can quickly and efficiently provide accessibility reporting for website managers and content providers. Tools that provide suggestions for repair help take the guesswork out of accessibility compliance.

Recommended features include:

  • Successful Voluntary Product Accessibility Template (VPAT)
  • Scalable, configurable web-based platform
  • User-friendly interface
  • Continuous monitoring
  • Craws complex structures
  • Single reporting of repeated issues
  • High quality, reliable results
  • Customizable reporting to standards of choice (508, WCAG 2.0, Mobile, etc.)
  • Suggestions for remediation
  • Guidance for manual testing
  • Bypass unchanged content
  • Differentiate common issues from unique ones (i.e. templates)
  • Ability to test:
    • Document Object Module (DOM) of web pages
    • Uploaded files, native format
    • Source code entered directly
    • Content in non-public development environments
    • Public-facing content
    • Web-based applications, user interfaces, content management systems, learning management systems
    • Content on multiple platforms (Mac, PC, Mobile, etc.)
  • Trial version prior to purchase
  • Vendor support and training

Resources

Checklists

Easy Checks - A First Review of Web Accessibility

Identifying Web Accessibility Issues from NCDAE

WebAIM's WCAG 2.0 Checklist

Web Content Accessibility Guidelines 2.0 Checklist

Website Accessibility Conformance Evaluation Methodology (WCAG-EM) 1.0

Guidelines and Demos

10 Easy Accessibility Tips from WebAIM

Web Accessibility Tutorials

ARIA Landmarks Tutorial

Improving a Web site with WCAG 2.0 Before and After Demonstration

Section 508 Standards

Section 508 Summary Requirements Penn State

The Accessibility Project

University System of Georgia Accessibility

W3C Cascading Style Sheets

W3C Web Accessibility Initiative (WAI)

Web Accessibility Toolkit

Web Accessible Rich Internet Applications

WebAIM Introduction to Web Accessibility

WCAG 2.0 Guidelines

WCAG 2.0 Quick Reference List

Publications and Blogs

Accessibility Lipstick on a Usability Pig

Google- Accessibility is NOT Just for Blind

Recommendations

Recommendations and suggestions from the AccessIT Community