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

Many older people require larger text due to declining eyesight, including in form controls.

WCAG 2.0 requirements:

     1.4.4 - Resize text (AA) says "text can be resized without assistive technology up to 200 percent without loss of content or functionality"

     1.4.8 - Visual Presentation (AAA) includes additional requirements on text justification, line spacing, line length, and horizontal scrolling

Example techniques to consider:

     Using relative font-sizes such as percent (C12) or ems (C14) and ensuring text containers resize (C28)

     Providing large fonts by default (future link)

     C17: Scaling form elements which contain text

     Avoiding the use of text in raster images (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

More techniques are listed under 1.4.4 - Resize text and 1.4.8 - Visual Presentation in "How to Meet WCAG 2.0".

Literature review reference: Vision decline with ageing.

Text presentation affects readability for many older people.

WCAG 2.0 requirements:

     1.4.8 - Visual Presentation (AAA) includes requirements on text style, text justification, line spacing, line length, and horizontal scrolling

Example techniques to consider:

     Avoiding fully-aligned text (C19) or centrally aligned text (future link)

     Using readable fonts (future link)

     Using upper and lower case according to the spelling conventions of the text language (future link)

     Avoiding chunks of italic text (future link)

     G188: Providing a button on the page to increase line spaces and paragraph spaces

     Providing sufficient inter-column spacing (future link)

     Avoiding overuse of different styles on individual pages and in sites (future link)

More techniques are listed under 1.4.8 - Visual Presentation in "How to Meet WCAG 2.0".

Literature review references: Vision decline with ageing, Previous approaches to ‘senior friendly’ Web guidelines, and Studies of elderly Web users’ specific disabilities - Vision.

Most older people’s experience changing color perception changes and they loseloss of contrast sensitivity.

WCAG 2.0 requirements:

     1.4.1 - Use of Color (A) requires that color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element

     1.4.3 - Contrast (Minimum) (AA) requires a contrast ratio of at least 4.5:1 for the visual presentation of text and images

     1.4.6 - Contrast (Enhanced) (AAA) requires a higher contrast ratio of at least 7:1 for the visual presentation of text and images

Example techniques to consider:

     G14: Ensuring that information conveyed by color differences is also available in text

     G122: Including a text cue whenever color cues are used

     G182: Ensuring that additional visual cues are available when text color differences are used to convey information [seems sufficiently redundant with G14 yet more complex so possibly not include here?]

     Using a light pastel background rather than a white background behind black text to create sufficient but not extreme contrast (future link)

     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

     G18: Ensuring that a contrast ratio of at least 4.5:1 exists between text (and images of text) and background behind the text [this seems A-number-1 key issue. Maybe put it at the top of the list?]

More techniques are listed under 1.4.1 - Use of Color, 1.4.3 - Contrast (Minimum),[deleted comma. I do like commas before conjunction is list, but don’t need for only two things:-] and 1.4.6 - Contrast (Enhanced) in "How to Meet WCAG 2.0".

Literature review references: Vision decline with ageing, and Studies of elderly Web users’ specific disabilities: vision.

MBecause many older people’s experience hearing or vision decline, and benefit fromthey often need transcripts, captions, and minimal low background sound. [note here you say vision, and elsewhere eyesight]

WCAG 2.0 requirements:

     1.2.1 - Audio-only and Video-only (Prerecorded) (A)

     1.2.2 - Captions (Prerecorded) (A)

     1.2.3 - Audio Description or Media Alternative (Prerecorded video) (A)

     1.2.4 - Captions (Live) (A)

     1.2.5 - Audio Description (Prerecorded video) (AA)

     1.2.7 - Extended Audio Description (Prerecorded video) (AAA)

     1.2.8 - Media Alternative (Prerecorded) (AAA)

     1.2.9 - Audio-only (Live) (AAA)

     1.4.7 - Low or No Background Audio (Prerecorded) (AAA)

Example techniques to consider:

     All transcript, caption, and audio description techniques from the listed success criteria should be considered as appropriate [huh? … why not list the top few like you do on the others?]

     G56: Mixing audio files so that non-speech sounds are at least 20 decibels lower than the speech audio content

More techniques are listed under the success criteria for Guideline 1.2 (Time-based Media) and under 1.4.7 - Low or No Background Audio (Prerecorded) in "How to Meet WCAG 2.0".

Literature review references: Vision decline with ageing and Hearing loss with age.

Some older people use 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 (A) says "a text alternative that serves the equivalent purpose"

     1.3.1 - Info and Relationships (A) says "information, structure, and relationships" to be made available to software [OR] , for example, to text-to-speech software

Example 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

     H44: Using label elements to associate text labels with form controls

     H42: Using h1-h6 to identify headings

More techniques are listed under 1.1.1 - Non-text Content and 1.3.1 - Info and Relationships in "How to Meet WCAG 2.0".

CAPTCHA presents a significant barrier for some people, especially oOlder people with declining eyesight may not be able to discern the characters in CAPTCHA, especially because CAPTCHA often does not increase when users have text sized larger. [audio captcha also extremely difficult, though maybe not worth listing here?]
(CAPTCHA stands for 'Completely Automated Public Turing tests to tell Computers and Humans Apart.') An example of CAPTCHA is: <img src="/WAI/images/captcha.png" alt="the letters 'captcha' difficult to read because skewed on complex background" />

WCAG 2.0 requirements:

     1.1.1 - Non-text Content (A) includes a requirement for alternative CAPTCHAs

Example techniques to consider:

     G143: Providing a text alternative that describes the purpose of the CAPTCHA AND G144: Ensuring that the Web Page contains another CAPTCHA serving the same purpose using a different modality

     Providing more than two modalities of CAPTCHAs (future link)

     Providing access to a human customer service representative who can bypass CAPTCHA (future link)

     Not requiring CAPTCHAs for authorized users (future link)

Literature review reference: Vision decline with ageing.

Many older people rely onneed links to be particularly clear and identifiable links.

WCAG 2.0 requirements:

     2.4.4 - Link Purpose (In Context) (A) requires says [consider changing “requires” to “says” or “states” throughout] that the purpose of a link can be determined from the link text alone, or from the link text together with its surrounding context

     2.4.9 - Link Purpose (Link Only) (AAA) says "a mechanism is available to allow the purpose of each link to be identified from link text alone"

     2.4.7 - Focus Visible (AA) requires a visible keyboard focus indicator (that shows what component on the web page has focus) [from http://www.w3.org/WAI/EO/Drafts/PWD-Use-Web/2009/provisions]

Example techniques to consider:

     G91: Providing link text that describes the purpose of a link

     Limiting the number of links per page (future link)

     Making links visually distinct (future link)

     G195: Using an author-supplied, highly visible focus indicator

     Highlighting a link or control when the mouse hovers over it, or when it receives keyboard focus (future links)

More techniques are listed under 2.4.4 - Link Purpose (In Context), 2.4.9 - Link Purpose (Link Only), and 2.4.7 - Focus Visible in "How to Meet WCAG 2.0".

Literature review reference: Previous approaches to ‘senior friendly’ Web guidelines.

Many older people need navigation to be particularlyrely on clear navigation mechanisms.

WCAG 2.0 requirements:

     2.4.5 - Multiple Ways (AA) says "More than one way is available to locate a Web page within a set of Web pages"

     2.4.8 - Location (AAA) says "Information about the user's location within a set of Web pages is available"

     2.4.2 - Page Titled (A) says "Web pages have titles that describe topic or purpose" [maybe delete? since not a top issues for many older people]

Example techniques to consider:

     G63: Providing a site map

     G161: Providing a search function to help users find content

     G88: Providing descriptive titles for Web pages [maybe delete? since not a top issues for many older people] (to help sSearch- based navigation) [what do you mean? Just for SEO? If so, not strong enough argument to include there I think]

     G65: Providing a breadcrumb trail

     G128: Indicating current location within navigation bars

     Providing a link to the home page or main page (future link)

More techniques are listed under 2.4.5 - Multiple Ways, 2.4.8 - Location and 2.4.2 - Page Titled in "How to Meet WCAG 2.0".

Literature review references: Previous approaches to ‘senior friendly’ Web guidelines and Studies of elderly Web users’ specific disabilities - Cognition.

SFor some older people find it is difficult to use a mouse due to declining vision decline or reduced dexterity.

WCAG 2.0 requirements: [do these relate to keyboard use only? If so, group with next one.]

     2.4.7 - Focus Visible (AA) requires focus indicators to be visible

     3.3.2 - Labels or Instructions (A) requires labels "when content requires user input" says that labels are provided when content requires user input

     1.1.1 - Text Alternatives (A) requires "text alternatives for any non-text content" such as form controls

Example techniques to consider:

     Highlighting a link or control when the mouse hovers over it (future link) [if this is the only one that applies to mouse use (as opposed to keyboard us), I think not worth keeping separate from below]

     G195: Using an author-supplied, highly visible focus indicator

     H44: Using label elements to associate text labels with form controls, (which increases the clickable area for form controls) [ah, I see, this one does as well]

     [Also helpful for increasing clickable area: using real text with relative font size and not images of text…]

More techniques are listed under 2.4.7 - Focus Visible and 3.3.2 - Labels or Instructions in "How to Meet WCAG 2.0".

Literature review references: Motor skill diminishment and Studies of elderly Web users’ specific disabilities - Mobility.

Some older people cannot use a mouse well at all and instead use a keyboard.use a keyboard rather than a mouse for website navigation.[more than for navigation?]

WCAG 2.0 requirements:

     2.1.1 - Keyboard (A) says "the content is operable through a keyboard interface"

     2.1.2 - No Keyboard trap (A) makes sure that keyboard focus "can be moved away from that component using only a keyboard"

     2.1.3 - Keyboard (No Exception) (AAA) says "All functionality of the content is operable through a keyboard interface "

     2.4.1 - Bypass Blocks (A) says "A mechanism is available to bypass blocks of content that are repeated"

     2.4.3 - Focus Order (A) says "components receive focus in an order that preserves meaning and operability"

     2.4.7 - Focus Visible (AA) requires an ability forsays “the "keyboard focus indicator is(to be) visible"

Example techniques to consider:

     Ensuring keyboard control by using H91: Using HTML form controls and links to ensure that users can use the form [with only the keyboard –OR- without the mouse]

     G90: Providing keyboard-triggered event handlers

     G1: Adding a link at the top of each page that goes directly to the main content area

     G59: Placing the interactive elements in an order that follows sequences and relationships within the content

     G195: Using an author-supplied, highly visible focus indicator

     Providing a highly visible highlighting mechanism for links or controls when they receive keyboard focus (future link)

More techniques are listed under various success criteria for Guideline 2.1 - Keyboard Accessible and Guideline 2.4 - Navigable in "How to Meet WCAG 2.0".

Literature review references: Motor skill diminishment and Studies of elderly Web users’ specific disabilities - Mobility.

Some older people are particularly distracted by movement and sounds on web pages.

WCAG 2.0 requirements:

     2.2.2 - Pause, Stop, Hide (A) says "a mechanism for the user to pause, stop, or hide" moving or blinking content

     2.2.4 - Interruptions (AAA) says "Interruptions can be postponed or suppressed"

     1.4.2 - Audio Control (A) says "a mechanism is available to pause or stop the audio"

Example techniques to consider:

     G4: Allowing the content to be paused and restarted from where it was paused

     G11: Creating content that blinks for less than 5 seconds

     Providing the user with a means to stop moving content even if it stops automatically within 5 seconds (future link)

     G76: Providing a mechanism to request an update of the content instead of updating automatically

     G60: Playing a sound that turns off automatically within three seconds

     G171: Playing sounds only on user request

More techniques are listed under 2.2.2 - Pause, Stop, Hide, 2.2.4 - Interruptions, and 1.4.2 - Audio Control in "How to Meet WCAG 2.0".

Literature review references: Cognitive decline with age and Studies of elderly Web users’ specific disabilities - Cognition.

Sit takes some older people longer to may read text and complete transactions more slowly due to declining vision, dexterity, or cognition. [hum, except longer than what? :-]

WCAG 2.0 requirements:

     2.2.1 - Timing Adjustment (A) requires says that users canto be able to turn off, adjust, or extend any time limits

     2.2.3 - No Timing (AAA) says "Timing is not an essential part of the event or activity presented by the content" (except for multimedia or real-time events)

     2.2.2 - Pause, Stop, Hide (A) requires that scrolling content can be paused and that auto updating content can be paused or controlled

Example techniques to consider:

     G4: Allowing the content to be paused and restarted from where it was paused

     G198: Providing a way for the user to turn the time limit off

     SCR16: Providing a script that warns the user a time limit is about to expire AND [consider lowercase (so screen readers don’t assume abbr), and line break here] SCR1: Allowing the user to extend the default time limit

     G4: Allowing the content to be paused and restarted from where it was paused [duplicates first bullet in this list]

More techniques are listed under 2.2.1 - Timing Adjustment, 2.2.3 - No Timing, and 2.2.2 - Pause, Stop, Hide in "How to Meet WCAG 2.0".

Literature review references: Cognitive decline with age and Studies of elderly Web users’ specific disabilities - Cognition.

Providing good page organization is important as many older people read the whole page.[edit]

WCAG 2.0 requirements:

     2.4.6 - Headings and Labels (AA) says "Headings and labels describe topic or purpose"

     2.4.10 - Section Headings (AAA) says "Section headings are used to organize the content"

     1.4.8 - Visual Presentation (AAA) includes techniques to help make text more readable

Example techniques to consider:

     G130: Providing descriptive headings

     G131: Providing descriptive labels

     G141: Organizing a page using headings

     Using vertical (bulleted or numbered) lists rather than inline lists (future link) [not sure this one worth listing?]

More techniques are listed under 2.4.6 - Headings and Labels, 2.4.10 - Section Headings and 1.4.8 - Visual Presentation in "How to Meet WCAG 2.0".

Literature review references: Cognitive decline with age and Previous approaches to ‘senior friendly’ Web guidelines.

Many older people find it particularly difficult to understandcan be overwhelmed by complex sentences, unusual words, and technical jargon.

WCAG 2.0 requirements:

     3.1.3 - Unusual Words (AAA) says "A mechanism is available for identifying specific definitions of words or phrases used in an unusual or restricted way"

     3.1.4 - Abbreviations (AAA) says "A mechanism for identifying the expanded form or meaning of abbreviations is available"

     3.1.5 - Reading Level (AAA) requires providing a version that "does not require reading ability more advanced than the lower secondary education level"

Example techniques to consider:

     Using the clearest and simplest language appropriate for the content (future link)

     G102: Providing the expansion or explanation of an abbreviation

     G153: Making the text easier to read

More techniques are listed under the success criteria for Guideline 3.1 - Readable in "How to Meet WCAG 2.0".

Literature review references: Cognitive decline with age and Previous approaches to ‘senior friendly’ Web guidelines.

Consistent navigation and presentation

Pop-ups and new windows

Page refresh and updates

Instructions and input assistance

Error prevention and recovery for forms

Some older people will be using older browsers that might not be as capable or fault tolerant as current releases.[edit]

WCAG 2.0 requirements:

     4.1.1 - Parsing (A) requires that markup is used correctly according to specification

Example techniques to consider:

     G134: Validating Web pages

     G192: Fully conforming to specifications

More techniques are listed under 4.1.1 - Parsing in "How to Meet WCAG 2.0".