Difference between revisions of "Web Accessibility"
Nsinclair3 (talk | contribs) |
Nsinclair3 (talk | contribs) |
||
Line 50: | Line 50: | ||
*<span style="font-size:larger"><span style="font-family: tahoma,geneva,sans-serif">Provide users with the means to report inaccessible content.</span></span> | *<span style="font-size:larger"><span style="font-family: tahoma,geneva,sans-serif">Provide users with the means to report inaccessible content.</span></span> | ||
− | = <br/>Resources | + | = <br/>Resources<br/> = |
<span style="font-family:tahoma,geneva,sans-serif">I</span><span style="font-size:larger"><span style="font-family: tahoma,geneva,sans-serif">mproving a Web site using Web Content Accessibility Guidelines (WCAG) 2.0</span></span> | <span style="font-family:tahoma,geneva,sans-serif">I</span><span style="font-size:larger"><span style="font-family: tahoma,geneva,sans-serif">mproving a Web site using Web Content Accessibility Guidelines (WCAG) 2.0</span></span> | ||
− | <span style="font-size:larger"><span style="font-family: tahoma,geneva,sans-serif">[http://www.w3.org/WAI/demos/bad/Overview.html Before and After Demonstration]</span></span | + | <span style="font-size:larger"><span style="font-family: tahoma,geneva,sans-serif">[http://www.w3.org/WAI/demos/bad/Overview.html Before and After Demonstration]</span></span> |
− | <span style="font-size:larger"><span style="font-family: tahoma,geneva,sans-serif">[http://www.w3.org/TR/WCAG20-TECHS/ WCAG 2.0 Guidelines] | + | <span style="font-size:larger"><span style="font-family: tahoma,geneva,sans-serif">[http://www.w3.org/TR/WCAG20-TECHS/ WCAG 2.0 Guidelines]</span></span> |
<span style="font-size:larger"><span style="font-family: tahoma,geneva,sans-serif">[http://www.w3.org/WAI/intro/aria Web Accessible Rich Internet Applications]</span></span> | <span style="font-size:larger"><span style="font-family: tahoma,geneva,sans-serif">[http://www.w3.org/WAI/intro/aria Web Accessible Rich Internet Applications]</span></span> |
Revision as of 12:15, 16 May 2013
About
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)
Principles
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)
- Text Alternatives
- Time-based Media Alternatives
- Adaptable Content
- Distinguishable Content
- Keyboard Accessible
- Enough Time
- Seizures
- Navigable
- Readable and Understandable Content
- Predictable Functionality and Operation
- Input Assistance to Help Users Avoid and Correct Mistakes
- Compatible with Current and Future Assitive Technologies
Techniques
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.
Resources
Improving a Web site using Web Content Accessibility Guidelines (WCAG) 2.0
Before and After Demonstration
Web Accessible Rich Internet Applications
10 Easy Accessibility Tips from WebAIM
University System of Georgia Accessibility
Section 508 Summary Requirements Penn State