Recommendation : 2. Reduce the footprint of static content
Is an alternative to images always available ?
Does each image have alt text?
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.
Source code / CHROME: extension lighthouse / accessibility
CF RGAA 4 criteria 1.1 to 1.9
Operational issues related to the project
Rule for assessing the level of compliance of the criterion
Number of images analyzed / Number of images
13 other criteria related to the recommendation: Reduce the footprint of static content
Have the images been compressed upstream in a format suitable for viewing ?
What images are really meaningful and useful for understanding the service (examples: logo, images, links, contractual images, etc.) ?
What images can we avoid (not useful for understanding the service) ?
Can text replace certain types of images (icons, picto ...) ?
Is the information overlay removed ?
Has the impact of internationalisation (multi-languages, etc.) been assessed ?
Is there a limit to the number of different fonts ?
Do you prefer system fonts ?
Is the configuration of the form minimal (so as not to overload the code for unhelpful styles) ?
Does the form allow the user to disable dynamic functions (ex: auto completion) ?
Are the forms useful (example: not creating an account for the purchase of a product / service - e-commerce) ?
Are robots banned and unsolicited access treated by inexpensive solutions (captcha vs "addition", ....) ?
When selection lists are available, are they limited to values relevant to the service user ?