This is an old revision of the document!

Who should read this user guide, and how should you use it?

This document should be given to stakeholders and/or service providers who create the technical specifications and the HTML/CSS templates, and who are responsible for the different technical developments of rich interfaces. It should be used in addition to the technical specifications of a project, and the Accessibility guidelines for HTML and CSS (to ensure WCAG 2.0 compliance). The recommendations may be supplemented with others, or left out, according to the circumstances—the project manager is often the most appropriate person for this task.

The recommendations should be considered for the HTML/CSS, JavaScript, and Flash integration phases. Some recommendations apply when pages are produced dynamically from templates that are integrated in a content management system (CMS).

There are some annotations that complete the document and should be read to understand each recommendation:

Note: Notes help complete the recommendations by providing additional details for specific situations.

Warning: Warnings highlight specific points that require attention or traps to avoid in order to guarantee good accessibility.

Tip: Tips are not directly linked to accessibility, but you can improve the general quality of the interfaces by implementing them, or facilitate the integration of accessibility in the subsequent steps in the project. Note that the recommendations in this project, although aimed at accessibility, are often good practice for ensuring ease of use, and improved user experience, performance, and referencing.

HTML5 : The HTML5 insets provide additional details or warnings to the recommendations in the light of the developments proposed in the new HTML specification.

notices/interfaces-riches-javascript/comment-utiliser-cette-notice.1367249369.txt.gz · Last modified: 29 April 2013 at 17:29 by Sébastien Delorme (Atalan)

Project coordinated by Atalan.

In partnership with: