Go to content
Version française
Wiki AcceDe Web
You are here:
Home
»
Home
»
Accessibility guidelines for graphic design (to ensure WCAG 2.0 compliance)
»
6.1.1. Provide a heading for each data table
Sitemap
This is a sitemap over all available pages ordered by
namespaces
.
notices
contributeurs
graphique-ergonomique
html-css
9.2.2. Tag each row header and column header cell with <th>
8.2.1. Tag quotation blocks with <blockquote>
Tag inline quotes with <q>
8.1.3. Tag definition lists with <dl>, <dt> and <dd>
8.1.1. Tag unordered lists with <ul> and <li>
8.1.2. Tag ordered lists with <ol> and <li>
Who should read this user guide, and how should you use it?
Contact
Context and objectives
Credits
9.2.1. Provide a title for each data table with the <caption> tag
1.2.1 Write the HTML source code by following the logical reading order
4.1.1. Write valid HTML code according to the grammar rules of the DOCTYPE used
4.2.2. Use HTML tags for their semantic value
2.1.1. Enter an accurate <title> on each page
10.3.2. Garantir la compréhension de l'information même lorsque CSS est désactivé
10.2.3. Ensure the readability of content even if the text size is doubled
10.3.1. Make sure content is readable when images are not displayed
11.2.1. Ensure visibility of focus when set from the keyboard
WCAG 2.0 correspondence table
1.1.1. Identify the main regions of the page with the role attribute
7.4.1. Indicate in the alt attribute of the CAPTCHA image where the user can find the non-graphic CAPTCHA version
6.2.1. Indicate the size and format of each document that can be downloaded
5.3.2. Include <map> and <area> tags just after each image map in the HTML code
7.1.2. Include information about expected field values directly in <label> tags
License agreement
7.3.1. Update the page <title> when a page returns an error or a confirmation message
11.1.2. Include skip links
1.1.2. Implement a logical and thorough hierarchy of headings using the tags <h1> to <h6>
5.2.1. Do not use CSS to display informative images
4.2.1. Do not use HTML attributes or tags designed exclusively for formatting
9.1.2. Do not use tags or attributes that are specific to data tables in formatting tables
12.1.2. Do not use the wmode parameter with the values transparent or opaque
10.1.1. Do not use the CSS properties display or visibility to hide content that cannot be displayed by the user
7.2.2. Order drop-down list options in a logical way
12.1.1. Provide an alternative to each multimedia content (<video>, <audio>, <object>, etc.)
6.1.1. Write meaningful texts for links and buttons
HTML and CSS additionnal recommendations
7.2.1. Group and title fields of the same type with <fieldset> and <legend>
Acknowledgements
5.3.1. Enter the alt attribute to each image map and corresponding <area /> tags
5.2.2. Enter the alt attribute for informative images
Enter a value for the title attribute for each <iframe>
3.1.1. Use the lang attribute in the <html> tag to define the main language of the page
Include the summary and structure of each data table with the summary attribute
6.3.1. Indicate the opening of new windows
1.1.3. Structure navigation menus with lists
10.2.1. Use CSS to format text
9.2.4. Use the headers and id attributes to associate cells with table header cells in complex data tables
3.2.1. Use the lang attribute to indicate a change in the language
9.2.3. Use the scope attribute to associate cells with the headers in simple tables
6.1.2. As a last resort, use the title attribute to make link and button texts explicit that cannot be made clear otherwise
7.1.1. Use the <label> tag as well as the “for” and “id” attributes to associate form controls with their text labels
5.1.1. Use an empty alternate text (alt="") for decorative and illustrative images
10.2.2. Only use relative sizes (em, %, small, etc.) for typefaces
11.1.1. Make sure the tab order follows the logical reading order
9.1.1. Ensure the correct reading order of formatting tables
1.2.2. Ensure the consistency of the HTML order from one page to the next
2.2.1. Ensure the correct encoding of all characters
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/graphique-ergonomique/prevoir-un-titre-pour-chaque-tableau-de-donnees.txt · Last modified: 20 January 2014 at 11:50 by rlapeze
