Hosting Video and Audio on YouTube for Compliance
IMPORTANT: This table needs actioning by everyone as it is not covered by third party widgets and will help make you compliant!
Hosting your videos and audio on YouTube supports accessibility by offering captions, subtitles, and audio descriptions. The platform is also compatible with screen readers and keyboard navigation, ensuring usability for individuals with visual and mobility impairments.
Swipe on table to read more details
Perceivable
1.2.1
A
For prerecorded audio-only and prerecorded video-only media, the following are true, except when the audio or video is a media alternative for text and is clearly labeled as such:
Prerecorded Audio-only: An alternative for time-based media is provided that presents equivalent information for prerecorded audio-only content.
Prerecorded Video-only: Either an alternative for time-based media or an audio track is provided that presents equivalent information for prerecorded video-only content.
Covered by Content Management.
All BUs to only use video embedded in Youtube instead of uploading videos on hybris. This should cover all the video related guidelines not covered.
In case videos on the website do not comply, the scanning of the website will detect and alert the BU about it.
Perceivable
1.2.2
A
Captions are provided for all prerecorded audio content in synchronized media, except when the media is a media alternative for text and is clearly labeled as such.
Covered by Content Management.
Audio must be managed by a third party WCAG compliant. Example: https://www.marionnaud.fr/conseils-beaute/category/podcasts-marionnaud
This is an example of a Podcast used in MFR which is not showing Captions.
In case PODcasts (audio prerecorded) on the website do not comply, the scanning of the website will detect and alert the BU about it.
Perceivable
1.2.3
A
An alternative for time-based media or audio description of the prerecorded video content is provided for synchronized media, except when the media is a media alternative for text and is clearly labeled as such.
Covered by Content Management.
Audio must be managed by a third party WCAG compliant. Example: https://www.marionnaud.fr/conseils-beaute/category/podcasts-marionnaud
This is an example of a Podcast used in MFR which is not showing Captions.
In case PODcasts (audio prerecorded) on the website do not comply, the scanning of the website will detect and alert the BU about it.
Perceivable
1.2.5
AA
Audio description is provided for all prerecorded video content in synchronized media.
Covered by Content Management.
Audio must be managed by a third party WCAG compliant. Example: https://www.marionnaud.fr/conseils-beaute/category/podcasts-marionnaud
This is an example of a Podcast used in MFR which is not showing Captions.
In case videos on the website do not comply, the scanning of the website will detect and alert the BU about it.
Perceivable
2.5.8
AA
The size of the target for pointer inputs is at least 24 by 24 CSS pixels, except where:
Spacing: Undersized targets (those less than 24 by 24 CSS pixels) are positioned so that if a 24 CSS pixel diameter circle is centered on the bounding box of each, the circles do not intersect another target or the circle for another undersized target;
Equivalent: The function can be achieved through a different control on the same page that meets this criterion;
Inline: The target is in a sentence or its size is otherwise constrained by the line-height of non-target text;
User agent control: The size of the target is determined by the user agent and is not modified by the author;
Essential: A particular presentation of the target is essential or is legally required for the information being conveyed.
Note 1: Targets that allow for values to be selected spatially based on position within the target are considered one target for the purpose of the success criterion. Examples include sliders, colour pickers displaying a gradient of colours, or editable areas where you position the cursor.
Note 2: For inline targets the line-height should be interpreted as perpendicular to the flow of text. For example, in a language displayed vertically, the line-height would be horizontal.
Investigation ongoing and so far resulted in a deck with occurrences.
Some of these occurrences have an alternative way of using the functionality and are regarded as OK.
Some of these occurrences have NO alternative and need remediation by enlarging.
PO FEEDBACK:
- we asked ChatGPT to summarise requirement in easy way (link: https://elab-aswatson.atlassian.net/wiki/spaces/~296055901/pages/5331484775/High-prio+Accessibility+Reqs+Review#Target-Size-(Minimum)---Level-AA(Added-in-2.2))
- targets (links, buttons, navigation items) should be big enough (min 24 x 24 px) with some exceptions (e.g. for inline link text or in case the element has enough space around to avoid issues while clicking)
We asked ChatGPT to analyse a full page screenshot of TPS (link: https://elab-aswatson.atlassian.net/wiki/spaces/~296055901/pages/5331484775/High-prio+Accessibility+Reqs+Review#Target-Size-(Minimum)---Level-AA(Added-in-2.2)):
- some elements are compliant because larger than 24 x 24
- some elements are reported as potential issues (e.g. navigation dots in banner carousel)
In general, it suggested to perform full analysis using browser extension (e.g. Accessibility Insights for Web or axe DevTools)
Final feedback: a deeper testing/review of elements should be run to spot too small elements that do not respect the requirement, also taking advantages of browser extension.
*POUR are the four principles of accessibility - Perceivable, Operable, Understandable, and Robust as outlined in the Web Content Accessibility Guidelines (WCAG).
