AcceDe Web, a Guide for Accessibility Web Projects, OW2con'16, Paris.
0 likes313 views
The document outlines web accessibility guidelines developed by David Monnehay aimed at making accessibility easier for project management teams. It emphasizes the need for clear, practical recommendations and provides a set of design and UX principles to ensure websites and applications are accessible. The guidelines are open-sourced and can be adapted to fit existing project development processes, promoting collaboration among team members in optimizing accessibility.
![Easily understandable recommendations
Synthetic and operational
An open sourced knowledge base for web professionals
Project oriented
Adapted to project development phases
Provide skip links [Design and UX guideline]
A “Go to content” skip link must be displayed in the same place at the top of every page.
Tip
If necessary the skip link can be hidden by default, so that it is only displayed in specific
circumstances circumstances (navigation with the keyboard, version for mobile phones,
etc.).](https://image.slidesharecdn.com/3davidmonnehayaccede-web-160928091037/85/AcceDe-Web-a-Guide-for-Accessibility-Web-Projects-OW2con-16-Paris-4-320.jpg)
AcceDe Web, a Guide for Accessibility Web Projects, OW2con'16, Paris.
- 1. AcceDe Web Open source practical accessibilty guidelines David Monnehay E-Accessibility consultant
- 2. Available guidelines RGAA SGQRI 008-02 They are not fitted for project management Hard to master for most members of a production team (project managers, ux designer, graphic designer, editors & contributors,…) One of the reasons for the limited amount of accessible websites and applications available and many more…
- 3. Project supported by Agence Entreprises & Handicap, Anysurfer, Association des Paralysés de France (APF), CIGREF, Design For All Foundation, ESSEC, Handirect, Hanploi, Sciences Po, Télécom ParisTech First set of web accessibility guidelines suited for project management
- 4. Easily understandable recommendations Synthetic and operational An open sourced knowledge base for web professionals Project oriented Adapted to project development phases Provide skip links [Design and UX guideline] A “Go to content” skip link must be displayed in the same place at the top of every page. Tip If necessary the skip link can be hidden by default, so that it is only displayed in specific circumstances circumstances (navigation with the keyboard, version for mobile phones, etc.).
- 5. Use cases Guideline for graphic and UX design : Provide different visual states for links
- 6. Guideline for graphic and UX design : Provide different visual states for links Guideline for HTML & CSS : Make sure the focus state is visible Use cases
- 7. Use cases
- 8. Guideline for graphic and UX design : Provide a way to stop animations Use cases Guideline for rich interfaces and JavaScript : Slideshows Basic HTML Code, Javascript behavior, keyboard behavior
- 9. Guidelines for rich interfaces and JavaScript : Slideshows Basic HTML Code, Javascript behavior, keyboard behavior Use cases
- 10. Guidelines for rich interfaces and JavaScript : Slideshows Basic HTML Code, Javascript behavior, keyboard behavior Guideline for graphic and UX design : Make sure that there is sufficient contrast between the content and the background or propose an alternative with contrast Use cases
- 11. Guidelines for rich interfaces and JavaScript : Slideshows Basic HTML Code, Javascript behavior, keyboard behavior Guideline for graphic and UX design : Make sure that there is sufficient contrast between the content and the background or propose an alternative with contrast Fail 2.4:1 Pass 4.7:1 Fail 2.3:1 Fail 2.2:1 Use cases
- 12. Use cases
- 13. Use cases
- 14. Check list for each project steps An easy way to include every team members in the accessibility optimization effort The right information when needed Can be adapted to fit any existing quality process