Skip to navigation | Skip to content Join the Facebook page Ideose Join Ideose page on Twitter

Translation

Back to the original French page Read this page in Italian by Google Translation Read this page in Portuguese by Google Translation Read this page in English by Google Translation Read this page in German by Google Translation Read this page in Spanish by Google Translation Read this page in Arabic by Google Translation Read this page in Hebrew by Google Translation

Space Ideose

WCAG 2.0 for HTML

Go to Beginning of content without using the bar Consultation and Sharing How to use the bar Consultation and Sharing Listen to the main content of this page
Print Print the main content of this page Send Email the main content of this page Share Share this page on TwitThis Share this page on Facebook Share this page on Wikio Share this page on Google Share this page on LinkedIn Share this page on Digg Share this page on del.icio.us Share this page on Netvibes

Warning: The original version of this document is WebAIM's WCAG 2.0 Checklist for HTML documents . This French translation was done by Ideose as part of an agreement between WebAIM and Ideose .

Note: See page documents on web accessibility for a list of all translated documents. Other resources on web accessibility are also listed in the portal accessible digital .

Summary

  1. Perceptible
  2. Usable
  3. Understandable
  4. Robust

Translations

Translations of this document are available:

Important!

The information on this page are not WCAG 2.0. This is a simple checklist that presents recommendations for the implementation of the principles and techniques to meet WCAG HTML 2.0. The formulation used here is significantly different from that used in the official version of WCAG 2.0 in order to make easier their implementation and verification of web pages (Note: see also the French version approved by the W3C WCAG 2.0 as advertised Ideose by June 28, 2009).

Recommendations to use this list:

  • This list may not be used to verify compliance with WCAG 2.0. You must use the official documentation of WCAG 2.0 to determine the level of compliance or noncompliance.
  • This list should not be referenced in the regulations. Although this is a useful resource for the technical implementation of WCAG 2.0 for HTML content, this is not a list to put in the regulations. Official documentation of WCAG 2.0 describes much better the mechanisms of implementation of accessibility in the regulations or laws.
  • WCAG 2.0 covers the accessibility of all Web content and are not technology specific. But this list was reduced to HTML primarily for the assessment of HTML content. This list is quite limited and subject to technological change, while WCAG 2.0 are much less.
  • This list presents the interpretation of WCAG 2.0 and its success criteria by WebAIM. It describes the techniques recommended by WebAIM to meet the criteria for success. The first column of the tables below provides links to the success criteria of the official version of WCAG 2.0 in French. Only official guidelines can be used to verify conformance to WCAG 2.0.

A version of this list is also available ( download Adobe Reader ).

Perceptible
Web content is made ​​perceptible to the senses - sight, hearing and / or touch.

Recommendation 1.1
Text equivalents - Provide text equivalents for all non-text content which can then be presented in different forms depending on user needs: large print, Braille, speech, symbols or simpler language.

Success criteria Recommendations
1.1.1 Non-text Content
(Level A)
  • All images, buttons and forms an image map areas of the images must have a text alternative appropriate and equivalent.
  • Images that do not convey content, which are decorative or whose content is already provided by the text have an alt empty text ( alt="" ) or are implemented in the background CSS. All images links have a text alternative that describes the function of the link.
  • Alternatives to complex images are given in the web page or in a separate page (for linking and / or attribute longdesc ).
  • The form buttons have a description given by the attribute value .
  • Fields inputs have text labels associated or, if the labels can not be used, they describe an attribute title .
  • The embedded multimedia (embedded) is identified by an accessible text.
  • Frames ( frames ) have titles appropriate.

Recommendation 1.2
Time-based media - Propose alternate versions to the media time.

Note: if audio or video takes over the content of the web page (for example, an audio or video version of sign language for the Web page), then Web content is their alternative.

Success criteria Recommendations
1.2.1 Content only audio or only video (prerecorded)
(Level A)
  • A descriptive text transcript (including all information and audio information) is given for the audio on the Web offline (audio podcasts, MP3, etc..).
  • A textual description is given for audio or video without sound, on the web and offline (eg, a video that has no audio track).
1.2.2 Captions (prerecorded)
(Level A)
  • The subtitles are provided for the synchronized videos on the Web offline (YouTube videos, etc..).
1.2.3 Audio-description or for a replacement version of time-based media (pre-registered)
(Level A)
1.2.4 Captions (Live)
(Level AA)
  • , vidéo conférences, animations Flash, etc.). Of synchronized captions are given for a live broadcasting, which contains audio (audio-only broadcast, web casts, video conferences, Flash animations, etc..).
1.2.5 Audio description (pre-recorded)
(Level AA)
  • Of audio-descriptions are given for all videos.
    Note: this is only required if the vehicle video visual content that is not already featured on the soundtrack.
1.2.6 Sign Language (prerecorded)
(Level AAA)
  • A video sign language is given to all media that contain audio.
1.2.7 Audio-description extended (prerecorded)
(Level AAA)
  • When an audio-description can not be added to video due to audio timing (for example, there is no silence), an alternative version of the video with pauses to insert audio description is given.
Version 1.2.8 for an alternative time-based media (pre-recorded)
(Level AAA)
  • A descriptive text transcript is provided for all pre-recorded media that have a video track.
1.2.9 Only audio (live)
(Level AAA)
  • A descriptive text transcript (eg, a script for a live sound) is given for all to have direct audio.

Recommendation 1.3
Adaptable - Create content that can be presented in different ways without losing information or structure (eg with a simpler layout).

Success criteria Recommendations
1.3.1 Information and relationships
(Level A)
  • The semantic code is used for paragraph headings ( h1 ), lists ( ul , ol and dl ), texts whose meaning is stressed or specific texts (for example, strong , code , abbr , blockquote ), etc.. The semantic code should be used appropriately.
  • The tables are used to identify the data tables. When necessary, data cells are associated with their headers. The titles of data tables and summaries are given if necessary.
  • The text labels associated with form field input. Form fields are grouped into areas of common information with a fieldset / legend .
1.3.2 Sequential order logic
(Level A)
1.3.3 Sensory Characteristics
(Level A)
  • The instructions are not given only according to shape, size or position visual (eg, "Click the square to continue" or "The instructions are all in the column to the right").
  • The instructions are not given only so sound (eg, "A beep tells you that you can continue").

Recommendation 1.4
Distinguishable - Facilitate the visual and auditory perception of user content including separating foreground from background.

Success criteria Recommendations
1.4.1 Use of Color
(Level A)
  • The color is not the only means used to convey information or elements visually distinguishable.
  • The color is not the only means used to distinguish a link from the surrounding text unless brightness contrast between the link and surrounding text is at least 3:1 and an average additional given when the mouse passes over or when it receives keyboard focus (for example, the link becomes underlined).
1.4.2 Sound Control
(Level A)
  • A mechanism is given to stop, pause or adjust the volume for a sound that starts automatically on a page and lasts more than 3 seconds.
1.4.3 Contrast (Minimum)
(Level AA)
  • The text and image texts have a contrast ratio of at least 4.5:1.
  • A large text (above 18 points or 14 point bold) has a contrast ratio of at least 3:1.
1.4.4 Resize text
(Level AA)
  • The page is readable and functional when the text size is doubled.
1.4.5 Text as images
(Level AA)
  • If the same visual presentation of text can be done alone, an image is not used to display text.
1.4.6 Contrast (Enhanced)
(Level AAA)
  • The text and image texts have a contrast ratio of at least 7:1.
  • A large text (above 18 points or 14 point bold) has a contrast ratio of at least 4.5:1.
1.4.7 Background sound of low volume or absent
(Level AAA)
  • The audio of a speech has little or no background noise, making it easily audible speech.
1.4.8 Visual Presentation
(Level AAA)
  • Text blocks of more than one sentence:
    • contain no more than 80 characters.
    • are NOT justified (aligned to both left and right).
    • have a spacing of lines (at least half the height of the text) and a spacing of subsections (1.5 times the line spacing) minimum.
    • have a foreground color and background specified. They can be applied to specific items or entire page using CSS (all other elements inherit style then).
    • does NOT create horizontal bar when the text size is doubled.
1.4.9 Text as an image (without exception)
(Level AAA)
  • The text is presented as an image only for decoration (image does not convey content) OR when the information can not be presented only with text.

Usable
The forms interface, and navigation controls are used.

Recommendation 2.1
Keyboard Accessibility - Make all functionality keyboard accessible.

Success criteria Recommendations
2.1.1 Keyboard
(Level A)
  • All features of the page are used to the keyboard, unless a feature can not be operated at the keyboard by all known methods (eg, draw freehand).
  • Shortcut keys for a specific page and keyboard shortcuts (the shortcuts should be avoided) does not conflict with existing browser and shortcuts to a screen reader.
2.1.2 No Keyboard Trap
(Level A)
  • Focus keyboard is never locked or trapped in a page element. The user can navigate to and from any navigable part of the page using only the keyboard.
2.1.3 Keyboard (No Exception)
(Level AAA)
  • All features of the page are used to the keyboard.

Recommendation 2.2
Sufficient time - Provide users enough time to read and use content.

Success criteria Recommendations
2.2.1 Setting time
(Level A)
  • If a page or application has a time limit, the user has the option to close, modify or extend this time limit. This is not a requirement for real-time events (eg, an auction) where the time limit is mandatory or if time limit is longer than 20 hours.
2.2.2 Pause, Stop, Hide
(Level A)
  • Automatic movements, blinking or scrollable content that do not last more than 3 seconds can be paused, stopped, or hidden by the user. Movements, blinking or scrollable content can be used to attract attention or to emphasize content as long as they last less than 3 seconds.
  • The contents that automatically update (for example, automatic redirects or page refresh, a news ticker, a field updated via AJAX, an alert notification, etc..) Can be paused, stopped or hidden by the user or the user can manually control the triggering of updates.
2.2.3 No timeframe
(Level AAA)
  • The content and functionality have no time limits or time constraints.
2.2.4 Interruptions
(Level AAA)
  • Interruptions (alerts, page updates, etc..) Can be triggered later, or removed by the user.
2.2.5 New authentication
(Level AAA)
  • If an authentication session expires, the user can re-authenticate and continue without losing any data of the current page.

Recommendation 2.3
Crises - Do not design content can cause seizures.

Success criteria Recommendations
2.3.1 No more than three flashes or below the critical
(Level A)
2.3.2 Three Flashes
(Level AAA)
  • No content in a page should flash more than 3 times per second.

Recommendation 2.4
Waterway - Provide the user with guidance to navigate, find content and determine where the website.

Success criteria Recommendations
2.4.1 Bypass Blocks
(Level A)
  • A link is provided to skip navigation and other page elements that are repeated on all pages.
  • If a page has a struture correct paragraph headings, it can be considered a sufficient technique instead of the link "Go to main content." Note that the paragraph headings navigation is not yet possible in all browsers.
  • If a page has frames and have appropriate titles, this technique is sufficient to pass each part individually.
2.4.2 Title of page
(Level A)
  • The Web page has a page title descriptive and informative.
2.4.3 Course Focus
(Level A)
  • The order of navigation links, form fields, etc.. is logical and intuitive.
2.4.4 Function of the link (as appropriate)
(Level A)
  • The destination of each link (or button image forms or areas of an image map) can be determined either by the link text alone or from the link text and its context (for example, the paragraphs that the surrounding the list items, the table cells or the headers of a table).
  • Links (or buttons image forms) with the same text that point to different directions are distinguishable by reading.
2.4.5 Multiple Access
(Level AA)
  • Different means of access to Web pages are provided on the site - at least two: a list of relevant pages, a table of contents, a sitemap, a search engine or a list of all the Web pages available.
2.4.6 Headings and Labels
(Level AA)
  • The paragraph headings in the pages, the labels for the form fields and interactive controls are informative. Avoid using the same titles (for example, "More details") or the same text labels (eg "Name") unless the structure does not differentiate adequately.
2.4.7 Visibility of the focus
(Level AA)
  • The page element that has keyboard focus is visually apparent (when you tab through the page, you can see where you are).
2.4.8 Location
(Level AAA)
  • If a Web page is part of a set of pages, or if the site is complex, an indication of the location of the current page is given, for example via a breadcrumb or by specifying step in the sequence (eg, "Step 2 of 5 - Shipping Address").
2.4.9 Function of the link (link only)
(Level AAA)
  • The destination of each link (or button image forms or areas of an image map) can be determined from the link text alone.
  • There are no links (or buttons image forms) with the same text that point to different directions.
2.4.10 In section headers
(Level AAA)
  • Beyond giving an overall structure to the document, information is grouped and have paragraph headings if appropriate.

Understandable
The content and interface are understandable.

Recommendation 3.1
Readable - Make text content readable and understandable.

Success criteria Recommendations
3.1.1 Language of Page
(Level A)
  • The language of the page is identified using the HTML attribute lang .
3.1.2 Language of a passage
(Level AA)
  • When appropriate, sections of content that have a different language identify this change in language for example using the attribute lang ( <blockquote lang="es"> ).
3.1.3 Rare Words
(Level AAA)
  • The words can be ambiguous, unknown, or used in a very special are defined by an adjacent text, a definition list, a glossary, or any other suitable method.
3.1.4 Abbreviations
(Level AAA)
  • The descriptions of the abbreviations are given their first occurrence using the tag <abbr> or pointing to a definition or glossary. Note: WCAG 2.0 provides no exception to the same abbreviations used regularly (for example, the abbreviation HTML should always be described).
Reading level 3.1.5
(Level AAA)
  • A more understandable alternative is given a content that requires a person over 9 years of study to be understood.
3.1.6 Pronunciation
(Level AAA)
  • If the pronunciation of a word is vital to understand this word, its pronunciation is given immediately after the word or via a link or a glossary.

Recommendation 3.2
Predictable - Ensure that pages appear and operate in predictable ways.

Success criteria Recommendations
3.2.1 In Focus
(Level A)
  • When a part of a page receives focus, it should not create a radical change in the page as opening a new window, a further change in keyboard focus, or any changes that may be confusing or disorienting the user.
3.2.2 A seizure
(Level A)
  • When a user inputs information or interacts with a control, this should not create a radical change in the page as opening a new window, a further change in keyboard focus, or any changes that may create confusion or disorientation user unless the user is informed of this change before.
3.2.3 Navigation coherent
(Level AA)
  • The navigation links that are repeated on web pages do not change their order on different Web pages.
3.2.4 Identification of coherent
(Level AA)
  • The elements that have the same functionality in many Web pages are identified consistently. For example, a search box at the top of the site must always have the same label.
3.2.5 Change in demand
(Level AAA)
  • Substantial changes to a page such as opening a new window, a further change in keyboard focus, or any changes that may create confusion or confuse the user must be initiated by the user. Conversely, the ability to disable such changes is given to the user.

Recommendation 3.3
Input help - Help users avoid and correct input errors.

Success criteria Recommendations
3.3.1 Identification of errors
(Level A)
  • The required form fields or those seeking a format, a value or a specific length give this information by the field label (or if the label is not given, the information is given by the attribute title of the field) .
  • If used, the indications and the errors due to a form validation (client side or server side) alert users of errors in an efficient, intuitive and accessible. Errors are clearly identified, quick access to the problematic element is given and the user may easily correct the error and return the form.
3.3.2 Labels or Instructions
(Level A)
  • Labels, signs and adequate instructions for the interactive elements are given via instructions, examples, labels form fields correctly placed and / or fieldset / legend .
Suggestion 3.3.3 after an error
(Level AA)
  • If an input error is detected (by a client-side validation or server side), suggestions are given to correct the error in a certain way in time and accessible.
3.3.4 Error Prevention (Legal, Financial, Data)
(Level AA)
  • If the user can change or delete information with legal, financial or test changes / deletions are reversible, verified or confirmed.
3.3.5 Help
(Level AAA)
  • If the user can send, change or delete information, the information is reversible, verified or confirmed.
3.3.6 Error Prevention (All)
(Level AAA)
  • If the user can send information, the shipment is reversible, verified or confirmed.

Robust
Content can be treated reliably by a variety of user agents including assistive technologies.

Recommendation 4.1
Compatible - Maximize compatibility with current and future user agents, including assistive technologies.

Success criteria Recommendations
4.1.1 Parsing
(Level A)
  • Errors HTML / XHTML meaningful validation / parsing is avoided. Use the W3C validator
4.1.2 Name, Role and value
(Level A)
  • The coding is used in a manner to facilitate accessibility. This includes respect the HTML / XHTML and use forms, fields, labels, titles, frames, etc.. appropriately.

© 2008 W3C ® ( MIT , ERCIM , Keio ), Tous droits réservés. This list is given in respect of assistance to the implementation of Web Content Accessibility Guidelines (WCAG) 2.0 (W3C Recommendation of 11 December 2008), which are under Copyright © 2008 W3C ® ( MIT , ERCIM , Keio ), All rights reserved. The legal aspects , the trademark license and conditions of use apply W3C.

WebAIM is an initiative of:
Center for Persons with Disabilities (CPD) Utah State University

Copyright 1999-2009 WebAIM

Top of Page