Navigation: W3C Home > WAI Home > WAI-AGE Project > Needs for Older Users > Comparative needs analysis > Detailed analysis

Comparative requirements analysis (detailed) for older Web users
[Editor's DRAFT - 21 August 2008]

Status: This document is a draft. Please send comments to public-comments-wai-age@w3.org (a publicly archived list).

Introduction

This table provides an analysis of the requirements for older users on the Web against the WAI guidelines to identify commonalities and differences. The table only presents requirements identified by one of more authors of the over 150 articles collected for the literature review. Any individual requirement listed below may have been recommended by several authors, or by only one author; a recommendation may have been based on a scientific study or an observation of users. There also may be additional requirements needed in order to satisfy the full range of functional and sensory impairments experienced with ageing. The requirements listed do not necessarily reflect the view of the editor or of W3C.

The following versions of WAI guidelines were used for this analysis:

WCAG 1.0 - WCAG 1.0 W3C Recommendation 5 May 1999
WCAG 2.0 - WCAG 2.0 W3C Candidate Recommendation 30 April 2008
ATAG 1.0 - ATAG 1.0 W3C Recommendation 3 February 2000
ATAG 2.0 - ATAG 2.0 W3C Working Draft 10 March 2008
UAAG 1.0 - UAAG 1.0 W3C Recommendation 17 December 2002

As ATAG 2.0 is designed to support the generation of Web content that meets the requirements of WCAG 2.0, the various ATAG Success Criteria will match the corresponding levels ("A", "AA" and "AAA") of WCAG Success Criteria. For this reason, only ATAG 2.0 high-level principles have been listed for the record.

The tables of collected recommendations for making Web sites better meet the needs of older users have been categorised according to the POUR principles of WCAG 2.0:

Perceivable content recommendations - users must be able to perceive the information being presented
Operable content recommendations - users must be able to operate the interface
Understandable content recommendations - users must be able to understand the information as well as the operation of the user interface
Robust content recommendations - users must be able to access the content as technologies advance
Miscellaneous recommendations - this last table contains recommendations that did not have a corresponding technique to meet WCAG 2.0 Success Criteria

Key to symbols and abbreviations used in the tables

">" means the need is not fully met by the WCAG 2.0 Success Criteria techniques
"=" means the need is fully met by the WCAG 2.0 Success Criteria techniques
"<" means the need is exceeded by the WCAG 2.0 Success Criteria techniques
GL means Guideline
CP means Checkpoint
ST means Sufficient Technique
AT means Advisory Technique
SC means Success Criteria

NOTE: These tables only reflect the recommendations identified in the literature reviewed; other recommendations made be required in order to meet all the needs of older users with ageing-related functional or sensory limitations. Please note the cautions made in the Introduction.

Perceivable

Recommendations identified in the Literature Review:	WCAG 1.0 Checkpoints	WCAG 2.0 Techniques (& Success Criteria)	ATAG 1.0 Guidelines or Checkpoints	ATAG 2.0 Principles	UAAG 1.0 Checkpoints	Comment
Use 12-14pt text size	3.4	> AT (SC 1.4.4)		B1; B2; B3	4.1	@@ Combo of WCAG + UAAG may satisfy this need
Use relative units for text and layout	3.4	= ST (SC 1.4.4; SC 1.4.8)	GL 1	B1; B2; B3	??
Provide text size adjustment link		= ST (SC 1.4.4)		B1; B2; B3
Use a sans serif font		= AT (SC 1.4.8)		B1; B2; B3	4.2
Avoid bold body-text (except for emphasis)		Perceivable				Some authors consider that extra font weight makes large blocks of text harder to read
Avoid underlined text (do use for links)		Perceivable				Some authors suggest that underlining makes large blocks of text harder to read by interfering with the descenders
Avoid text in all capitals (use proper case)		= AT (SC 1.4.8) = AT (GL 3.1)		B1; B2; B3
Left justified text (with L2R scripts)		> AT (SC 1.4.4) = AT (GL 3.1)		B1; B2; B3
Use increased line spacing		= ST (SC 1.4.8)		B1; B2; B3
Provide sufficient (high) contrast	2.2	< ST (SC 1.4.3 & SC 1.4.6)	GL 1	B1; B2; B3	4.3
Avoid blues and greens		> ST (SC 1.4.1) < ST (SC 1.4.3)		B1; B2; B3
Avoid fluorescent colours		Perceivable				Text & objects presented with fluorescent colours can be difficult to focus on with age-impaired vision
Use dark text on light background		= AT (SC 1.4.3 & SC 1.4.6)		B1; B2; B3
Avoid patterned backgrounds		> AT (SC 1.4.3 & SC 1.4.6)		B1; B2; B3	3.1
Use HTML rather than images or multimedia for text-based information	3.1	= ST (SC 1.4.5; SC 1.4.9) = AT (SC 1.4.3; SC 1.4.4; SC 1.4.6; SC 1.4.8; SC 1.4.9)		B1; B2; B3
Provide 'white space' page margins		> AT (SC 1.4.8)		B1; B2; B3
Avoid horizontal scrolling		= ST (SC 1.4.8)		B1; B2; B3	4.1
Do not indicate required form fields with just just an asterisk - use text		= AT (SC 1.4.1)		B1; B2; B3
Ensure links are blue and underlined		> AT (SC 1.4.8) > AT (GL 2.4)		B1; B2; B3	4.3
Ensure links change colour after visit		Perceivable			10.2
Ensure links are visibly different when they have focus		> ST (SC 2.4.7) = AT (SC 1.4.1)		B1; B2; B3	10.2
Combine images and links with the same destination		= ST (SC 1.1.1) = AT (SC 2.4.9)		B1; B2; B3
Present links as lists		= AT (SC 1.4.8)		B1; B2; B3
Clearly separate links	10.5	Perceivable	GL 1
Links are large in size		= AT (SC 1.4.4)		B1; B2; B3
Provide a text equivalent for images	1.1	= ST (SC 1.1.1)	CP 3.4	B1; B2; B3
Provide captions and/or transcripts for video and animations	1.1; 1.4	= ST (SC 1.2.1; SC 1.2.2; SC 1.2.4; SC 1.2.8)	CP 3.1 & 3.5	B1; B2; B3	2.5
Don't use colour alone to portray information	2.1	= ST (SC 1.3.1; SC 1.4.1)	GL 1	B1; B2; B3
Use style sheets for presentation and layout	3.3; 5.3	= ST (SC 1.3.1; SC 1.4.5; SC 1.4.9)	CP 2.2 & 4.5	B1; B2; B3
Provide a linear alternative to pages using table layout	10.3	< ST (SC 1.3.1; SC 2.4.10)	GL 1	B1; B2; B3
Ensure links change colour after visit		Perceivable Operable?			10.2
Clearly separate links	10.5	Perceivable Operable?	GL 1
Provide Previous/Next page links (where appropriate)		Perceivable Operable				mentioned in Note for WCAG 2.0 SC 3.2.4 (e.g. 'go to page 5') Some authors identified that a clear reading path aids comprehension
Make search results visible in normal view-port		Perceivable				Suggested as it provides reinforcement as to why the particular results are provided
Make sure the user notices small page changes/updates		Perceivable				refers to "change blindness" WAI ARIA's 'live regions' may address this requirement

List of Tables

Operable

Recommendations identified in the Literature Review:	WCAG 1.0 Checkpoints	WCAG 2.0 Techniques	ATAG 1.0 Guidelines or Checkpoints	ATAG 2.0 Principles	UAAG 1.0 Checkpoints	Comment
Avoid moving (and scrolling) text	7.3	> ST (SC 2.2.2; SC 2.2.1) > AT (SC 2.2.2)		B1; B2; B3	2.4; 3.3
Use static menus (not fly-out / pull-down)		Operable				Fly-out & pull-down dynamic menus are harder for older people with mobility limitations or new to mouse use to manipulate
Provide clean pages; avoid clutter; avoid irrelevant material to the main content		> AT (GL 2.4)		B1; B2; B3
Ensure links are blue and underlined		> AT (SC 1.4.8) > AT (GL 2.4)		B1; B2; B3	4.3
Ensure links change colour after visit					10.2
Ensure links are visibly different when they have focus		> ST (SC 2.4.7) = AT (SC 1.4.1)		B1; B2; B3	10.2
Combine images and links with the same destination		= ST (SC 1.1.1) = AT (SC 2.4.9)		B1; B2; B3
Provide Previous/Next page links (where appropriate)		Operable				mentioned in note WCAG 2.0 SC 3.2.4 (e.g. 'go to page 5') Some authors identified that a clear reading path aids comprehension
Don't disable the "back" button		Operable			11.5 ??
Provide "breadcrumbs"		= ST (SC 2.4.8)		B1; B2; B3
Provide true home page link on all pages of site		= AT (SC 2.4.8)		B1; B2; B3
Ensure the 'search' function covers whole site		? ST (SC 2.4.5)		B1; B2; B3
Ensure the 'search' function is labeled	10.2	= ST (SC 2.4.6; SC 3.3.2)	GL 1	B1; B2; B3
Avoid blinking content	7.2	> ST (SC 2.2.2)	GL 1	B1; B2; B3
Avoid animations (unless requested)	7.3	> ST (SC 2.2.2)	GL 1	B1; B2; B3	3.2
Do not automatically refresh pages	7.4	= ST (SC 2.2.4)	GL 1	B1; B2; B3	3.5
Use device-independent event handlers	9.3	= ST (SC 2.1.1) = AT (SC 2.1.1)	GL 1	B1; B2; B3
Ensure logical tabbing order	9.4	= ST (SC 2.4.3)	GL 1	B1; B2; B3		@@ check agelight
Provide a linear alternative to pages using table layout	10.3	< ST (SC 1.3.1; SC 2.4.10)	GL 1	B1; B2; B3
Provide clear links	13.1	= ST (SC 2.4.4; SC 2.4.9)	GL 1	B1; B2; B3
Provide a site-map	13.3	= ST (SC 2.4.5; SC 2.4.8)	GL 1	B1; B2; B3
Provide a navigation menu	13.5	?? ST (SC 2.4.5)	GL 1	B1; B2; B3
Use static menus (not fly-out / pull-down)		Operable				Fly-out & pull-down dynamic menus are harder for older people with mobility limitations or new to mouse use to manipulate
If pop-up windows used, then the full message is displayed		Operable				In order that users doesn't have to deal with navigation as well as reading in a situation that is already confusing for some people
Ensure links change colour after visit		Perceivable Operable?			10.2
Clearly separate links	10.5	Perceivable Operable?	GL 1
Provide Previous/Next page links (where appropriate)		Perceivable Operable				mentioned in Note for WCAG 2.0 SC 3.2.4 (e.g. 'go to page 5') Some authors identified that a clear reading path aids comprehension
Don't disable the "back" button		Operable			11.5 ??

List of Tables

Understandable

Recommendations identified in the Literature Review:	WCAG 1.0 Checkpoints	WCAG 2.0 Techniques	ATAG 1.0 Guidelines or Checkpoints	ATAG 2.0 Principles	Comment
Avoid text in all capitals (use proper case)		= AT (SC 1.4.8) = AT (GL 3.1)		B1; B2; B3
Left justified text (with L2R scripts)		> AT (SC 1.4.4) = AT (GL 3.1)		B1; B2; B3
Avoid pop-ups or new windows	10.1	> AT (SC 3.2.2)	GL 1	B1; B2; B3	UAAG 2.0 draft - GL 3.11
If pop-up windows used, then the full message is displayed		Understandable			In order that users doesn't have to deal with navigation as well as reading in a situation that is already confusing for some
Provide Help &/or FAQ's for the site		> ST (SC 3.3.2)		B1; B2; B3	WCAG 2.0 refers to Forms help only
Provide instructions for form completion		= ST (SC 3.3.2)		B1; B2; B3
Provide clear error messages for forms		< ST (SC 3.3.1 & SC 3.3.3) < AT (SC 3.3.1 & SC 3.3.3)		B1; B2; B3
Accommodate misspellings, hyphens and common variations within forms		> ST (SC 3.3.5) > AT (SC 3.3.3)		B1; B2; B3
Provide clear/consistent branding on all pages		> AT (SC 3.2.4)		B1; B2; B3
Provide an "About us" and/or "Contacts" page		> AT (GL 3.1)		B1; B2; B3
Ensure search function is tolerant of misspellings		> ST (SC 3.3.5)		B1; B2; B3	@@ suggested ">" - maybe it should be "="?
Ensure the 'search' function is labeled	10.2	= ST (SC 2.4.6; SC 3.3.2)	GL 1	B1; B2; B3
Use an active voice for writing		> ST (SC 3.1.5) > AT (SC 3.1.5)		B1; B2; B3
Use short sentences and paragraphs	14.1	> ST (SC 3.1.5) > AT (SC 3.1.5)		B1; B2; B3
Provide consistent navigation	13.4; 14.3	= ST (SC 3.2.3)	GL 1	B1; B2; B3
Write clearly with important information at the start	13.8; 14.1	> AT (GL 3.1)	GL 1	B1; B2; B3
Include a glossary (especially for technical terms)	14.1	< ST (SC 3.1.3; SC 3.1.4; SC 3.1.6) < AT (SC 3.1.3)		B1; B2; B3
Only use icons and graphics that are relevant to the topic or that aid comprehension and understanding	14.2	> AT (GL 3.1)		B1; B2; B3	WCAG suggests adding images to aid understanding, rather than restricting them to this use.
Ensure search query is repeated on search results page		Understandable			Suggested so that the users realises that they are on a results page
Group like information	12.3	Understandable?	GL 1

List of Tables

Robust

Recommendations identified in the Literature Review:	WCAG 1.0 Checkpoints	WCAG 2.0 Techniques	ATAG 1.0 Guidelines or Checkpoints	Comment
Use valid code	3.2	= ST (SC 4.1.1)	CP 2.2
Use short pages		Robust??		Recommended to assist users with older or slower equipment and also to minimise scrolling for older users who find mouse user difficult
Avoid making users down load documents (provide material as HTML where appropriate)	11.1	Robust??		Suggested as some older users have an aversion to downloads
Pages should function without scripting support	6.3	Robust??	GL1

List of Tables

Miscellaneous

@@ Miscellaneous recommendations have been placed Tables 1 to 4 (and do not appear in Table 5) if they obviously matched a POUR WCAG 2.0 Principle.

Recommendations identified in the Literature Review:	WCAG 1.0 Checkpoints	WCAG 2.0 Principles	UAAG 1.0 Checkpoints	Comment
@@ search functions	13.7			@@ check checklists

Consider page download speed - create 'small' pages		Not Applicable	UAAG requires an indicator of activity	technical issue related to socioeconomics more than accessibility
Do not require 'double clicks'		Not Applicable		A confusion between software and Web pages?

Undertake user testing	Appendix A	Understanding Conformance		@@ Is this a "robust" principle?

List of Tables

Comparative requirements analysis (detailed) for older Web users [Editor's DRAFT - 21 August 2008]

Page Contents

Introduction

Key to symbols and abbreviations used in the tables

Perceivable

Operable

Understandable

Robust

Miscellaneous

Comparative requirements analysis (detailed) for older Web users
[Editor's DRAFT - 21 August 2008]