Some elements have a [tabindex] value greater than 0

Just noticed the same issue with axe DevTools. It’s classified as ‘serious’.

Hi @andresgs @huubl

The [tabindex] 0 was created as many users have asked us to do that due the accessibility requirements.

However, we will add an option to the banner settings screen where you can switch off this feature and get rid of the Google page speed warning.

The update will be released early next week.

Hope this helps.

Hi @huubl @andresgs

This is done, please update the plugin to the latest version.

We have implemented a new Accessibility setting on this screen:
https://www.dropbox.com/s/v4szss16lyohjj8/screenshot-14.png?dl=0

The default is ‘Content’ which will remove the “[tabindex] value greater than 0” warning on Google Page Speed insights.

Hope this helps.

Hello, I have the latest WordPress updated 6.1 and we are using the Accessible Web Helper tool with our account with Accessible Web, on our one site this is flagged to resolve.

Elements should not have tabindex greater than zero
SERIOUS · BEST PRACTICE
Ensures tabindex attribute values are not greater than 0.

Highlight All 1 Elements
Highlight elementSkip to toolbar
<a class="screen-reader-shortcut" href="#wp-toolbar" tabindex="1">Skip to toolbar</a>
Failure Details
Element has a tabindex greater than 0

This is in the /wp-includes/class-wp-admin-bar.php
Also, we have All page content should be contained by landmarks issues with Skip to toolbar and Log Out

https://snipboard.io/XIoauq.jpg

Any way to resolve this or is there a work around to get this resolved for WCAG compliant?

Hi @jflds

We have implemented a new Accessibility setting on this screen:
https://www.dropbox.com/s/v4szss16lyohjj8/screenshot-14.png?dl=0

The default is ‘Content’ but you can switch it to “Cookie Banner” for WCAG requirements.

If this is not what you were looking for, please create a new ticket on this forum as this ticket is related to this feature.

Hope this helps.

I apologize when I search for this issue, I didn’t realize it was in this plugin support. We are not using this plugin. I believe it may be in the WordPress core issue? I will create a new ticket. Thanks.