This shows you the differences between two versions of the page.
notices:interfaces-riches-javascript:comment-utiliser-cette-notice [29 April 2013 at 17:29] Sébastien Delorme (Atalan) |
notices:interfaces-riches-javascript:comment-utiliser-cette-notice [13 August 2013 at 14:22] (current) Sébastien Delorme (Atalan) |
||
---|---|---|---|
Line 1: | Line 1: | ||
====== Who should read this user guide, and how should you use it? ====== | ====== 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 [[notices:html-css]]. 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. | + | This document should be given to stakeholders and/or service providers responsable for the technical specifications, the HTML/CSS templates and the technical development of rich interfaces. It should be used in addition to the technical specifications of a project, and the [[notices:html-css]]. The recommendations may be supplemented with others, or left out, according to the circumstances. The project manager is often the most appropriate person to make this decision. |
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). | 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). | ||
Line 9: | Line 9: | ||
<note>**Note**: Notes help complete the recommendations by providing additional details for specific situations.</note> | <note>**Note**: Notes help complete the recommendations by providing additional details for specific situations.</note> | ||
<note attention>**Warning**: Warnings highlight specific points that require attention or traps to avoid in order to guarantee good accessibility.</note> | <note attention>**Warning**: Warnings highlight specific points that require attention or traps to avoid in order to guarantee good accessibility.</note> | ||
- | <note astuce>**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.</note> | + | <note astuce>**Tip**: Tips are not directly linked to accessibility, but improve the general quality of interfaces or facilitate the integration of accessibility of subsequent steps in the project. Note that the recommendations in this project, although aimed at accessibility, also improve user experience, ease of use, performance and referencing. </note> |
- | <note html5>**HTML5** : The HTML5 insets provide additional details or warnings to the recommendations in the light of the developments proposed in the new HTML specification.</note> | + | <note html5>**HTML5**: The HTML5 insets provide additional details or warnings in light of the developments proposed in the new HTML specification.</note> |