Older Users and Web Accessibility Changelog

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

Published Version: http://www.w3.org/WAI/older-users/developing

About

In some situations, developers are tasked to create Web sites optimized for older users. Often they are not aware of the relationship between the accessibility needs of older users and the needs of people with disabilities. In fact, they may not even be aware of the existence of standards for Web accessibility at all. This resource would explain to them how they could benefit from implementing existing Web accessibility guidelines, and how to use them to create accessible Web sites for older users.

Scenarios

Purpose, Goals, Objectives

Rationale:

Objective:

Audience

Primary:

Secondary:

Scope

Will:

Will not:

Approach

Initial outline and ideas:

Title Options

WCAG for Older Users (technical page):

EOWG Brainstorm (technical page OR landing page)

See also title ideas for Older People land page below

References

WAI-AGE task force and EOWG Discussions:

Open Issues

ChangeLog

Changes 22 September 2010

Changes 9 September 2010

Changes 6 September 2010

Changes 13 August 2010

Changes 10 August 2010

Changes 4 August 2010

Changes 21 July 2010

Changes 29 June 2010

Changes 23 June 2010

Changes 16 June 2010

Changes 1 June 2010

{#x100526}Changes 26 May 2010

{#x100525}Changes 25 May 2010

{#x100520}Changes 20 May 2010

{#x100512}Changes 12 May 2010

{#x100506}Changes 6 May 2010

** {#backgd}Background from WAI-AGE Deliverables:** {#background-from-wai-age-deliverables .listintro}

Rationale:
This document describes how to use existing Web accessibility guidelines to create Web sites for older users. It highlights the relationship between the accessibility needs of older users and the needs of people with disabilities, and guides the readers to more in-depth resources such as the Web Content Accessibility Guidelines (WCAG) 2.0, the WAI-AGE Literature Review documents, or other relevant resources.
Proposal:
In some situations, developers are tasked to create Web sites for older users. Often they are not aware of the relationship between the accessibility needs of older users and the needs of people with disabilities. In fact, they may not even be aware of the existence of standards for Web accessibility at all. This resource would explain to them how they could benefit from existing Web accessibility guidelines, and how to use them to create accessible Web sites for older users.

Requirements Groupings option

A second attempt to organise material by the types of needs older users have, then show how WCAG 2.0 meets those needs. Trying the approach and presentation style used in Shared Web Experiences: Barriers Common to Mobile Device Users and People with Disabilities.

Groupings based on WAI Guidelines and Older Web Users: Findings from a Literature Review plus meeting identified impairments. Techniques drawn from early draft of Developing Websites for Older People (June 2010). Need to emphasize that any success criteria not listed still need to be met!

Questions:

  1. Is this ‘requirements’ approach working? Is the organisation/categorisation good? (Too many? Too few?)
  2. Is the level of explanation of each requirement sufficient?
  3. Might it be appropriate to link to the Lit Review for each requirement?
  4. How best to include success criteria that don’t readily fit into the proposed categories?
  5. @@
*--- start requirements groupings trial ---* ### Perceivable [definition: ]{.os}Information and user interface components must be presentable to users in ways they can perceive.[ end definition]{.os}
#### Text size Many older people experience declining eyesight that requires larger text within web pages. **WCAG 2.0 requirements:** - [1.4.4 - Resize text](http://www.w3.org/TR/WCAG20/#visual-audio-contrast-scale) (AA)\ - [1.4.8 - Visual Presentation](http://www.w3.org/TR/WCAG20/#visual-audio-contrast-visual-presentation) (AAA) **Techniques to consider:** - Providing large fonts by default (future link) - [](http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/C17)Avoiding scaling font sizes smaller than the user-agent default (future link) - [G178: Providing controls on the Web page that allow users to incrementally change the size of all text on the page up to 200 percent](http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/G178) - [C17: Scaling form elements which contain text](http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/C17) - [G179: Ensuring that there is no loss of content or functionality when the text resizes and text containers do not resize](http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/G179) - Ensuring that text in raster images is at least 18pt (future link) [\[@@ different form the following - reported \]]{.open} - Making sure any text in images of text is at least 14 points and has good contrast (future link)
#### Text style and presentation A number of studies recommended specific preferred text presentation styles for older people; other approaches identified here will make text easy to read.\ \[@@ a number of studies have identified that overly decorated text can be difficult to read \] Open items: - bold and underline - ?? **WCAG 2.0 requirements:** - [1.4.8 - Visual Presentation](http://www.w3.org/TR/WCAG20/#visual-audio-contrast-visual-presentation) (AAA) - [1.4.5 - Images of text](http://www.w3.org/WAI/WCAG20/quickref/#visual-audio-contrast-text-presentation) (AA) - [1.4.9 - Images of Text (No Exception)](http://www.w3.org/WAI/WCAG20/quickref/#visual-audio-contrast-visual-presentation-tech-optional-head) (AAA) - [Guideline 3.1 - Make text content readable and understandable](http://www.w3.org/WAI/WCAG20/quickref/#meaning) **Techniques to consider:** - Using readable fonts (future link) - Presenting text in sans serif font or providing a mechanism to achieve this (CSS) (future link) - Using upper and lower case according to the spelling conventions of the text language (future link) - [G172: Providing a mechanism to remove full justification of text](http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/G172) OR [G169: Aligning text on only one side](http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/G169) - Avoiding centrally aligned text (future link) - Avoiding text that is fully justified (to both left and right margins) in a way that causes poor spacing between words or characters (future link) - Using left-justified text for languages that are written left to right and right-justified text for languages that are written right-to-left (future link) - Avoiding chunks of italic text (future link) - [G188: Providing a button on the page to increase line spaces and paragraph spaces](http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/G188) - Providing sufficient inter-column spacing (future link) - Limiting text column width (future link)Putting an em-space or two spaces after sentences (future link) - Avoiding overuse of different styles on individual pages and in sites (future link) - [C22: Using CSS to control visual presentation of text](http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/C22) - [C30: Using CSS to replace text with images of text and providing user interface controls to switch](http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/C30)
#### Color and Contrast Many older people experience changing color perception and sensitivity, and loss of contrast sensitivity. **WCAG 2.0 requirements:** - [1.4.1 - Use of Color](http://www.w3.org/TR/WCAG20/#visual-audio-contrast-scale) (A) - [1.4.3 - Contrast (Minimum)](http://www.w3.org/TR/WCAG20/#visual-audio-contrast-contrast) (AA) - [1.4.6 - Contrast (Enhanced)](http://www.w3.org/TR/WCAG20/#visual-audio-contrast7) (AAA) - [1.4.8 - Visual Presentation](http://www.w3.org/TR/WCAG20/#visual-audio-contrast-visual-presentation) (AAA) **Techniques to consider:** - [G14: Ensuring that information conveyed by color differences is also available in text](http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/G14) - [G122: Including a text cue whenever color cues are used](http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/G122) - [G182: Ensuring that additional visual cues are available when text color differences are used to convey information](http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/G182) - [G183: Using a contrast ratio of 3:1 with surrounding text and providing additional visual cues on focus for links or controls where color alone is used to identify them](http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/G183) - Conveying information redundantly using color (future link) - [G18: Ensuring that a contrast ratio of at least 4.5:1 exists between text (and images of text) and background behind the text](http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/G18) - [G148: Not specifying background color, not specifying text color, and not using technology features that change those defaults](http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/G148) - [G174: Providing a control with a sufficient contrast ratio that allows users to switch to a presentation that uses sufficient contrast](http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/G174) - Using a light pastel background rather than a white background behind black text to create sufficient but not extreme contrast (future link) - [G111: Using color and pattern](http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/G111) - [](http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/G182)Using a higher contrast values for lines in diagrams (future link) - Providing sufficient color contrast in graphs and charts (future link) - Providing sufficient color contrast for empty text fields (future link) - [G17: Ensuring that a contrast ratio of at least 7:1 exists between text (and images of text) and background behind the text](http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/G17) [\[@@ how to include AAA techniques relative to AA techniques, e.g. G18 above \]]{.open} \[@@ visible links - include elsewhere? \]
#### Multimedia [Older people commonly experience declines in vision and hearing and require]{.listintro style="margin-top:0.2em"}[ alternatives such as captions, transcripts, and/or audio description]{.listintro style="margin-top:0.2em"}. **WCAG 2.0 requirements:** - [1.2.1 - Audio-only and Video-only (Prerecorded)](http://www.w3.org/WAI/WCAG20/quickref/#media-equiv-av-only-alt) (A) - [1.2.2 - Captions (Prerecorded)](http://www.w3.org/WAI/WCAG20/quickref/#qr-media-equiv-captions) (A) - [](http://www.w3.org/WAI/WCAG20/quickref/#qr-media-equiv-live-audio-only)[1.2.4 - Captions (Live)](http://www.w3.org/WAI/WCAG20/quickref/#qr-media-equiv-real-time-captions) (A) - [](http://www.w3.org/WAI/WCAG20/quickref/#qr-media-equiv-live-audio-only)[1.2.3 - Audio Description or Media Alternative (Prerecorded video)](http://www.w3.org/WAI/WCAG20/quickref/#media-equiv-audio-desc) (A) - [1.2.5 - Audio Description (Prerecorded video)](http://www.w3.org/WAI/WCAG20/quickref/#media-equiv-audio-desc-only) (AA) - [1.2.7 - Extended Audio Description (Prerecorded video)](http://www.w3.org/WAI/WCAG20/quickref/#media-equiv-extended-ad) (AAA) - [1.2.8 - Media Alternative (Prerecorded)](http://www.w3.org/WAI/WCAG20/quickref/#media-equiv-text-doc) (AAA) - [1.2.9 - Audio-only (Live)](http://www.w3.org/WAI/WCAG20/quickref/#qr-media-equiv-live-audio-only) (AAA) - [1.4.7 - Low or No Background Audio (Prerecorded)](http://www.w3.org/WAI/WCAG20/quickref/#visual-audio-contrast-noaudio) (AAA) **Techniques to consider:** - \[@@ list all the below? order ok? any others? \] - [G158: Providing an alternative for time-based media for audio-only content](http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/G158) - [G159: Providing an alternative for time-based media for video-only content](http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/G159) - [166: Providing audio that describes the important video content and describing it as such](http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/G166) - [G93: Providing open (always visible) captions](http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/G93) - [G87: Providing closed captions](http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/G87) - [G69: Providing an alternative for time based media](http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/G69) - [G78: Providing a second, user-selectable, audio track that includes audio descriptions](http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/G78) - [G173: Providing a version of a movie with audio descriptions](http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/G173) - [G8: Providing a movie with extended audio descriptions](http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/G8) - [G9: Creating captions for live synchronized media](http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/G9) *AND* [G93: Providing open (always visible) captions](http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/G93) - [G9: Creating captions for live synchronized media](http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/G9) *AND* [G87: Providing closed captions](http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/G87) - [G151: Providing a link to a text transcript of a prepared statement or script if the script is followed](http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/G151) - [G150: Providing text based alternatives for live audio-only content](http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/G150) - [G157: Incorporating a live audio captioning service into a Web page](http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/G157) - [G56: Mixing audio files so that non-speech sounds are at least 20 decibels lower than the speech audio content](http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/G56)
#### Speech synthesis Some older people are using text to speech (speech synthesis) software, which is becoming increasingly available in browsers and operating systems. **WCAG 2.0 requirements:** - [1.1.1 - Non-text Content](http://www.w3.org/WAI/WCAG20/quickref/#text-equiv-all) (A) - [1.3.1 - Info and Relationships](http://www.w3.org/WAI/WCAG20/quickref/#content-structure-separation-programmatic) (A) **Techniques to consider:** - [G94: Providing short text alternative for non-text content that serves the same purpose and presents the same information as the non-text content](http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/G94) - [H44: Using label elements to associate text labels with form controls](http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/H44) - [H42: Using h1-h6 to identify headings](http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/H42)
#### CAPTCHA - Completely Automated Public Turing tests to tell Computers and Humans Apart Many studies have identified that CAPTCHA presents a significant barrier for some people. **WCAG 2.0 requirements:** - [1.1.1 - Non-text Content](http://www.w3.org/WAI/WCAG20/quickref/#text-equiv-all) (A) **Techniques to consider:** - [G143: Providing a text alternative that describes the purpose of the CAPTCHA](http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/G143) *AND* [G144: Ensuring that the Web Page contains another CAPTCHA serving the same purpose using a different modality](http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/G144) - [](http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/G144)\[@@ contrast? \]
### Operable [definition: ]{.os}User interface components and navigation must be operable.[ end definition]{.os} Potential groupings: - distractions (scrolling text, blinking, animations, refresh) - clear links - clickable area - larger fonts? - navigation and location (site map, menu, 'home page' links, search, breadcrumbs) - tabbing
#### XX @@ **WCAG 2.0 requirements:** - @@ **Techniques to consider:** - @@
### Understandable [definition: ]{.os}Information and the operation of user interface must be understandable.[ end definition]{.os} Potential groupings: - Readable text - covered already - caps - justification - scrolling text - Understandable text - reading level - writing style (active voice, short sentences/paragraphs, front loading) - glossary - Pop-ups - Forms - timing/timouts - help & instruction - mistake identification - error correction - error avoidance (incl spelling accommodation) - clickable controls - focus - Navigation - covered already - consistency - \[about us, contact us, branding\] - Scanning (vs reading everything) - cover in Readable/Understanable text - headings - lists? ### Robust [definition: ]{.os}Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.[ end definition]{.os} Grouping: - older equipment ?? *--- end requirements groupings trial ---*

Presenting the Success Criteria (or Guidelines) within Impairment & Needs Groupings

A first attempt to organise material by the types of needs older users have, then show how WCAG 2.0 meets those needs.

Advantages of this approach:

Disadvantages of the approach:

Groupings might be:

*--- start impairments and needs groupings option trial ---* ### Addressing the Declining Eyesight/Vision of Older People {#declinevision} \[\[ @@ short introductory blurb about age-related vision decline and requirements of older people ... possibly break into text, images, design, multimedia issues, other ... \]\] \[\[ @@ none of the rationales have been rewritten to suit this approach as yet \]\] \[\[ **Editor's note:** the linked numbers in brackets below that currently link to the Literature Review are provided to assist technical reviewing of this document - they will be removed before publication. \]\] #### [Guideline 1.1 Text Alternatives](http://www.w3.org/WAI/WCAG20/quickref/#text-equiv) {#guideline-1.1-text-alternatives .listintro style="margin-top:0.2em"} Information rendered in electronic text can be presented in whatever form best meets the needs of the user. It can also be easily enlarged, or spoken aloud, so that it is easier for people with reading disabilities to understand. ##### [1.1.1 - Non-text Content](http://www.w3.org/WAI/WCAG20/quickref/#text-equiv-all) (A) {#non-text-content-a .listintro style="margin-top:0.2em"} This success criterion includes addressing CAPTCHAs which can pose a readability barrier for many, including older people with declining vision [\[03\]](http://www.w3.org/TR/2008/WD-wai-age-literature-20080514/#whatvision) #### [Guideline 1.2 Time-based Media](http://www.w3.org/WAI/WCAG20/quickref/#visual-audio-contrast){.listintro} {#guideline-1.2-time-based-media .listintro} Older people commonly experience a decline in vision [\[03\]](http://www.w3.org/TR/2008/WD-wai-age-literature-20080514/#whatvision) (as well as a significant decline in hearing [\[02\]](http://www.w3.org/TR/2008/WD-wai-age-literature-20080514/#whathearing)). Providing alternatives for video-only and multi-media files through captioning, transcripts, and/or audio description helps older people better understand time-based media. The following success criteria for [Guideline 1.2](http://www.w3.org/WAI/WCAG20/quickref/#visual-audio-contrast) will increase the accessibility of multi-media for older people with declining vision: - [[1.2.1 - Audio-only and Video-only (Prerecorded)](http://www.w3.org/WAI/WCAG20/quickref/#media-equiv-av-only-alt) (A)]{.style1} - **[1.2.3 - Audio Description or Media Alternative (Prerecorded video)](http://www.w3.org/WAI/WCAG20/quickref/#media-equiv-audio-desc) (A)** - **[1.2.5 - Audio Description (Prerecorded video)](http://www.w3.org/WAI/WCAG20/quickref/#media-equiv-audio-desc-only) (AA)** - **[1.2.7 - Extended Audio Description (Prerecorded video)](http://www.w3.org/WAI/WCAG20/quickref/#media-equiv-extended-ad) (AAA)** - **[1.2.8 - Media Alternative (Prerecorded)](http://www.w3.org/WAI/WCAG20/quickref/#media-equiv-text-doc) (AAA)** #### [Guideline 1.3 Adaptable](http://www.w3.org/WAI/WCAG20/quickref/#content-structure-separation) {#guideline-1.3-adaptable .listintro style="margin-top:0.2em"} This guideline ensures that all information is available in a form that can be perceived by all users, for example, spoken aloud, or presented in a different or simpler visual layout. ##### [1.3.1 - Info and Relationships](http://www.w3.org/WAI/WCAG20/quickref/#content-structure-separation-programmatic) (A) {#info-and-relationships-a .listintro style="margin-top:0.2em"} Older people whose color perception and contrast acuity declines significantly with older age [\[03\]](http://www.w3.org/TR/2008/WD-wai-age-literature-20080514/#whatvision) will benefit from the following technique: - [G138: Using semantic markup whenever color cues are used](http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/G138) ##### [1.3.2 - Meaningful Sequence](http://www.w3.org/WAI/WCAG20/quickref/#content-structure-separation-sequence) (A) {#meaningful-sequence-a .listintro style="margin-top:0.2em"} Older people experiencing a decline in vision [\[03\]](http://www.w3.org/TR/2008/WD-wai-age-literature-20080514/#whatvision) who may use the browser zoom feature or operating system text enlargement to adapt the page and make it easier to use may benefit from this success criterion. ##### [1.3.3 - Sensory Characteristics](http://www.w3.org/WAI/WCAG20/quickref/#content-structure-separation-understanding) (A) {#sensory-characteristics-a .listintro style="margin-top:0.2em"} Older people experiencing sensory declines [\[05\]](http://www.w3.org/TR/2008/WD-wai-age-literature-20080514/#what) and may not see (or hear) well will benefit from this criterion. #### [Guideline 1.4 Distinguishable](http://www.w3.org/WAI/WCAG20/quickref/#visual-audio-contrast) {#guideline-1.4-distinguishable .listintro} This guideline is concerned with making the default presentation as easy to perceive as possible to people with disabilities. The primary focus is on making it easier for users to separate foreground information, be it visual or audio information, from the background. ##### [1.4.4 - Resize text](http://www.w3.org/WAI/WCAG20/quickref/#visual-audio-contrast-scale) (AA) {#resize-text-aa .listintro style="margin-top:0.2em"} This success criterion will increase readability for older people experiencing a decline in vision [\[03\]](http://www.w3.org/TR/2008/WD-wai-age-literature-20080514/#whatvision) ##### [1.4.5 - Images of text](http://www.w3.org/WAI/WCAG20/quickref/#visual-audio-contrast-text-presentation) (AA) {#images-of-text-aa .listintro style="margin-top:0.2em"} Enabling more flexibility in text enlargement, or color and contrast modification, for older people experiencing a decline in vision [\[03\]](http://www.w3.org/TR/2008/WD-wai-age-literature-20080514/#whatvision) is a benefit of this success criterion ##### [1.4.9 - Images of Text (No Exception)](http://www.w3.org/WAI/WCAG20/quickref/#visual-audio-contrast-visual-presentation-tech-optional-head) (AAA) {#images-of-text-no-exception-aaa .listintro style="margin-top:0.2em"} This success criterion increases accessibility for older people experiencing a decline in vision [\[03\]](http://www.w3.org/TR/2008/WD-wai-age-literature-20080514/#whatvision) ##### [1.4.8 - Visual Presentation](http://www.w3.org/WAI/WCAG20/quickref/#visual-audio-contrast-visual-presentation) (AAA) {#visual-presentation-aaa .listintro style="margin-top:0.2em"} Older people can experience declining cognitive abilities [\[07\]](http://www.w3.org/TR/2008/WD-wai-age-literature-20080514/#whatcog) and declining vision [\[03\]](http://www.w3.org/TR/2008/WD-wai-age-literature-20080514/#whatvision) making many aspects of the visual presentation of text important for readability. Readability can be enhanced through techniques such as: - [G175: Providing a multi color selection tool on the page for foreground and background colors](http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/G175) - [G169: Aligning text on only one side](http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/G169) - [G188: Providing a button on the page to increase line spaces and paragraph spaces](http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/G188) - [G146: Using liquid layout](http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/G146) ( *AND* using measurements that are relative to other measurements in the content) - Most of the advisory techniques dealing with visual presentation are also important for older people, including those dealing with: - Hover - to highlight paragraphs, list items, or table cells - Links - visually distinct links. - Lists - vertical rather than horizontal; expandable bullets; show/hide bullet points. - Spacing - line, paragraph and column spacing. - Text - justification; use of proper case; avoiding italics; default font size. #### [Guideline 3.1 Readable](http://www.w3.org/WAI/WCAG20/quickref/#meaning) {#guideline-3.1-readable .listintro} Making websites that are readable and usable by older people with vision impairments [\[03\]](http://www.w3.org/TR/2008/WD-wai-age-literature-20080514/#whatvision) (or declining cognitive abilities [\[07\]](http://www.w3.org/TR/2008/WD-wai-age-literature-20080514/#whatcog) ) can be enhanced by incorporating many of the [advisory techniques about text presentation](http://www.w3.org/WAI/WCAG20/quickref/Overview.php#meaning-advisory) covering issues such as: - Writing - using the simplest language appropriate for the content, examples, illustrations - Text - justification, line length, italics, case - Links - visually distinct, in-page links - Presentation - pale (non-white) background #### [Guideline 3.2 Predictable](http://www.w3.org/WAI/WCAG20/quickref/#consistent-behavior) {#guideline-3.2-predictable .listintro} This guideline helps users with disabilities by presenting content in a predictable order from Web page to Web page and by making the behavior of functional and interactive components predictable. It is difficult for some users to form an overview of the Web page. Users with vision or cognitive limitations, including older users, may become confused if components appear in different places on different pages. ##### [3.2.5 - Change on Request](http://www.w3.org/WAI/WCAG20/quickref/#consistent-behavior-no-extreme-changes-context) (AAA) {#change-on-request-aaa .listintro style="margin-top:0.2em"} Older people experiencing vision[ [\[03\]](http://www.w3.org/TR/2008/WD-wai-age-literature-20080514/#whatvision)]{.listintro} (and cognitive [\[07\]](http://www.w3.org/TR/2008/WD-wai-age-literature-20080514/#whatcog)) declines, and especially "change blindness" [\[06\]](http://www.w3.org/TR/2008/WD-wai-age-literature-20080514/#elderlyuserscog), will benefit from this success criterion. *--- end impairments and needs groupings option trial ---*

Alternative Success Criteria Rationale Expressions

Examples of different ways of expressing the SC rationale - ‘meeting this criterion will …’ vs. putting the impairment and implications first.

Option 1: Meeting this SC will …

Sensory Characteristics - Success Criterion 1.3.3 (A) {#sensory-characteristics—success-criterion-1.3.3-a .listintro}
Timing adjustable - Success Criterion 2.2.1 (A) {#timing-adjustable—success-criterion-2.2.1-a .listintro}
On Focus - Success Criterion 3.2.1 (A) {#on-focus—success-criterion-3.2.1-a .listintro}

Option 2: Older people experience X with Y implication, so do Z

Sensory Characteristics - Success Criterion 1.3.3 (A) {#sensory-characteristics—success-criterion-1.3.3-a-1 .listintro}
Timing adjustable - Success Criterion 2.2.1 (A) {#timing-adjustable—success-criterion-2.2.1-a-1 .listintro}
On Focus - Success Criterion 3.2.1 (A) {#on-focus—success-criterion-3.2.1-a-1 .listintro}

— end Alternative Success Criteria Rationale Expressions —

 

{#lp}Landing Page for Older Users ----------------------------------- Published: <http://www.w3.org/WAI/older-users> **Purpose:** - to act as an introductory page to the overlap between design for older users and web accessibility - to link to WAI resources that specifically address issues with designing for older users **Audience:** - everyone interested in developing websites that meet the needs of older users **References:** - [EOWG minutes 21 May 2010](http://www.w3.org/2010/05/21-eo-minutes.html) - [EOWG minutes 12 Feb 2010](http://www.w3.org/2010/02/12-eo-minutes.html#item02) - [Feb 2010 version](http://www.w3.org/WAI/EO/Drafts/older-users2010-02Feb-12) **Title considerations (landing page):** - Design for Older Users and Web Accessibility Overlaps - Web Accessibility and Older Users - Designing for Older Users and Web Accessibility Overlaps - Overlaps in Designing for Older Users and Web Accessibility - Web Accessibility and Older People - Web Accessibility and Older People: Existing Guidelines for People with Disabilities Meet the Needs of Older Users - Web Accessibility and Older People: Broadening Access to Older Web Users - Web Accessibility and Older People: Providing Access to Older Web Users - Web Accessibility and Older People: Ensuring Access for Older Web Users - Web Accessibility and Older People: Guidelines and Access for Older Web Users - Web Accessibility and Older People: Meeting the Requirements of Older Web Users - Web Accessibility and Older People: Meeting the Needs of Older Web Users - Web Accessibility and Older People: Guidelines for meeting the Needs of Older Web Users - Web Accessibility and Older People: Resources for meeting the Needs of Ageing Web Users - Web Accessibility and Older People: Best Practices for meeting the Needs of Older Web Users

</div>

Back to Top