Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Accessibility: Video block placeholder image missing Alt #4747

Open
rnunez80 opened this issue May 11, 2023 · 2 comments
Open

Accessibility: Video block placeholder image missing Alt #4747

rnunez80 opened this issue May 11, 2023 · 2 comments
Assignees
Labels
99 tag: UX Accessibility Accessibility issues

Comments

@rnunez80
Copy link

Accessibility Issues
WCAG 2.1 Level A
Alternative (alt) text is read to users utilizing screen readers. Alternative text should be provided to describe what is present in the image so that users who are unable to see have an equal experience as sighted users. Quick tip: If the image is being utilized as a link with no other text, the alternative text should be the location of the link. If the image is of words, the alternative text should be the words contained in the image.
Impact: critical
Violations
WCAG 2.1 Level A: 1.1.1 Non-text Content
Section 508: 1194.22 (a) Text equivalent for non-text elements
Element Location
.computer.mobile.tablet:nth-child(1) > div > .video.block.align > .video-inner > .\31 6:9.embed.ui > .placeholder

Element Source

Failure Summary
Fix any of the following: Image does not have an alt attribute. To markup the image as decorative, override the semantics by adding role="none" or role="presentation"

@stevepiercy
Copy link
Collaborator

@maniksharma424
please read and follow Contributing to Plone and First-time contributors.

@plone plone deleted a comment from maniksharma424 May 14, 2023
@rotavio
Copy link

rotavio commented Jul 14, 2023

We've just found out this issue while running a11y tests.
The Embed component from SemanticUI does not have a way to change props for the placeholder image.

Are there any plans to fix this issue?

If we choose to customize it in our project, what would be the native or "volto way" of doing this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
99 tag: UX Accessibility Accessibility issues
Projects
None yet
Development

No branches or pull requests

4 participants