Story #75568
closed
Epic #75567: Accessibility: As an editor I want to create accessible content which passes the accessiblity tests from WCAG 2.0.
Images: I want to create accessible images when adding images to content elements.
Added by Kerstin Finke over 8 years ago.
Updated over 4 years ago.
Description
As an editor I want to create accessible images when adding images to content elements.
Acceptance Criteria:
- A warning is displayed
- if no alt-text is given - text: “An image must have an alt text if it is not decorative only”
- if the alt-text includes the filename - “The alt text must not include the filename”
- if the alt text has more than 100 characters - “The alt text must not be longer than 100 characters.”
- The warning contains the WCAG rule and a direct link to the explanation of the rule (WCAG rule 1.1.1 - Level A - https://www.w3.org/WAI/WCAG20/quickref/?showtechniques=11%2C111#text-equiv)
Technical Description / Additional Information:
- There is currently no possibilty to override the alt text in the file link element, this has to be added.
- This concerns all images added to content in all content elements (text and media, file link, …)
- Parent task set to #75567
- Description updated (diff)
- Description updated (diff)
- Subject changed from Images: As an editor I want to create accessible images when adding images to content elements. to Images: I want to create accessible images when adding images to content elements.
- Description updated (diff)
- Related to Task #89505: Make alternative text more prominent in backend added
It would also be nice to have a link to the decision tree of the Web Accessibility Tutorials shown next to the field.
https://www.w3.org/WAI/tutorials/images/decision-tree/
I just resorted the form elements in the backend to make the alt information more prominent. Additionally I added a description text for the alt field to give every editor more information why it is important to fill this field.
There are no warnings implemented yet, as there is currently no common way for warnings (just for errors like for required fields). For the acceptance criteria warnings we should maybe only inform on conflicts with WCAG.
- Having an empty issue for a non descriptive image is a clear accessibility issue in terms of WCAG
- Having a filename inside the image could also happen if you named your file in a descriptive manner.
- Also I did not find any reference for the 100 characters limit in the WCAG - I think it is a good suggestion, but I do not see it as a requirement of the WCAG
- Tags set to accessibility
- Status changed from New to Closed
As there is currently no one working on these stories and as we have a restarted accessibility initiative and these kind of stories should be taken into account and planned to be developed by that initiative. Of course, the content here is still relevant and can be used for creating further plans once concrete steps to implement these stories are being taken.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by