Developing Websites for Older People: How Web Content Accessibility Guidelines (WCAG) 2.0 Applies | Web Accessibility Initiative (WAI) | W3C

Developing Websites for Older People:
How Web Content Accessibility Guidelines (WCAG) 2.0 Applies

in Older Users and Web Accessibility: Meeting the Needs of Ageing Web Users

Summary

An extensive literature
review identified that
existing standards from the W3C Web Accessibility Initiative
(WAI) address the accessibility needs of older
web users. This page introduces how to use Web Content Accessibility
Guidelines (WCAG) 2.0 to improve the accessibility and usability of
websites and web applications for older people.

Please see Web Accessibility and Older People: Meeting the Needs of
Ageing Web Users
for additional
background and resources on the overlapping needs of older people and
people with disabilities.

Page Contents

  • About WCAG 2.0
  • How WCAG 2.0 Applies to Older People
    • Perceivable information and user interface
      • Text size
      • Text style and text layout
      • Color and contrast
      • Multimedia
      • Text-to-speech (speech synthesis)
      • CAPTCHA
    • Operable user interface and navigation
      • Links
      • Navigation and location
      • Mouse use
      • Keyboard use and tabbing
      • Distractions
      • Sufficient time
    • Understandable information and user interface
      • Page organization
      • Understandable language
      • Consistent navigation and labeling
      • Pop-ups and new windows
      • Page refresh and updates
      • Instructions and input assistance
      • Error prevention and recovery for forms
    • Robust content and reliable interpretation
      • Older equipment/software

About WCAG 2.0

The Web Content Accessibility Guidelines (WCAG) 2.0 includes organizing
principles and guidelines, and has success criteria at three levels: A,
AA, AAA. WAI recommends meeting at least [...]

Read article at w3.org

Article Taxonomies

Categories:
Fatal error: Uncaught Error: Object of class WP_Error could not be converted to string in /home/webable/www/www/wp-content/themes/webable/content-mcm.php:65 Stack trace: #0 /home/webable/www/www/wp-includes/template.php(812): require() #1 /home/webable/www/www/wp-includes/template.php(745): load_template('/home/webable/w...', false, Array) #2 /home/webable/www/www/wp-includes/general-template.php(206): locate_template(Array, true, false, Array) #3 /home/webable/www/www/wp-content/themes/webable/single-mcm_article.php(15): get_template_part('content-mcm') #4 /home/webable/www/www/wp-includes/template-loader.php(106): include('/home/webable/w...') #5 /home/webable/www/www/wp-blog-header.php(19): require_once('/home/webable/w...') #6 /home/webable/www/www/index.php(17): require('/home/webable/w...') #7 {main} thrown in /home/webable/www/www/wp-content/themes/webable/content-mcm.php on line 65