Kilotest: Diagnoses of tabindex positive violation by HTML element 525 on Water for People contact page

Basics

About the page

• URL: https://www.waterforpeople.org/contact-us/
• Tested 3 days ago on 2026-10-07 at 23:11 by job 261007T2305-6zv
• Summary of results:
  • Rule engines:
    • Called: 12
    • Were able to test: 12
    • Reported any rule violations: 12
  • Violations: 864
  • Violators: 314
  • 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 3 rule engines (ASLint + Axe + Pour)
• Violations: 22
• Violators: 17

About the violator

• Tag name: SPAN
• Text: First
• Start tag: <span id="input_2_1_3_container" class="name_first gform-grid-col gform-grid-col--size-auto">
• XPath: [not obtained]
• Bounding box: x = 450, y = 1468, width = 500, height = 107
• Reported by ASLint

Diagnoses

Here is how rule engines diagnose the tabindex positive issue for HTML element 525 of the Water for People contact page.

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

   Rule engine: ASLint (eSSENTIAL Accessibility)

   Rule: positive_tabindex