• Skip to content
• | To change text size or colors

WAI: Strategies, guidelines, and resources to make the Web accessible to people with disabilities

Navigation: W3C Home > WAI Home > WAI-AGE Project > Recommendations comparison

WAI Guidelines and Older Web Users: Findings from a Literature Review
[Editor's DRAFT - 11 March 2009]

Status: This document is a draft in development, and should not be referenced or quoted under any circumstances.
Please send comments to public-comments-wai-age@w3.org (a publicly archived list).

Introduction

This document compares collected recommendations on designing Web pages to be usable by older people with Web Content Accessibility Guidelines (WCAG) from the Web Accessibility Initiative (WAI). This work is part of the WAI-AGE Project to increase accessibility of the Web for older people as well as for people with disabilities.

The first column in the tables below lists recommendations that were compiled from a thorough Literature Review on Web Accessibility for Older Users. Note that these are not WAI recommendations. Some come from scientific studies and others from casual observations, as described in the literature review.

The second and third columns list related provisions in WCAG from WCAG 1.0 W3C Recommendation 5 May 1999 and WCAG 2.0 Recommendation 11 December 2008. While the most direct relations are listed, many of these are also related to broader provisions such as WCAG 2.0 Success Criteria 1.3.1 Info and Relationships.

The information is loosely grouped under four principles: perceivable, operable, understandable and robust. This rough grouping is only to help organize the information; it is not definitive.

More detailed information is available in Appendix @@ of the Literature Review (Interim link). That appendix includes:

• Notations on whether the recommendations are partially or fully covered in WCAG
• Relationship of the recommendations to WAI's User Agent Accessibility Guidelines (UAAG), which covers Web browsers, media players, and other "user agents"
• Relationship of the recommendations to WAI's Authoring Tool Accessibility Guidelines (ATAG)

Note: "n.a." in a cell means that either no WCAG 1.0 checkpoints were applicable; no WCAG 2.0 success criteria were applicable; or no comments were required

Perceivable

Collected Recommendations:	WCAG 1.0 Checkpoints	WCAG 2.0 Success Criteria &/or Guidelines	Comment
Use 12-14pt text size	3.4	1.4.4 Resize text; 1.4.8 Visual Presentation	Combination of WCAG + UAAG may satisfy this need
Use relative units for text and layout	3.4	1.4.4 Resize text; 1.4.8 Visual Presentation	n.a.
Provide text size adjustment link	n.a.	1.4.4 Resize text	n.a.
Use a sans serif font	n.a.	1.4.8 Visual Presentation	n.a.
Avoid bold body-text (except for emphasis)	n.a.	n.a.	n.a.
Avoid underlined text (do use for links)	n.a.	n.a.	n.a.
Avoid text in all capitals (use proper case)	n.a.	1.4.8 Visual Presentation; 3.1 Readable	n.a.
Left justified text (with L2R scripts)	n.a.	1.3.2 Meaningful Sequence; 1.4.4 Resize text; 1.4.8 Visual Presentation; 3.1 Readable	n.a.
Use increased line spacing	n.a.	1.4.8 Visual Presentation	n.a.
Provide sufficient (high) contrast	2.2	1.4.1 Use of Color; 1.4.3 Contrast (Minimum); 1.4.6 Contrast (Enhanced)	n.a.
Avoid blues and greens with black	n.a.	1.4.1 Use of Color; 1.4.3 Contrast (Minimum)	n.a.
Avoid fluorescent colors	n.a.	n.a.	n.a.
Use dark text on light background	n.a.	1.4.8 Visual Presentation; 1.4.3 Contrast (Minimum); 1.4.6 Contrast (Enhanced)	n.a.
Avoid patterned backgrounds	n.a.	1.4.3 Contrast (Minimum); 1.4.6 Contrast (Enhanced)	n.a.
Use HTML rather than images or multimedia for text-based information	3.1	1.4.3 Contrast (Minimum); 1.4.4 Resize text; 1.4.5 Images of Text; 1.4.6 Contrast (Enhanced); 1.4.8 Visual Presentation; 1.4.9 Images of Text (No Exception)	n.a.
Provide 'white space' page margins	n.a.	1.4.8 Visual Presentation	n.a.
Avoid horizontal scrolling	n.a.	1.4.8 Visual Presentation	n.a.
Do not indicate required form fields with just just an asterisk - use text	n.a.	1.4.1 Use of Color	n.a.
Ensure links are blue and underlined	n.a.	1.4.1 Use of Color; 1.4.8 Visual Presentation; 2.4 Navigable	n.a.
Ensure links change co lour after visit	n.a.	n.a.	n.a.
Ensure links are visibly different when they have focus	n.a.	1.4.1 Use of Color; 2.4.7 Focus Visible	n.a.
Combine images and links with the same destination	n.a.	1.1.1 Non-text Content; 2.4.9 Link Purpose (Link Only)	n.a.
Present links as lists	n.a.	1.4.8 Visual Presentation	n.a.
Clearly separate links	10.5	n.a.	n.a.
Links should be large in size	n.a.	1.4.4 Resize text	n.a.
Provide a text equivalent for images	1.1	1.1.1 Non-text Content	n.a.
Provide captions and/or transcripts for video and animations	1.1; 1.4	1.2.1 Audio-only and Video-only (Prerecorded); 1.2.2 Captions (Prerecorded); 1.2.4 Captions (Live); 1.2.8 Full Text Alternative	n.a.
Don't use co lour alone to portray information	2.1	1.3.1 Info and Relationships; 1.4.1 Use of Color	n.a.
Use style sheets for presentation and layout	3.3; 5.3	1.3.1 Info and Relationships; 1.4.5 Images of Text; 1.4.9 Images of Text (No Exception)	n.a.
Provide a linear alternative to pages using table layout	10.3	1.3.1 Info and Relationships;   2.4.10 Section Headings	n.a.
Make search results visible in normal view-port	n.a.	n.a.	n.a.
Make sure the user notices small page changes/updates	n.a.	n.a.	WAI ARIA's 'live regions' may address this requirement

Page contents

Operable

Collected Recommendations:	WCAG 1.0 Checkpoints	WCAG 2.0 Success Criteria &/or Guidelines	Comment
Avoid moving (and scrolling) text	7.3	2.2.1 Timing Adjustable; 2.2.2 Pause, Stop, Hide	n.a.
Use static menus (not fly-out / pull-down)	n.a.	n.a.	n.a.
Provide clean pages; avoid clutter; avoid irrelevant material to the main content	n.a.	2.4 Navigable	n.a.
Clearly separate links	10.5	n.a.	n.a.
Don't disable the "back" button (don't break the browsers history functionality)	n.a.	n.a.	n.a.
Provide "breadcrumbs"	n.a.	2.4.8 Location	n.a.
Provide true home page link on all pages of site	n.a.	2.4.8 Location	n.a.
Ensure the 'search' function covers whole site	n.a.	2.4.5 Multiple Ways	n.a.
Ensure the 'search' function is labeled	10.2	2.4.6 Headings and Labels; 3.3.2 Labels or Instructions	n.a.
Avoid blinking content	7.2	2.2.2 Pause, Stop, Hide	n.a.
Avoid animations (unless requested)	7.3	2.2.2 Pause, Stop, Hide	n.a.
Do not automatically refresh pages	7.4	2.2.4 Interruptions	n.a.
Use device-independent event handlers	9.3	2.1.1 Keyboard	n.a.
Ensure logical tabbing order	9.4	2.4.3 Focus Order	n.a.
Provide clear links	13.1	2.4.4 Link Purpose (In Context); 2.4.9 Link Purpose (Link Only)	n.a.
Provide a site-map	13.3	2.4.5 Multiple Ways; 2.4.8 Location	n.a.
Provide a navigation menu	13.5	2.4.5 Multiple Ways	n.a.
If pop-up windows used, then the full message is displayed	n.a.	n.a.	n.a.
Undertake user testing	Appendix A	Understanding Conformance	n.a.

Page contents

Understandable

Collected Recommendations:	WCAG 1.0 Checkpoints	WCAG 2.0 Success Criteria &/or Guidelines	Comment
Avoid text in all capitals (use proper case)	n.a.	1.4.8 Visual Presentation; 3.1 Readable	n.a.
Left justified text (with L2R scripts)	n.a.	1.4.4 Resize text; 3.1 Readable	n.a.
Provide Previous/Next page links (where appropriate)	n.a.	n.a.	mentioned in Note for WCAG 2.0 SC 3.2.4 (e.g. 'go to page 5')
Avoid pop-ups or new windows	10.1	3.2.2 On Input	UAAG 2.0 draft - GL 3.11
If pop-up windows used, then the full message is displayed	n.a.	n.a.	n.a.
Provide Help &/or FAQ's for the site	n.a.	3.3.2 Labels or Instructions	WCAG 2.0 refers to Forms help only
Provide instructions for form completion	n.a.	3.3.2 Labels or Instructions	n.a.
Provide clear error messages for forms	n.a.	3.3.1 Error Identification; 3.3.3 Error Suggestion	n.a.
Accommodate misspellings, hyphens and common variations within forms	n.a.	3.3.5 Help; 3.3.3 Error Suggestion	n.a.
Provide clear/consistent branding on all pages	n.a.	3.2.4 Consistent Identification	n.a.
Provide an "About us" and/or "Contacts" page	n.a.	3.1 Readable	n.a.
Ensure search function is tolerant of misspellings	n.a.	3.3.5 Help	n.a.
Ensure the 'search' function is labeled	10.2	2.4.6 Headings and Labels; 3.3.2 Labels or Instructions	n.a.
Use an active voice for writing	n.a.	3.1.5 Reading Level	n.a.
Use short sentences and paragraphs	14.1	3.1.5 Reading Level	n.a.
Use short pages	n.a.	n.a.	n.a.
Provide consistent navigation	13.4; 14.3	3.2.3 Consistent Navigation	n.a.
Write clearly with important information at the start	13.8; 14.1	3.1 Readable	n.a.
Include a glossary (especially for technical terms)	14.1	3.1.3 Unusual Words; 3.1.4 Abbreviations; 3.1.6 Pronunciation	n.a.
Only use icons and graphics that are relevant to the topic or that aid comprehension and understanding	14.2	3.1 Readable	n.a.
Ensure search query is repeated on search results page	n.a.	n.a.	n.a.
Group like information	12.3	n.a.	n.a.

Page contents

Robust

Collected Recommendations:	WCAG 1.0 Checkpoints	WCAG 2.0 Success Criteria &/or Guidelines	Comment
Use valid code	3.2	4.1.1 Parsing	n.a.
Avoid making users down load documents (provide material as HTML where appropriate)	11.1	n.a.	n.a.
Pages should function without scripting support	6.3	n.a.	n.a.
Consider page download speed - create 'small' pages	n.a.	n.a.	Note that UAAG requires an indicator of activity.
Do not require 'double clicks'	n.a.	n.a.	This is primarily not a Web page issue, but an overlap between opening the browser and other software and accessing Web pages in some recommendations.

Page contents

@@ recheck all the recommendations for any additional forms-related or search-related issues

 

File (not necessarily content) last updated on $Date: 2009/03/20 10:52:59 $ by $Author: andrew $

Editor: Andrew Arch (W3C). Developed with the WAI-AGE Task Force and the Web Accessibility Initiative Education and Outreach Working Group (WAI EOWG).

[Contacting WAI] Feedback welcome to wai-eo-editors@w3.org (a publicly archived list).