Kilotest: Diagnoses of tabindex positive violation by HTML element 107 on Rainforest Alliance page

Basics

About the page

• URL: https://www.rainforest-alliance.org/
• Tested 2 days ago on 2026-10-07 at 22:20 by job 261007T2157-b1t
• Summary of results:
  • Rule engines:
    • Called: 12
    • Were able to test: 11
    • Reported any rule violations: 10
  • Violations: 3228
  • Violators: 1565
  • Issues: 71
• Download the full technical report (JSON)

About the issue

• Why it matters: Keyboard-only user cannot predict the navigation sequence
• Priority: lowest
• Related WCAG standard: 2.4.3
• Reported by 1 rule engine (ASLint)
• Violations: 1
• Violators: 1

About the violator

• Tag name: DIV
• Text: ACCEPT ALL … SAVE SETTINGS
• Start tag: <div id="cookie-information-template-wrapper" style="display: block;">
• XPath: /html/body/div[1]
• Bounding box: x = 0, y = 0, width = 1920, height = 0
• Reported by ASLint

Diagnoses

Here is how rule engines diagnose the tabindex positive issue for HTML element 107 of the Rainforest Alliance page.

1. 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.

   Rule engine: ASLint (eSSENTIAL Accessibility)

   Rule: positive_tabindex