-
-
Notifications
You must be signed in to change notification settings - Fork 566
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
feat(a11y): make menu buttons in 'More' dropdown selectable with the keyboard #2976
Conversation
…keyboard previously, these were pure divs, without a `<button>` element, and could not be selected with `Tab`, rendering them keyboard-inaccessible.
✅ Deploy Preview for elk-zone ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for elk-docs canceled.
|
i am not sure why this thinks nothing changed; i tested it locally with |
can you update your main and merge changes in this PR? |
We should:
|
… keyboard previously, these were pure divs, without a `<button>` element, and could not be selected with `Tab`, rendering them keyboard-inaccessible.
126073a
to
e2bf34d
Compare
done :)
i mean the comment the github bot posted on this PR, that says the build was cancelled. maybe i'm misinterpreting it somehow, clearly the preview is showing up.
can you say more? i'm looking at the rendered button and i don't see any i glanced at DropdownItem but i don't see anything related to |
ohhhh that's for the docs, not for the live preview of the site. that makes more sense. |
Add this in the script setup:
Then add
|
We should use props destr. instead with defaults (enabled by default in vue 3.5) |
i added
i don't know what this means. |
56db899
to
8391459
Compare
the default is `type="submit"` which is semantically wrong and may cause the browser to try to submit a form.
oh wait apparently this started working again?? the only thing i changed was the order anyway, i've reverted this change, so now |
8391459
to
01946de
Compare
Use undefined instead null in the composable |
I Will fix this |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
previously, these were pure divs, without a
<button>
element, and could not be selected withTab
, rendering them keyboard-inaccessible.see also #2767 (cc @userquin). that uses a slightly different approach; it adds a disabled anchor instead of using buttons. i think this html is more semantically accurate, but i don't mind changing it if you so desire.
fixes #2974