Difference between revisions of "Web Accessibility"

From AccessGA Wiki
Jump to navigation Jump to search
Line 16: Line 16:
<br/>[http://www.w3.org/WAI/WCAG20/quickref/#guidelines <span style="font-size:larger"><span style="font-family: tahoma,geneva,sans-serif">WCAG 2.0 Quick Reference List</span></span>]
<br/>[http://www.w3.org/WAI/WCAG20/quickref/#guidelines <span style="font-size:larger"><span style="font-family: tahoma,geneva,sans-serif">WCAG 2.0 Quick Reference List</span></span>]
*<span style="font-size:larger"><span style="font-family: tahoma,geneva,sans-serif">Text Alternatives</span></span>
*<span style="font-size:larger"><span style="font-family: tahoma,geneva,sans-serif">Time-based Media Alternatives</span></span>
*<span style="font-size:larger"><span style="font-family: tahoma,geneva,sans-serif">Adaptable Content</span></span>
*<span style="font-size:larger"><span style="font-family: tahoma,geneva,sans-serif">Distinguishable Content</span></span>
*<span style="font-size:larger"><span style="font-family: tahoma,geneva,sans-serif">Keyboard Accessible</span></span>
*<span style="font-size:larger"><span style="font-family: tahoma,geneva,sans-serif">Enough Time</span></span>
*<span style="font-size:larger"><span style="font-family: tahoma,geneva,sans-serif">Seizures</span></span>
*<span style="font-size:larger"><span style="font-family: tahoma,geneva,sans-serif">Navigable</span></span>
*<span style="font-size:larger"><span style="font-family: tahoma,geneva,sans-serif">Readable and Understandable Content</span></span>
*<span style="font-size:larger"><span style="font-family: tahoma,geneva,sans-serif">Predictable Functionality and Operation</span></span>
*<span style="font-size:larger"><span style="font-family: tahoma,geneva,sans-serif">Input Assistance to Help Users Avoid and Correct Mistakes</span></span>
*<span style="font-size:larger"><span style="font-family: tahoma,geneva,sans-serif">Compatible with Current and Future Assitive Technologies</span></span>
[http://www.section508.gov/index.cfm?fuseAction=stdsSum <span style="font-size:larger"><span style="font-family: tahoma,geneva,sans-serif">Section 508 Standards</span></span>]
[http://www.section508.gov/index.cfm?fuseAction=stdsSum <span style="font-size:larger"><span style="font-family: tahoma,geneva,sans-serif">Section 508 Standards</span></span>]

Revision as of 12:22, 16 May 2013


Web Accessibility refers to the inclusive practice of making websites usable by people of all abilities and disabilities by incorporating accessibility standards into website design and development.  Individuals with disabilities may encounter barriers to access if a website is not designed and developed with accessibility in mind. 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.

"Web accessibility means that people with disabilities can perceive, understand, navigate, and interact with the Web, and that they can contribute to the Web.1" Accessible websites improve the experience of all users.

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


Key groups have developed web accessibility guidelines and standards including the US Access Board, which developed the Telecommunications Act Accessibility Guidelines and Section 508 Standards, and the World Wide Web Consortium, W3C, an international consortium which develops protocols and guidelines that ensure the long-term growth of the Web.

Web Content Accessibility Guidelines (WCAG) 2.0

1: Content must be perceivable.

2: Interface components in the content must beoperable.

3: Content and controls must be understandable

4: Content should be robust enough to work with current and future user agents (including assistive technologies)

WCAG 2.0 Quick Reference List

Section 508 Standards


Key Techniques

  • Use appropriate headings (<h1>, (<h2>, (<h3>) to provide document structure. Screen readers rely on the markup language for navigation.
  • Use CSS Style sheets to apply styles to your document.
  • 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.
  • Add the functionality to skip to the main content.
  • Add appropriate labels to forms.
  • Explain all acronyms.
  • Use checklists for evaluation.
  • Evaluate 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.


Improving a Web site using Web Content Accessibility Guidelines (WCAG) 2.0

Before and After Demonstration

WCAG 2.0 Guidelines

Web Accessible Rich Internet Applications

10 Easy Accessibility Tips from WebAIM

University System of Georgia Accessibility

Section 508 Summary Requirements Penn State

AccessIT Community recommendations/suggestions