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

ID 260316: [Programmatic Access - Simon - Value Mapping]: Aria-label is not defined for "Remove" button under "Value mapping" dialog. #66346

Closed
Tracked by #65701
eledobleefe opened this issue Apr 12, 2023 · 3 comments · Fixed by #69699
Assignees
Labels
area/frontend internal for issues made by grafanistas MAS type/accessibility Accessibility problem / enhancement wcag/4.1.2 UI components name and role can be programmatically determined.

Comments

@eledobleefe
Copy link
Contributor

eledobleefe commented Apr 12, 2023

User Experience:

Screen reader dependent users may get misguided while navigating, if the screen reader is not announcing the proper name of the controls present on the page as they will not understand it's purpose.
Note: User credentials should NOT be included in the bug.

Repro Steps:

  • Open #Url: play.grafana.org Sign in with valid credentials. "Home" page appears.
  • Navigate the Feature Showcase pane heading and select it.
  • Navigate the expanded Dropdown and select the "Edit" menu item.
  • Navigate the page "Edit" page which appears.
  • Navigate to the "All" buttons and select it.
  • Navigate to "Value Mapping" button and expand it.
  • Navigate all the controls present under it.
  • Run AI tool. Verify the issue

Actual Result:
Issue: Aria-label is not defined for "Remove" button under "Value mapping" dialog.
Observation: Screen reader is announcing as "Button" when focus moves to it.

Expected Result:
Aria-label should be defined for "Remove" button under "Value mapping" dialog.
_Note: Same issue exists with 'Copy" button under "Value mapping" dialog. Same issue appears for Explore->Query patterns. samw issue appears for alerting->alerting group_s

Issue:
Ensures buttons have discernible text (button-name - https://accessibilityinsights.io/info-examples/web/button-name)

Target application:
1 -Time series graphs - Grafana - https://play.grafana.org/d/000000016/1-time-series-graphs?orgId=1&editPanel=1&showCategory=Value%20mappings

Element path:
button[data-testid="remove-value-mapping"]

Snippet:
<button aria-label=""data-testid="remove-value-mapping" class="css-x1vujn">

How to fix:
Fix all of the following:

  • Element does not have inner text that is visible to screen readers
  • aria-label attribute does not exist or is empty
  • aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
  • Element has no title attribute
  • Element's default semantics were not overridden with role="none" or role="presentation"

Environment:
Microsoft Edge version 105.0.1329.1
This accessibility issue was found using Accessibility Insights for Web 2.32.0 (axe-core 4.4.1), a tool that helps find and fix accessibility issues.

Severity:

SEV2

Area:

Value Mappings Modal / IconButton Component (Saga Design System)

@grafanabot
Copy link
Contributor

@eledobleefe please add one or more appropriate labels. Here are some tips:

  • if you are making an issue, TODO, or reminder for yourself or your team, please add one label that best describes the product or feature area. Please also add the issue to your project board. 🚀

  • if you are making an issue for any other reason (docs typo, you found a bug, etc), please add at least one label that best describes the product or feature that you are discussing (e.g. area/alerting, datasource/loki, type/docs, type/bug, etc). Our issue triage doc also provides additional guidance on labeling. 🚀

Thank you! ❤️

@grafanabot grafanabot added the internal for issues made by grafanistas label Apr 12, 2023
@eledobleefe eledobleefe added area/frontend type/accessibility Accessibility problem / enhancement MAS labels Apr 12, 2023
@joshhunt
Copy link
Contributor

image

The two IconButtons (Copy and Remove) are missing labels. We should probably enforce this prop is added with Typescript and fix all issues accross the codebase

@eledobleefe
Copy link
Contributor Author

I investigated a bit more and, as Josh said, the IconButton has both tooltip and ariaLabel as optional. When there is no ariaLabel set, this props gets the value of the tooltip, but when there is also no tooltip value, the ariaLabel is an empty string.

As there is current work on improving the IconButton, it could be a good idea to add this a11y issue in the same PR.

@L-M-K-B L-M-K-B self-assigned this May 3, 2023
@ckbedwell ckbedwell added the wcag/4.1.2 UI components name and role can be programmatically determined. label Jun 5, 2023
@L-M-K-B L-M-K-B closed this as completed Jun 8, 2023
@L-M-K-B L-M-K-B reopened this Jun 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/frontend internal for issues made by grafanistas MAS type/accessibility Accessibility problem / enhancement wcag/4.1.2 UI components name and role can be programmatically determined.
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

5 participants