Read on Twitter
Hey @osano - having some issue with your Cookie Consent banner. While I can highlight buttons via the keyboard, I can't actually "click" them by pressing enter (tested latest Firefox, Chrome, Edge - same result in all).
Can't raise an issue on GitHub about this either...
Can't raise an issue on GitHub about this either...
From my testing, it seems an anchor with no `href` attribute can't be submitted by a keyboard. With "revokable" setting enabled, you can'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.
If you switch to a button instead, keyboard is accessible again.
I wanted to a PR but I don't know what direction you want to go for supporting this or how to even handle the "revokable" button (as I can't switch that `div` to a `button` very easily).
If GitHub issues were enabled on the repo, this could be discussed there.
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 is important but it seems like this widely used library is missing some key pieces.
Accessibility 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've fixed part of the problem with accessibility on the "allow" and "deny" buttons (not sure about the revoke button). I can't check v4 though as it hasn't been updated/uploaded to NPM and pushed to the CDN. 
To add to it, your own consent builder on this page uses the older v3 version: https://www.osano.com/cookieconsent/download/
