-
Notifications
You must be signed in to change notification settings - Fork 88
Ignore SVG accessible name requirement when the svg is used as the image of a button with an accessible name #2224
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
Comments
another instance in IBM Cloud See https://cloud.ibm.com/observability/event-routing/routes/create
Checker incorrectly reports the following violations: Rule ID: svg_graphics_labelled
|
Triage: as a button child, because the button's children are presentational, the svg name check should be ignored. |
Another example:
|
Triage: ignore only if an ancestor with named from author, the image/svg is a descendant of any element that uses aria-label/aria-labelledby for its accessible name. |
When an svg is used as an image of a button, if the button already has an accessible name, the accessible name for the svg should not be required.
a test case in Carbon: https://react.carbondesignsystem.com/?path=/docs/experimental-fluid-components-unstable-fluidnumberinput--overview
Is this similar to the requirement for an image if it's used for a button?
Also refer to Inapplicable Example 4 in ACT rule for its interpretation.
The text was updated successfully, but these errors were encountered: