Go to content
Version française
Wiki AcceDe Web
You are here:
Home
»
Home
»
Accessibility guidelines for HTML and CSS (to ensure WCAG 2.0 compliance)
»
Who should read this user guide, and how should you use it?
Sitemap
This is a sitemap over all available pages ordered by
namespaces
.
notices
contributeurs
graphique-ergonomique
À qui s'adresse cette notice ?
2.2.1. Associate text with each ambiguous symbol
1.1.4. Make sure that the navigation is visually consistent
3.2.1. Make sure that information is comprehensible, even if the colours are absent
3.1.1. Make sure that there is sufficient contrast between the content and the background or propose an alternative with contrast
Who should read this user guide, and how should you use it?
2.1.1. Keep accents on uppercase letters
Contact
Context and objectives
Credits
1.1.3. Make the current position visually different in the menus
4.2.1. Distinguish links from the surrounding text
WCAG 2.0 correspondence table
7.4.1. Clearly indicate the total number of steps as well as the current step
7.3.1. Clearly indicate mandatory fields
5.1.2. Indicate the language of each document available for download written in a foreign language
5.1.1. Indicate the size and format of each document that can be downloaded
License agreement
Modèle de page "aide et accessibilité"
2.1.2. Do not justify the text
7.1.3. Place each label next to the corresponding field
7.2.1. Provide a submit button at the end of each form
1.1.2. Provide at least two of the following navigation methods: main menu, site map, and search engine
7.3.2. Provide help for entering data
7.1.2. Use identical labels for form fields that have the same purpose
1.2.2. Provide skip links
7.3.3. Provide explicit error messages and suggestions for correcting errors
8.2.3. Provide a way of controlling the progress and volume of each audio content
8.1.3. Provide a way of controlling the progress and volume of each video
7.5.1. Provide an alternative to each CAPTCHA that is either just sound or visual
7.5.2. Provide a refresh method for each CAPTCHA
1.1.1. Provide breadcrumbs
7.2.2. Provide an explicit button text for each button
7.1.1. Provide an explicit label for each form field
4.1.1. Provide a link text for each link
7.3.4. Provide a confirmation message
8.2.2. Provide a way to access the text transcript of each audio content
8.1.2. Provide a way of accessing the text transcript of each video
8.1.6. Provide a way of activating the audio description
8.1.4. Provide a way of displaying the closed captions
7.4.2. Provide a way of returning to the previous steps
8.3.1. Provide a method for stopping each animated content
8.3.2. Provide a way of stopping sounds that are triggered automatically
7.4.3. Provide a summary of values entered before the form is finally submitted
8.2.1. Provide a heading or summary for each audio content
8.1.1. Provide a heading and/or summary for each video
6.1.1. Provide a heading for each data table
8.1.5. Provide a format for closed captions that ensures they are readable
1.2.1. Provide a help page
Additional Recommendations
7.1.4. In long forms group similar form fields together and give them a heading
Acknowledgements
4.1.2. Identify each link that triggers the opening of a new window
2.1.3. Make sure that the typefaces can be integrated in text format
html-css
interfaces-riches-javascript
Brief pour la prise en compte de l'accessibilité dans les vidéos
Notices
Accessibility guidelines for editors (template)
Corriger le dysfonctionnement des ancres activées au clavier sous Internet Explorer
Accessibility guidelines for graphic design (to ensure WCAG 2.0 compliance)
Home
Accessibility guidelines for HTML and CSS (to ensure WCAG 2.0 compliance)
Accessibility guidelines for rich interfaces and JavaScript (Use cases to comply with France’s accessibility guidelines)
playground
ressources
wiki
Home
Licence d'utilisation des contenus du wiki AcceDe Web
notices/html-css/comment-utiliser-cette-notice.txt · Last modified: 13 August 2013 at 14:26 by Sébastien Delorme (Atalan)
