The tabindex of 0 is not enough; this means that oftentimes these elements don't take precedence.

In our case a screen reader has to go through the entire homepage before encountering the cookie notice.

See attached patch.

Issue fork eu_cookie_compliance-3422687

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

  • 3422687 Comparecompare
About issue forks

Comments

wotts created an issue. See original summary.

wotts’s picture

wotts commented
Status: Active » Closed (won't fix)

cant figure out how to patch the correct minified js... :(

wotts’s picture

wotts commented
Status: Closed (won't fix) » Active

Re-opening in hopes that you can up the tabindex and create a new version with also correct minified js.

atowl’s picture

atowl commented

Hi @wotts,

If you modify the libraries file to look like 

eu_cookie_compliance:
  js:
    js/eu_cookie_compliance.js: { minified: false }

you can debug/change your tab index, then execute `npm run uglify` to get the minified output.
Or just add your change to the issue fork, and i can take care of the minification

kieran.cott’s picture

kieran.cott
Location 🇵🇭 Manila
commented

Hi @wotts,

Does the MR raised in https://www.drupal.org/project/eu_cookie_compliance/issues/3579992 address this issue, or are you still seeing the same behaviour when you apply the issue patch?