Www.accessibilityoz.com



Bureau of Meteorology

Developer Factsheet

Content

By: AccessibilityOz

Date: March 2013

Contents

Bureau of Meteorology Developer Factsheet Content 0

Contents 1

Overview 2

Content accessibility principles 2

Impact on users 3

Developer Checklist - Content 5

Level A 5

Level AA 24

Using automated testing tools 29

Introduction 29

Recommended tools 29

Testing content with the Web Developer Toolbar 29

Testing content with WAVE 31

Testing content with OzART 32

The Web Content Accessibility Guidelines 2.0 34

WCAG 2.0 Success Criteria 34

WCAG 2.0 Sufficient Techniques 36

WCAG 2.0 Common Failures 42

Resources 47

Accessibility 47

Tools 47

Further Information 48

AccessibilityOz 48

Overview

Content accessibility principles

Web content accessibility is the ability for a person with a disability to understand and use content presented on a web site, application, intranet, or program. It allows people with disabilities to access information like anyone else; interact with others without being classed as “disabled” and allows them to undertake activities which they may not otherwise be able to do.

Website content accessibility is important to people with the following disabilities:

• Blindness

• Colour-blindness

• Low vision

• Deafness

• Motor impairments

• Cognitive impairments.

The types of content covered by this checklist are: page titles; content i.e. the textual page content; headings and link text. Accessibility principles specific to these types of website content, include but are not limited to:

Page titles

• Page titles should not be missing or empty;

• Page titles should be legible, accurate, unique, concise and descriptive; and

• Page titles should include a consistent reference to the site.

Text content

• Page content is correctly spelt and meaningful;

• Any instructions are device independent and do not depend on location or visual appearance;

• Colour, shape or shading alone is not used to convey information;

• The default language is English, all foreign language has been marked up correctly and the page DOCTYPE is correct;

• Images of text are not used in preference to HTML; and

• Dates are in an unabbreviated, easy to read, format.

Headings

• Headings should not be empty, missing or incorrect;

• Headings should be coded with H1, H2 etc.

• Headings should be at the right level and nested correctly; and

• Headings should be descriptive and concise.

Link text

• Link text should be clear, not capitalised, descriptive and avoid the use of ASCII characters;

• Link text should be device independent i.e. ‘Click here’ is not used; and

• Links should not be empty or broken.

Impact on users

The following is an overview of common accessibility errors in page title, text content, headings and link text and the impact on users with a disability.

Page titles

• Page titles should not be missing or empty.

When the page title is missing or empty the screen reader user does not know what page or site they are on.

• Page titles should be legible, accurate, unique, concise and descriptive.

If the page title is incorrect the screen reader user cannot distinguish or confirm that they have arrived at the page they require.

• Page titles should include a consistent reference to the site.

The site name in the page serves as an added confirmation to the screen reader user of the current site and reassurance that an unexpected change in context has not occurred.

Text content

• Page content is correctly spelt and meaningful.

All content on a site should be correctly spelt and meaningful to minimise confusion to screen reader users and also those with cognitive issues.

• Any instructions are device independent and do not depend on location or visual appearance.

Device dependent instructions imply that functionality is restricted to particular device such as a mouse. Instructions that rely on visual cues alone, such as location or appearance, cannot be interpreted correctly by a user with a visual impairment.

• The default language is English, foreign language has been marked up correctly and the page DOCTYPE is correct.

Screen readers rely on the correct markup of the default language and any foreign language for correct pronunciation.

• Images of text are not used in preference to HTML.

Using images of text restricts the end user – people with low vision may have trouble reading the image text. The use of HTML allows people who require a particular visual presentation of text to be able to make adjustments as needed.

• Dates are in an unabbreviated format.

Screen readers correctly read the date when unabbreviated. If shortened this is often more difficult for the screen reader user to understand.

Headings

• Headings should not be empty, missing or incorrect.

Headings are used by screen reader users as a key element to guide their use of the page – empty, missing or incorrect headings can be misleading.

• Headings should be coded with H1, H2 etc. should be at the right level and nested correctly.

Headings are used by screen reader users to navigate a page and get an idea of relative importance of the content.

• Headings should be descriptive and concise.

Headings are used by screen reader and magnifier users to scan the page and get an overview idea of the content contained. Descriptive and concise headings enable both visually impaired and other users to do this.

Link text

• Link text should be clear, descriptive, not capitalised and avoid the use of ASCII characters.

Screen readers read out each letter of any capitalised word as an abbreviation and are not able to interpret ASCII characters.

• Link text should be device independent.

Device dependent instructions imply that functionality is restricted to a particular device such as a mouse.

Developer Checklist - Content

The following checklists are intended to guide developers on the implementation of success criterion for page titles, text content, headings and links. The checklists should be used during the development phase to ensure WCAG 2.0 compliance of all content on the site and should form part of the unit testing phase undergone by developers when updating or creating new content or functionality.

Level A

Page title

|Ref |Requirement |Details |Corre|Incorrect code |Pass | |PGT_A1 |

| | | |ct | | | | |

| | | |code | | | | |

|PGT_A2 |Page title should be present. |Page title must not be empty |⎫ |Bureau of Meteorology - Home|⎦ | | |

| | | | |Page | | | |

|PGT_A3i |Page title content is correct. |Page title is legible |⎫ |Bureau of Meteorology - Home|⎦ |BureauOfMeteorology - | |

| | | | |Page | |HomePage | |

|PGT_A3ii | |Page title is accurate |⎫ |Bureau of Meteorology - Home|⎦ |Burea of Metorology - Home | |

| | | | |Page | |Pg | |

|PGT_A3iii | |Page title is unique |⎫ |Bureau of Meteorology - Home|⎦ |Bureau of | |

| | | | |Page | |Meteorology (all pages) | |

|PGT_A3iv | |Page title is concise |⎫ | Coastal Waters Wind Warning|⎦ | Australian Government | |

| | | | |- Bureau of Meteorology | |Bureau of Meteorology Victoria - | |

| | | | | | |Coastal Waters Wind Warning for | |

| | | | | | |Victorian waters between Mallacoota| |

| | | | | | |and 60nm east of Gabo Island - | |

| | | | | | |Bureau of Meteorology | |

| | | | | | | | |

|PGT_A3v | |Page title is descriptive |⎫ |Bureau of Meteorology - |⎦ |Bureau - Glossary of | |

| | | | |Glossary of Terms - H | |Terms | |

|PGT_A3vi | |Page title does not include ASCII characters (punctuation |⎫ | Bureau of Meteorology - |⎦ |River Height data for Dawson| |

| | |excepted) | |River Height data for Dawson at | |at Utopia Downs * | |

| | | | |Utopia Downs | | | |

|PGT_A4i |Page title references the site |Page titles include a site reference |⎫ |Bureau of Meteorology - |⎦ |Climate information | |

| | | | |Climate information | | | |

|PGT_A4ii | |Site is referenced consistently across all page titles |⎫ |Bureau of Meteorology - Home|⎦ |Bureau of Meteorology - Home| |

| | | | |Page | |Page | |

| | | | | | | | |

| | | | |Bureau of Meteorology - | |Water Information: Bureau of| |

| | | | |Water Information | |Meteorology | |

| | | | | | | | |

| | | | |Bureau of Meteorology - | | | |

| | | | |Glossary of Terms - H | |Bureau - Glossary of | |

| | | | |Bureau of Meteorology – | |Terms | |

| | | | |Climate information | | | |

| | | | | | |BOM - Climate information | |

| | | | | | | | |

Text content

|Ref |Requirement |Details |Corre|Incorrect code |Pass | |TXT_A1i |

| | | |ct | | | | |

| | | |code | | | | |

| | | |⎫ |… use the navigation titled |⎦ |… use the navigation on the left to| |

| | | | |‘Locations’ to access… | |access… | |

| | | |⎫ |… use the Next arrow to go forward |⎦ |… use the arrow on the right to go | |

| | | | |and the Previous arrow to go back. | |forward and the arrow on the left | |

| | | | | | |to go back. | |

|TXT_A1ii | |Instructions do not refer to device-dependent handlers |⎫ |Select the station |⎦ |Click station | |

| | | | |name for the corresponding| |names to link to | |

| | | | |'Latest 72 hours' of | |corresponding 'Latest 72 hours' of | |

| | | | |observations. | |observations. | |

|TXT_A2i |Content is legible |Pages do not contain spelling mistakes |⎫ |…strength (sustained winds…… |⎦ |…strength (sustand winds… | |

|TXT_A2ii | |Content is meaningful when linearised |⎫ |[pic] |⎦ |[pic] | |

| | | | | | | | |

| | | | | | |Linearised: | |

| | | | | | |Sydney Melbourne Brisbane Perth | |

| | | | | | |28° 26° 30° 26° | |

| | | | | | |Mostly Mostly Mostly A little | |

| | | | | | |sunny. sunny. fine, drizzle. | |

| | | | | | |early | |

| | | | | | |shower | |

|TXT_A2iii | |Dates are in a friendly format |⎫ |Issued: 14th |⎦ |Issued: 141112 09:00:00 | |

| | | | |November 2012, 9am | | | |

| | | | | | | | |

| | | | |Issued: 14 Nov | | | |

| | | | |12 | | | |

|TXT_A2iv | |Text is complete i.e. not cut off mid-word or mid-sentence|⎫ |"The Great Barrier Reef, like|⎦ |"The Great Barrier Reef, like | |

| | | | |all coral reef ecosystems around | |all coral reef ecosystems around | |

| | | | |the world, is at risk from a range | |the world, is at risk from a range | |

| | | | |of threats including coastal | |of threats including coa…” | |

| | | | |development, climate change, | | | |

| | | | |floods, cyclones and land | | | |

| | | | |run-off.” | | | |

|TXT_A2v | |Information is not conveyed with colour alone |⎫ |…(that is, in deciles 8 or 9 and |⎦ |…indicated in blue on the map)… | |

| | | | |indicated in blue on the map)… | | | |

|TXT_A2vi | |ASCII characters are not used to convey information |⎫ |Note: Averages may change when |⎦ |*averages may change when the | |

| | |(punctuation excepted) | |the dataset is updated. | |dataset is updated. | |

|TXT_A2vii | |Shading is not used to convey information |⎫ |…the first table lists areas |⎦ |… shaded table rows indicate areas | |

| | | | |experiencing extreme weather | |experiencing extreme weather | |

| | | | |conditions, the second table… | |conditions… | |

|TXT_A3i |Content coding is correct |ASCII characters or number superscripts should be replaced|⎫ |…when the UV |⎦ |…when the UV Index forecast is 3 or| |

| | |by links | |Index forecast is 3 or above, a| |above*, a level… | |

| | | | |level… | | | |

|TXT_A3ii | |Pages specify a valid DOCTYPE. |⎫ | | | | |

Headings

|Ref |Requirement |Details |Corre|Incorrect code |Pass | |HED_A1i |

| | | |ct | | | | |

| | | |code | | | | |

|HED_A2i |Headings are coded correctly. |Headings are coded using H1, H2, etc. |⎫ |About the new Bureau of |⎦ |About the new Bureau| |

| | | | | | |of Meteorology homepage | |

| | | | | | | | |

| | | | | | | | |

|HED_A2ii | |Headings are nested properly |⎫ |About the new Bureau of |⎦ |About the new Bureau of | |

| | | | |Meteorology home page | |Meteorology home page | |

| | | | |Purpose of the new home page | |Purpose of the new home page | |

| | | | |design | |design | |

| | | | |Content overview | |Content overview | |

|HED_A2iii | |Heading levels are correct |⎫ |Changes District Forecast |⎦ |Changes District Forecast | |

| | | | |Boundaries | |Boundaries | |

| | | | |…etc… | |…etc… | |

| | | | | | | | |

| | | | |NSW | |NSW | |

| | | | |VIC | |VIC | |

| | | | |ACT | |ACT | |

| | | | |QLD | |QLD | |

| | | | |WA | |WA | |

| | | | |SA | |SA | |

| | | | |NT | |NT | |

| | | | |TAS | |TAS | |

| | | | |… | |… | |

|HED_A2iv | |Headings should not have additional style sheet classes |⎫ |Forecast for Thursday |⎦ |Forecast for Thursday | |

|HED_A2v | |Hidden structural labels are not coded as headings |⎫ |Main |⎦ |Main | |

| | | | |Navigation | |Navigation | |

|HED_A2vi | |Site title is not used as a heading on all pages |⎫ | | |

|HED_A2vii | |Headings are correct when style sheets are disabled |⎫ |Latest Weather |⎦ |Heading content is changed by the | |

| | | | | | |CSS | |

| | | | | | | latest-weather | |

| | | | | | | | |

|HED_A3i |Heading content is appropriate |Headings are correctly spelt |⎫ |Changes to Weather District |⎦ |Changes to Wether Distrikt | |

| | | | |Boundaries | |Forecasts | |

|HED_A3ii | |Headings are concise |⎫ |Agricultural Observations |⎦ |Agricultural Observations | |

| | | | |Bulletins | |Bulletins are now available for all| |

| | | | | | |States and Territories as at 30 | |

| | | | | | |June 2004. | |

|HED_A3iii | |Headings are not empty |⎫ |Changes to NSW District |⎦ | | |

| | | | |Forecast Boundaries | | | |

|HED_A3iv | |Headings are descriptive |⎫ |Guidelines for Contributory |⎦ |Text | |

| | | | |Text | | | |

|HED_A3v | |Headings are not capitalised |⎫ |Monthly Weather Summary, ACT |⎦ |MONTHLY WEATHER SUMMARY, ACT | |

| | | | |Meteorological Office | |METEOROLOGICAL OFFICE | |

Link Text

|Ref |Requirement |Details |Corre|Incorrect code |Pass | |LNK_A1i |

| | | |ct | | | | |

| | | |code | | | | |

|TXT_AA2 | |Foreign language [in page content] is marked up with the LANG| |…remainder of 2012 and early 2013, | |…remainder of 2012 and early | |

| | |attribute. | |with one model suggesting weak | |2013, with one model suggesting | |

| | | | |El Niño | |weak El Niño | |

| | | | |conditions remain possible over the | |conditions remain possible over | |

| | | | |austral summer…. | |the austral summer… | |

Headings

|Ref |Requirement |Details |Corre|Incorrect code |Pass | |HED_AA1 |

| | | |ct | | | | |

| | | |code | | | | |

Link Text

|Ref |Requirement |Details |Corre|Incorrect code |Pass | |LNK_AA1i |

| | | |ct | | | | |

| | | |code | | | | |

|LNK_AA1ii | |Alphabetised links are consistent |⎫ |Alphabetised links are coded in the |⎦ |Different presentation of | |

| | | | |same way across the site | |alphabetised links is used in | |

| | | | |[pic] | |different areas of the site | |

| | | | | | |[pic] | |

| | | | | | |or | |

| | | | | | |[pic] | |

| | | | | | |or | |

| | | | | | |[pic] | |

| | | | | | |or | |

| | | | | | |[pic] | |

|LNK_AA2i |Presentation |Link text colour contrast is sufficient |⎫ |For colour contrast requirements |⎦ |[pic] | |

| | | | |refer | | | |

| | | | | | | |

| | | | |AG20/visual-audio-contrast-contrast.h| | | |

| | | | |tml | | | |

|LNK_AA2ii | |In-line link formatting is consistent |⎫ |[pic] |⎦ |[pic] | |

|LNK_AA2iii | |Back to top links are consistent |⎫ |One presentation is used across the |⎦ |Inconsistent presentation | |

| | | | |site | |back to top | |

| | | | | | | | |

| | | | |Back to top | | top | |

| | | | | | | | |

| | | | | | | ^TOP | |

Using automated testing tools

Introduction

Automated testing tools are useful in assisting content managers and web developers with the identification of accessibility issues and errors of a website.

These tools are able to perform ‘machine-operable’ testing only, and should be used as a companion alongside human site review and testing.

The following testing tool information is provided as a guide only and is not an exhaustive list.

Recommended tools

The following testing tools are recommended as the most suitable, based on volume of pages being tested:

|Tool |Volume of pages |Type of tool |

|Web Developer Toolbar |Single pages. |Free browser extension for Firefox or Chrome. |

|WAVE |Single pages or small section of |Free online tool – can be used online or download the |

| |pages. |toolbar. |

|OzART |Large section of pages or entire |Online reporting tool – produces error category specific |

| |website. |reports, reduces time spent manually inspecting single web |

| | |pages. |

NB: In some instances only one tool may be suitable regardless of the volume of pages to be tested. In addition, if no tool is suitable a manual site review will be required.

Testing content with the Web Developer Toolbar

The following content references are requirements from the Checklist.

|Page title |

|Automatic |Manual required |Not assessed |

|None |PGT_A1 |N/A – all page title issues can be |

| |PGT_A2 |identified using the Web Developer |

| |PGT_A3i |Toolbar, however each page must be tested|

| |PGT_A3ii |individually and manually |

| |PGT_A3iii | |

| |PGT_A3iv | |

| |PGT_A3v | |

| |PGT_A3vi | |

| |PGT_A4i | |

| |PGT_A4ii | |

|Text Content |

|Automatic |Manual required |Not assessed |

|TXT_A3ii |TXT_A2ii |TXT_A1i |

| |TXT_A2v |TXT_A1ii |

| |TXT_A2vii |TXT_A2i |

| |TXT_A3i |TXT_A2iii |

| |TXT_AA1 |TXT_A2iv |

| |TXT_AA2 |TXT_A2vi |

|Headings |

|Automatic |Manual required |Not assessed |

|HED_A1i |HED_A1iii |HED_A1ii |

| |HED_A2i | |

| |HED_A2ii | |

| |HED_A2iii | |

| |HED_A2iv | |

| |HED_A2v | |

| |HED_A2vi | |

| |HED_A2vii | |

| |HED_A3i | |

| |HED_A3ii | |

| |HED_A3iii | |

| |HED_A3iv | |

| |HED_A3v | |

| |HED_AA1 | |

|Link Text |

|Automatic |Manual required |Not assessed |

|None |LNK_A1i |LNK_A2i |

| |LNK_A1ii |LNK_A2ii |

| |LNK_A1iii | |

| |LNK_A1iv | |

| |LNK_A1v | |

| |LNK_A1vi | |

| |LNK_A2iii | |

| |LNK_A2iv | |

| |LNK_A3i | |

| |LNK_A3ii | |

| |LNK_A3iii | |

| |LNK_A3iv | |

| |LNK_A3v | |

| |LNK_A3vi | |

| |LNK_A4i | |

| |LNK_A4ii | |

| |LNK_A5 | |

| |LNK_A6 | |

| |LNK_AA1i | |

| |LNK_AA1ii | |

| |LNK_AA2i | |

| |LNK_AA2ii | |

| |LNK_AA2iii | |

Testing content with WAVE

The following content references are requirements from the Checklist.

|Page title |

|Automatic |Manual required |Not assessed |

|PGT_A1 |PGT_A3i |N/A – all page title issues can be |

|PGT_A2 |PGT_A3ii |identified using WAVE, however each page |

| |PGT_A3iii |must be checked individually |

| |PGT_A3iv | |

| |PGT_A3v | |

| |PGT_A3vi | |

| |PGT_A4i | |

| |PGT_A4ii | |

|Text Content |

|Automatic |Manual required |Not assessed |

|TXT_A3ii |TXT_A2ii |TXT_A1i |

| |TXT_A2v |TXT_A1ii |

| |TXT_A2vii |TXT_A2i |

| |TXT_AA1 |TXT_A2iii |

| |TXT_AA2 |TXT_A2iv |

| | |TXT_A2vi |

| | |TXT_A3i |

|Headings |

|Automatic |Manual required |Not assessed |

|HED_A1i |HED_A1iii |HED_A1ii |

|HED_A3iii |HED_A2ii |*HED_A2i |

| |HED_A2iii |HED_A2vii |

| |HED_A2iv |HED_AA1 |

| |HED_A2v | |

| |HED_A2vi | |

| |HED_A3i | |

| |HED_A3ii | |

| |HED_A3iv | |

| |HED_A3v | |

|Link Text |

|Automatic |Manual required |Not assessed |

|LNK_A2iii |LNK_A1ii |LNK_A2i |

|LNK_A2iv |LNK_A1iii |LNK_A2ii |

|LNK_A3iii |LNK_A1iv |LNK_A5 |

|LNK_A3v |LNK_A1v |LNK_AA2i |

|LNK_A3vi |LNK_A1i |LNK_AA2ii |

| |LNK_A1vi | |

| |LNK_A3i | |

| |LNK_A3ii | |

| |LNK_A3iv | |

| |LNK_A4i | |

| |LNK_A4ii | |

| |LNK_A6 | |

| |LNK_AA1i | |

| |LNK_AA1ii | |

| |LNK_AA2iii | |

* WAVE does provide some indication of potential failures of this requirement

Testing content with OzART

The following content references are requirements from the Checklist.

|Page title |

|Automatic |Manual required |Not assessed |

|PGT_A1 |PGT_A3i |N/A – all page title issues can be |

|PGT_A2 |PGT_A3ii |identified using OzART |

|PGT_A3iv |PGT_A3iii | |

|PGT_A3vi |PGT_A3v | |

| |PGT_A4i | |

| |PGT_A4ii | |

|Text Content |

|Automatic |Manual required |Not assessed |

|TXT_A3ii |TXT_A1i |TXT_A2ii |

| |TXT_A1ii |TXT_A2iv |

| |TXT_A2i |TXT_A2vii |

| |TXT_A2iii | |

| |TXT_A2v | |

| |TXT_A2vi | |

| |TXT_A3i | |

| |TXT_AA1 | |

| |TXT_AA2 | |

|Headings |

|Automatic |Manual required |Not assessed |

|HED_A1i |HED_A2iii |HED_A1ii |

|HED_A1iii |HED_A2v |HED_A2i |

|HED_A2ii |HED_A2vi |HED_A2vii |

|HED_A2iv |HED_A3i |HED_AA1 |

|HED_A3ii |HED_A3iv | |

|HED_A3iii | | |

|HED_A3v | | |

|Link Text |

|Automatic |Manual required |Not assessed |

|LNK_A1ii |LNK_A1i |LNK_A5 |

|LNK_A1iii |LNK_A1vi |LNK_AA2i |

|LNK_A1iv |LNK_A2i |LNK_AA2ii |

|LNK_A1v |LNK_A2ii | |

|LNK_A2iii |LNK_A3i | |

|LNK_A2iv |LNK_A3ii | |

|LNK_A3v |LNK_A3iii | |

|LNK_A6 |LNK_A3iv | |

| |LNK_A3vi | |

| |LNK_A4i | |

| |LNK_A4ii | |

| |LNK_AA1i | |

| |LNK_AA1ii | |

| |LNK_AA2iii | |

* OzART does provide some indication of potential failures of this requirement

The Web Content Accessibility Guidelines 2.0

WCAG 2.0 Success Criteria

The Web Content Accessibility Guidelines Success Criterion relevant to the accessibility of page titles, text content, headings and link text are:-

Page Title

|SC |Description |

|2.4.2 |Page Titled: Web pages have titles that describe topic or purpose.(Level A) |

Copyright © W3C 11 December 2008 World Wide Web Consortium [Status: Recommendation]

Text content

|SC |Description |

|1.3.1 |Info and Relationships: Information, structure, and relationships conveyed through presentation can be |

| |programmatically determined or are available in text. (Level A) |

|1.3.2 |Meaningful Sequence: When the sequence in which content is presented affects its meaning, a correct reading |

| |sequence can be programmatically determined. (Level A) |

|1.3.3 |Sensory Characteristics: Instructions provided for understanding and operating content do not rely solely on |

| |sensory characteristics of components such as shape, size, visual location, orientation, or sound. (Level A) |

|1.4.1 |Use of Color: Color is not used as the only visual means of conveying information, indicating an action, |

| |prompting a response, or distinguishing a visual element. (Level A) |

|1.4.5 |Images of Text: If the technologies being used can achieve the visual presentation, text is used to convey |

| |information rather than images of text except for the following: (Level AA) |

| |Customizable: The image of text can be visually customized to the user's requirements; |

| |Essential: A particular presentation of text is essential to the information being conveyed. |

| |Note: Logotypes (text that is part of a logo or brand name) are considered essential. |

|2.1.1 |Keyboard: All functionality of the content is operable through a keyboard interface without requiring specific |

| |timings for individual keystrokes, except where the underlying function requires input that depends on the path |

| |of the user's movement and not just the endpoints. (Level A) |

|3.1.1 |Language of Page: The default human language of each Web page can be programmatically determined. (Level A) |

|3.1.2 |Language of Parts: The human language of each passage or phrase in the content can be programmatically |

| |determined except for proper names, technical terms, words of indeterminate language, and words or phrases that |

| |have become part of the vernacular of the immediately surrounding text. (Level AA) |

|3.2.4 |Consistent Identification: Components that have the same functionality within a set of Web pages are identified |

| |consistently. (Level AA) |

Copyright © W3C 11 December 2008 World Wide Web Consortium [Status: Recommendation]

Headings

|SC |Description |

|1.3.1 |Info and Relationships: Information, structure, and relationships conveyed through presentation can be |

| |programmatically determined or are available in text. (Level A) |

|2.4.6 |Headings and Labels: Headings and labels describe topic or purpose. (Level AA) |

Copyright © W3C 11 December 2008 World Wide Web Consortium [Status: Recommendation]

Link text

|SC |Description |

|1.1.1 |Non-text Content: All non-text content that is presented to the user has a text alternative that serves the |

| |equivalent purpose, except for the situations listed below. (Level A) |

| |Controls, Input: If non-text content is a control or accepts user input, then it has a name that describes its |

| |purpose. (Refer to Guideline 4.1 for additional requirements for controls and content that accepts user input.) |

| |Test: If non-text content is a test or exercise that would be invalid if presented in text, then text |

| |alternatives at least provide descriptive identification of the non-text content. |

| |Decoration, Formatting, Invisible: If non-text content is pure decoration, is used only for visual formatting, |

| |or is not presented to users, then it is implemented in a way that it can be ignored by assistive technology. |

|1.3.1 |Info and Relationships: Information, structure, and relationships conveyed through presentation can be |

| |programmatically determined or are available in text. (Level A) |

|1.4.3 |Contrast (Minimum): The visual presentation of text and images of text has a contrast ratio of at least 4.5:1, |

| |except for the following: (Level AA) |

| |Large Text: Large-scale text and images of large-scale text have a contrast ratio of at least 3:1; |

| |Incidental: Text or images of text that are part of an inactive user interface component, that are pure |

| |decoration, that are not visible to anyone, or that are part of a picture that contains significant other visual|

| |content, have no contrast requirement. |

| |Logotypes: Text that is part of a logo or brand name has no minimum contrast requirement. |

|2.1.1 |Keyboard: All functionality of the content is operable through a keyboard interface without requiring specific |

| |timings for individual keystrokes, except where the underlying function requires input that depends on the path |

| |of the user's movement and not just the endpoints. (Level A) |

|2.4.4 |Link Purpose (In Context): The purpose of each link can be determined from the link text alone or from the link |

| |text together with its programmatically determined link context, except where the purpose of the link would be |

| |ambiguous to users in general. (Level A) |

|2.4.5 |Multiple Ways: More than one way is available to locate a Web page within a set of Web pages except where the |

| |Web Page is the result of, or a step in, a process. (Level AA) |

|2.4.7 |Focus Visible: Any keyboard operable user interface has a mode of operation where the keyboard focus indicator |

| |is visible. (Level AA) |

|3.1.1 |Language of Page: The default human language of each Web page can be programmatically determined. (Level A) |

|3.2.4 |Consistent Identification: Components that have the same functionality within a set of Web pages are identified |

| |consistently. (Level AA) |

Copyright © W3C 11 December 2008 World Wide Web Consortium [Status: Recommendation]

The relevant guidelines are detailed in the website manager factsheet.

WCAG 2.0 Sufficient Techniques

For each of the guidelines and success criteria in WCAG 2.0 there are a wide variety of techniques. The techniques fall into two categories:

Sufficient techniques: techniques or a combination of techniques that are sufficient for meeting the success criteria.

Advisory techniques: techniques that should be considered (where relevant) to make content more accessible. The advisory techniques go beyond what is required by the individual success criteria and are not covered by these factsheets.

Page title

|SC |Description |

|2.4.2 |G88: Providing descriptive titles for Web pages AND associating a title with a Web page using the following |

| |technique: |

| |H25: Providing a title using the title element (HTML) |

Copyright © W3C 11 December 2008 World Wide Web Consortium [Status: Recommendation]

Text content

|SC |Description |

|1.3.1 |G115: Using semantic elements to mark up structure AND H49: Using semantic markup to mark emphasized or special|

| |text (HTML) |

| |G117: Using text to convey information that is conveyed by variations in presentation of text |

| |G140: Separating information and structure from presentation to enable different presentations |

| |Making information and relationships conveyed through presentation programmatically determinable using the |

| |following techniques: |

| |G138: Using semantic markup whenever color cues are used |

| |H48: Using ol, ul and dl for lists or groups of links (HTML) |

| |G117: Using text to convey information that is conveyed by variations in presentation of text |

| |Making information and relationships conveyed through presentation programmatically determinable or available |

| |in text using the following techniques: |

| |T1: Using standard text formatting conventions for paragraphs (Text) |

| |T2: Using standard text formatting conventions for lists (Text) |

| |T3: Using standard text formatting conventions for headings (Text) |

|1.3.2 |G57: Ordering the content in a meaningful sequence for all the content in the Web page |

| |Marking sequences in the content as meaningful using one of the following techniques AND G57: Ordering the |

| |content in a meaningful sequence for those sequences |

| |H34: Using a Unicode right-to-left mark (RLM) or left-to-right mark (LRM) to mix text direction inline (HTML) |

| |H56: Using the dir attribute on an inline element to resolve problems with nested directional runs (HTML) |

| |C6: Positioning content based on structural markup (CSS) |

| |C8: Using CSS letter-spacing to control spacing within a word (CSS) |

| |C27: Making the DOM order match the visual order (CSS) |

|1.3.3 |G96: Providing textual identification of items that otherwise rely only on sensory information to be understood|

|1.4.1 |Situation A: If the color of particular words, backgrounds, or other content is used to indicate information: |

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

| |H92: Including a text cue for colored form control labels (HTML) |

| |G182: Ensuring that additional visual cues are available when text color differences are used to convey |

| |information |

| |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 |

| |Situation B: If color is used within an image to convey information: |

| |G111: Using color and pattern |

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

|1.4.5 |C22: Using CSS to control visual presentation of text (CSS) |

| | |

| |C30: Using CSS to replace text with images of text and providing user interface controls to switch (CSS) |

| | |

| |G140: Separating information and structure from presentation to enable different presentations |

|2.1.1 |G202: Ensuring keyboard control for all functionality |

|3.1.1 |H57: Using language attributes on the html element (HTML) |

|3.1.2 |H58: Using language attributes to identify changes in the human language (HTML) |

|3.2.4 |G197: Using labels, names, and text alternatives consistently for content that has the same functionality AND |

| |following the sufficient techniques for Success Criterion 1.1.1 and sufficient techniques for Success Criterion|

| |4.1.2 for providing labels, names, and text alternatives. |

Copyright © W3C 11 December 2008 World Wide Web Consortium [Status: Recommendation]

Headings

|SC |Description |

|1.3.1 |G115: Using semantic elements to mark up structure |

| |Making information and relationships conveyed through presentation programmatically determinable by using the |

| |following technique: |

| |H42: Using h1-h6 to identify headings (HTML) |

|2.4.6 |G130: Providing descriptive headings |

| |G131: Providing descriptive labels |

| |Note: Headings and labels must be programmatically determined, per Success Criterion 1.3.1 . |

Copyright © W3C 11 December 2008 World Wide Web Consortium [Status: Recommendation]

Link text

|SC |Description |

|1.1.1 |H67: Using null alt text and no title attribute on img elements for images that AT should ignore (HTML) |

| |H2: Combining adjacent image and text links for the same resource (HTML) |

| |H86: Providing text alternatives for ASCII art, emoticons, and leetspeak (HTML) |

| |H30: Providing link text that describes the purpose of a link for anchor elements (HTML) |

| |Note: See Understanding Success Criterion 2.4.4 Link Purpose (In Context). |

| |G196: Using a text alternative on one item within a group of images that describes all items in the group |

|1.3.1 |G115: Using semantic elements to mark up structure AND H49: Using semantic markup to mark emphasized or special|

| |text (HTML) |

| |G117: Using text to convey information that is conveyed by variations in presentation of text |

| |G140: Separating information and structure from presentation to enable different presentations |

| |Making information and relationships conveyed through presentation programmatically determinable using the |

| |following techniques: |

| |H48: Using ol, ul and dl for lists or groups of links (HTML) |

|1.4.3 |Situation A: text is less than 18 point if not bold and less than 14 point if bold |

| |G18: Ensuring that a contrast ratio of at least 4.5:1 exists between text (and images of text) and background |

| |behind the text |

| |G148: Not specifying background color, not specifying text color, and not using technology features that change|

| |those defaults |

| |Situation B: text is at least 18 point if not bold and at least 14 point if bold |

| |G145: Ensuring that a contrast ratio of at least 3:1 exists between text (and images of text) and background |

| |behind the text |

| |G148: Not specifying background color, not specifying text color, and not using technology features that change|

| |those defaults |

|2.1.1 |G202: Ensuring keyboard control for all functionality |

| |Ensuring keyboard control by using one of the following techniques. |

| |H91: Using HTML form controls and links (HTML) |

| |G90: Providing keyboard-triggered event handlers using one of the following techniques: |

| |SCR20: Using both keyboard and other device-specific functions (Scripting) |

| |SCR35: Making actions keyboard accessible by using the onclick event of anchors and buttons (Scripting) |

| |SCR2: Using redundant keyboard and mouse event handlers (Scripting) |

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

| |H30: Providing link text that describes the purpose of a link for anchor elements (HTML) |

| |G53: Identifying the purpose of a link using link text combined with the text of the enclosing sentence |

| |Providing a supplemental description of the purpose of a link using one of the following techniques: |

| |H33: Supplementing link text with the title attribute (HTML) |

| |C7: Using CSS to hide a portion of the link text (CSS) |

| |Identifying the purpose of a link using link text combined with programmatically determined link context using |

| |one of the following techniques: |

| |H77: Identifying the purpose of a link using link text combined with its enclosing list item (HTML) |

| |H78: Identifying the purpose of a link using link text combined with its enclosing paragraph (HTML) |

| |H79: Identifying the purpose of a link using link text combined with its enclosing table cell and associated |

| |table headings (HTML) |

| |H80: Identifying the purpose of a link using link text combined with the preceding heading element (HTML) |

| |H81: Identifying the purpose of a link in a nested list using link text combined with the parent list item |

| |under which the list is nested (HTML) |

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

|2.4.5 |G125: Providing links to navigate to related Web pages |

| |G63: Providing a site map |

| |G126: Providing a list of links to all other Web pages |

| |G185: Linking to all of the pages on the site from the home page |

|2.4.7 |G149: Using user interface components that are highlighted by the user agent when they receive focus |

| |C15: Using CSS to change the presentation of a user interface component when it receives focus (CSS) |

| |G165: Using the default focus indicator for the platform so that high visibility default focus indicators will |

| |carry over |

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

| |SCR31: Using script to change the background color or border of the element with focus (Scripting) |

|3.1.1 |H57: Using language attributes on the html element (HTML) |

|3.2.4 |G197: Using labels, names, and text alternatives consistently for content that has the same functionality AND |

| |following the sufficient techniques for Success Criterion 1.1.1 and sufficient techniques for Success Criterion|

| |4.1.2 for providing labels, names, and text alternatives. |

Copyright © W3C 11 December 2008 World Wide Web Consortium [Status: Recommendation]

WCAG 2.0 Common Failures

The following are common mistakes that are considered failures of each Success Criterion by the WCAG Working Group.

Page Title

SC 2.4.2 Page Titled

()

|Failure |Description |

|F25 |Failure of Success Criterion 2.4.2 due to the title of a Web page not identifying the contents. |

Copyright © W3C 11 December 2008 World Wide Web Consortium [Status: Recommendation]

Text content

SC 1.3.1 Info and Relationships

()

|Failure |Description |

|F2 |Failure of Success Criterion 1.3.1 due to using changes in text presentation to convey information without |

| |using the appropriate markup or text. |

|F17 |Failure of Success Criterion 1.3.1 and 4.1.1 due to insufficient information in DOM to determine one-to-one |

| |relationships (e.g., between labels with same id) in HTML. |

|F43 |Failure of Success Criterion 1.3.1 due to using structural markup in a way that does not represent |

| |relationships in the content. |

|F87 |Failure of Success Criterion 1.3.1 due to inserting non-decorative content by using :before and :after |

| |pseudo-elements and the 'content' property in CSS. |

Copyright © W3C 11 December 2008 World Wide Web Consortium [Status: Recommendation]

SC 1.3.2 Meaningful sequence

()

|Failure |Description |

|F33 |Failure of Success Criterion 1.3.1 and 1.3.2 due to using white space characters to create multiple columns in|

| |plain text content. |

|F32 |Failure of Success Criterion 1.3.2 due to using white space characters to control spacing within a word. |

|F1 |Failure of Success Criterion 1.3.2 due to changing the meaning of content by positioning information with CSS.|

Copyright © W3C 11 December 2008 World Wide Web Consortium [Status: Recommendation]

SC 1.3.3 Sensory Characteristics

()

|Failure |Description |

|F14 |Failure of Success Criterion 1.3.3 due to identifying content only by its shape or location. |

|F26 |Failure of Success Criterion 1.3.3 due to using a graphical symbol alone to convey information. |

Copyright © W3C 11 December 2008 World Wide Web Consortium [Status: Recommendation]

SC 1.4.1 Use of Color

()

|Failure |Description |

|F13 |Failure of Success Criterion 1.1.1 and 1.4.1 due to having a text alternative that does not include |

| |information that is conveyed by color differences in the image. |

|F73 |Failure of Success Criterion 1.4.1 due to creating links that are not visually evident without color vision. |

Copyright © W3C 11 December 2008 World Wide Web Consortium [Status: Recommendation]

SC 2.1.1 Keyboard

()

|Failure |Description |

|F54 |Failure of Success Criterion 2.1.1 due to using only pointing-device-specific event handlers (including |

| |gesture) for a function. |

Copyright © W3C 11 December 2008 World Wide Web Consortium [Status: Recommendation]

SC 3.2.4 Consistent Navigation

()

|Failure |Description |

|F31 |Failure of Success Criterion 3.2.4 due to using two different labels for the same function on different Web |

| |pages within a set of Web pages. |

Copyright © W3C 11 December 2008 World Wide Web Consortium [Status: Recommendation]

Headings

SC 1.3.1 Info and Relationships

()

|Failure |Description |

|F2 |Failure of Success Criterion 1.3.1 due to using changes in text presentation to convey information without |

| |using the appropriate markup or text. |

|F43 |Failure of Success Criterion 1.3.1 due to using structural markup in a way that does not represent |

| |relationships in the content. |

Copyright © W3C 11 December 2008 World Wide Web Consortium [Status: Recommendation]

Link Text

SC 1.1.1 Non-text Content

()

|Failure |Description |

|F39 |Failure of Success Criterion 1.1.1 due to providing a text alternative that is not null (e.g., alt="spacer" or|

| |alt="image") for images that should be ignored by assistive technology. |

|F72 |Failure of Success Criterion 1.1.1 due to using ASCII art without providing a text alternative. |

Copyright © W3C 11 December 2008 World Wide Web Consortium [Status: Recommendation]

SC 1.3.1 Info and Relationships

()

|Failure |Description |

|F2 |Failure of Success Criterion 1.3.1 due to using changes in text presentation to convey information without |

| |using the appropriate markup or text. |

|F42 |Failure of Success Criterion 1.3.1 and 2.1.1 due to using scripting events to emulate links in a way that is |

| |not programmatically determinable. |

Copyright © W3C 11 December 2008 World Wide Web Consortium [Status: Recommendation]

SC 2.1.1 Keyboard

()

|Failure |Description |

|F54 |Failure of Success Criterion 2.1.1 due to using only pointing-device-specific event handlers (including |

| |gesture) for a function. |

|F55 |Failure of Success Criteria 2.1.1, 2.4.7, and 3.2.1 due to using script to remove focus when focus is |

| |received. |

|F42 |Failure of Success Criterion 1.3.1 and 2.1.1 due to using scripting events to emulate links in a way that is |

| |not programmatically determinable. |

Copyright © W3C 11 December 2008 World Wide Web Consortium [Status: Recommendation]

SC 2.4.4 Link Purpose (In Context)

()

|Failure |Description |

|F63 |Failure of Success Criterion 2.4.4 due to providing link context only in content that is not related to the |

| |link. |

Copyright © W3C 11 December 2008 World Wide Web Consortium [Status: Recommendation]

SC 2.4.7 Focus Visible

()

|Failure |Description |

|F55 |Failure of Success Criteria 2.1.1, 2.4.7, and 3.2.1 due to using script to remove focus when focus is |

| |received. |

|F78 |Failure of Success Criterion 2.4.7 due to styling element outlines and borders in a way that removes or |

| |renders non-visible the visual focus indicator. |

Copyright © W3C 11 December 2008 World Wide Web Consortium [Status: Recommendation]

SC 3.2.4 Consistent Identification

()

|Failure |Description |

|F31 |Failure of Success Criterion 3.2.4 due to using two different labels for the same function on different Web |

| |pages within a set of Web pages. |

Copyright © W3C 11 December 2008 World Wide Web Consortium [Status: Recommendation]

Resources

Accessibility

Disability Discrimination Act 1992



A brief guide to the Disability Discrimination Act

(by the Australian Human Rights Commission)



World Wide Web Access: Disability Discrimination Act Advisory Notes

(by the Australian Human Rights Commission)



WCAG2 (W3C Web Content Accessibility Guidelines, Version 2.0)



Web Accessibility National Transition Strategy



WebAIM – Web Accessibility In Mind



Tools

Web Developer Toolbar by Chris Pederick



OzART



WAVE



Colour contrast analysers

•

•

Further Information

AccessibilityOz

Web: .au

Phone: 03 8677 0828

Email: enquiries@.au

-----------------------

AccessibilityOz

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download