Kilotest: Diagnoses of tabindex positive violation by HTML element 950 on Sightline Institute page

Here is how tools diagnose the tabindex positive issue for HTML element 950 of the Sightline Institute page.

Basics

About the tabindex positive issue
- Why it matters: Keyboard-only user cannot predict the navigation sequence
- Priority: lowest
- Related WCAG standard: 2.4.3
About the Sightline Institute page
- URL: https://www.sightline.org/
- Tested on 2026-04-03 at 04:04
About HTML element 950
- Take me there
- Tag name: DIV
- Text: Okay … Close GDPR Cookie Banner
- Start tag: <div class="moove-gdpr-button-holder">
- XPath: /html/body/aside[1]/div[1]/div[1]/div[2]
- Bounding box: x = 0, y = 0, width = 0, height = 0

Positive <code>tabindex="1"</code> should not be used. Outside of very specific corner cases, a tabindex should not be given a positive integer value. Users who use keyboards to interact with the web expect a web document to be navigable in sequential order, starting at the top left (or right depending on language of the document) and going in order from there.
Tool: ASLint (eSSENTIAL Accessibility)

Rule: positive_tabindex
Positive <code>tabindex="2"</code> should not be used. Outside of very specific corner cases, a tabindex should not be given a positive integer value. Users who use keyboards to interact with the web expect a web document to be navigable in sequential order, starting at the top left (or right depending on language of the document) and going in order from there.
Tool: ASLint (eSSENTIAL Accessibility)

Rule: positive_tabindex
Positive <code>tabindex="3"</code> should not be used. Outside of very specific corner cases, a tabindex should not be given a positive integer value. Users who use keyboards to interact with the web expect a web document to be navigable in sequential order, starting at the top left (or right depending on language of the document) and going in order from there.
Tool: ASLint (eSSENTIAL Accessibility)

Rule: positive_tabindex