Recommendation : 2. Reduce the footprint of static content
Is an alternative to images always available ?
Pictures
A People
B Planet
B Prosperity
Difficulty
*
Priority
High
Récurrence
OnUpdate
Tests
Does each image have alt text?
Precisions
Accessibility assistants must be able to use a description of the information carried by the image in order to allow a good understanding of the service without seeing the image.
Use Case
Source code / CHROME: extension lighthouse / accessibility
CF RGAA 4 criteria 1.1 to 1.9
Additional elements
Operational issues related to the project
Rule for assessing the level of compliance of the criterion
Number of images analyzed / Number of images
Life cycle
Conception
13 other criteria related to the recommendation: Reduce the footprint of static content
Pictures
Have the images been compressed upstream in a format suitable for viewing ?
Pictures
What images are really meaningful and useful for understanding the service (examples: logo, images, links, contractual images, etc.) ?
Pictures
What images can we avoid (not useful for understanding the service) ?
Text
Can text replace certain types of images (icons, picto ...) ?
Animated content
Is the information overlay removed ?
Text
Has the impact of internationalisation (multi-languages, etc.) been assessed ?
Text
Is there a limit to the number of different fonts ?
Text
Do you prefer system fonts ?
Forms
Is the configuration of the form minimal (so as not to overload the code for unhelpful styles) ?
Forms
Does the form allow the user to disable dynamic functions (ex: auto completion) ?
Forms
Are the forms useful (example: not creating an account for the purchase of a product / service - e-commerce) ?
Forms
Are robots banned and unsolicited access treated by inexpensive solutions (captcha vs "addition", ....) ?
Forms
When selection lists are available, are they limited to values relevant to the service user ?