Hey @osano - having some issue with your Cookie Consent banner. While I can highlight buttons via the keyboard, I can& #39;t actually "click" them by pressing enter (tested latest Firefox, Chrome, Edge - same result in all).

Can& #39;t raise an issue on GitHub about this either... https://abs.twimg.com/emoji/v2/... draggable="false" alt="🙁" title="Leicht stirnrunzelndes Gesicht" aria-label="Emoji: Leicht stirnrunzelndes Gesicht">
From my testing, it seems an anchor with no `href` attribute can& #39;t be submitted by a keyboard. With "revokable" setting enabled, you can& #39;t re-open the banner via the keyboard either though that uses a `div`.

If you switch to a button instead, keyboard is accessible again.
I wanted to a PR but I don& #39;t know what direction you want to go for supporting this or how to even handle the "revokable" button (as I can& #39;t switch that `div` to a `button` very easily).

If GitHub issues were enabled on the repo, this could be discussed there.
Repository for reference to anyone else seeing this thread: https://github.com/osano/cookieconsent

Accessibility">https://github.com/osano/coo... is important but it seems like this widely used library is missing some key pieces.
After going through your change log @osano, it does seem you& #39;ve fixed part of the problem with accessibility on the "allow" and "deny" buttons (not sure about the revoke button). I can& #39;t check v4 though as it hasn& #39;t been updated/uploaded to NPM and pushed to the CDN. https://abs.twimg.com/emoji/v2/... draggable="false" alt="đŸ€·â€â™‚ïž" title="Achselzuckender Mann" aria-label="Emoji: Achselzuckender Mann">
You can follow @MrTurnerj.
Tip: mention @twtextapp on a Twitter thread with the keyword “unroll” to get a link to it.

Latest Threads Unrolled: