-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
a11y: Dropdown uses link rather than button as part of it's template #512
Comments
I'll let the @carbon-design-system/design part of the team weigh in regarding the UX, but I believe the We can update on our end if a |
@CptPilot , could you post a screenshot of what your use case looks like when using the Dropdown? |
Thanks for the pointer @tw15egan . Everyone had been referring to it as a dropdown in our design meetings that I hadn't spotted there was a Select component that meets our needs exactly. Apologies for the confusion, completely my fault. Closing. |
Happy to help 🙂 |
* chore(package): update lint-staged to version 6.0.1 * chore(package): update lockfile https://npm.im/greenkeeper-lockfile
…-design-system#512) * Update type tokens * chore(type): sync changes to sass
We've just moved to using Carbon for our UI and this was picked up by our accessibility tests that look for links where they shouldn't be.
Confirmed by the example, each option for the dropdown uses a link rather than a button
http://carbondesignsystem.com/components/dropdown/code
Given it's best practice to only use link as navigational elements rather than functional / form elements, can this be changed to be a button (we have now done so for our templates)
The text was updated successfully, but these errors were encountered: