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

Explore Accessibility and labeling Options for AILabel Component #18241

Closed
1 task
2nikhiltom opened this issue Dec 11, 2024 · 2 comments
Closed
1 task

Explore Accessibility and labeling Options for AILabel Component #18241

2nikhiltom opened this issue Dec 11, 2024 · 2 comments

Comments

@2nikhiltom
Copy link
Contributor

2nikhiltom commented Dec 11, 2024

Originated in this slack thread while discussing about Accessible name does not match or contain the visible label text violation in AILabel (false pisitive)

Redundant ARIA labeling concern
The redundancy concern stems from the fact that the visible text ("AI Text goes here") within the button is already accessible and will be announced by screen readers as the button's accessible name. Specifying the same text again using the aria-label attribute creates duplication

Proposed Solution the thread discussion:
Refine the interaction and improve accessibility by introducing tooltips

  • Display a Tooltip on hover/focus of the button to provide additional information. This would make the content more discoverable and enhance the accessibility for users who rely on hover or focus events.
  • And still Maintain the existing Toggletip behavior for displaying more detailed information when the button is clicked or focused, ensuring that the button's functionality remains interactive and provides the necessary explainability when triggered.

Update label to AI explanation / AI details / AI info sinceAI as a button name is pretty scant

  • Explore more potential ideas/workarounds
Copy link
Contributor

Thank you for submitting a feature request. Your proposal is open and will soon be triaged by the Carbon team.

If your proposal is accepted and the Carbon team has bandwidth they will take on the issue, or else request you or other volunteers from the community to work on this issue.

@2nikhiltom
Copy link
Contributor Author

Closing this as the root cause of violation is fixed here.

@github-project-automation github-project-automation bot moved this from Triage to Completed 🚢 in Roadmap Jan 29, 2025
@github-project-automation github-project-automation bot moved this from ⏱ Backlog to ✅ Done in Design System Jan 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: ✅ Done
Status: Completed 🚢
Development

No branches or pull requests

2 participants