-
Notifications
You must be signed in to change notification settings - Fork 70
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
[23a2a8] Image has non-empty accessible name - Inapplicable Example 1 is arguable #2241
Comments
Applies also to Image accessible name is descriptive - Inapplicable Example 3 |
And Image not in the accessibility tree is decorative - Inapplicable Example 4 |
Discussed during F2F.
Next steps:
|
Moving
to another issue, since it's quite complex. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In Image has non-empty accessible name, Inapplicable example 1 is arguable:
Chrome exposes the element as an image in the acc tree, while Firefox treats it as a graphics-document but announces it as an empty image when using a screen reader.
Marking this example as inapplicable forces tools to ignore it as an issue if they aim for full consistency. I suggest removing this specific inapplicable example and adding an Accessibility Support note. Alternatively, we could expand the role's applicability. Either approach works, but I don’t think it should remain inapplicable.
The text was updated successfully, but these errors were encountered: