Kilotest: Diagnoses of tabindex positive violation by HTML element 360 on Tisbest Philanthropy business inquiry page

Basics

About the page

• URL: https://www.tisbest.org/business-inquiry/
• Tested 2 days ago on 2026-10-07 at 23:24 by job 261007T2305-nh6
• Summary of results:
  • Rule engines:
    • Called: 12
    • Were able to test: 12
    • Reported any rule violations: 11
  • Violations: 2473
  • Violators: 1163
  • Issues: 55
• 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 3 rule engines (ASLint + Axe + Pour)
• Violations: 22
• Violators: 15

About the violator

• Tag name: DIV
• Text: – Please Select – … Other
• Start tag: <div class="ginput_container ginput_container_select">
• XPath: [not obtained]
• Bounding box: x = 976, y = 561, width = 296, height = 42
• Reported by ASLint

Take me there

Diagnoses

Here is how rule engines diagnose the tabindex positive issue for HTML element 360 of the Tisbest Philanthropy business inquiry page.

1. Positive <code>tabindex="29"</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