Kilotest: Diagnoses of Tab-focusable elements wrong violation by HTML element 110 on DEPLOY/US more ways to give page

Basics

About the page

• URL: https://www.deployus.org/more-ways-to-give
• Tested 3 days ago on 2026-10-07 at 21:12 by job 261007T2109-z9l
• Summary of results:
  • Rule engines:
    • Called: 12
    • Were able to test: 12
    • Reported any rule violations: 11
  • Violations: 172
  • Violators: 75
  • Issues: 27
• Download the full technical report (JSON)

About the issue

• Why it matters: Item selections by a keyboard-only user are useless or impossible
• Priority: highest
• Related WCAG standard: 2.1.1
• Reported by 1 rule engine (Testaro)
• Violations: 4
• Violators: 4

About the violator

• Tag name: A
• Text: LATEST UPDATES
• Start tag: <a href="/latest-updates">
• XPath: /html/body/div[4]/header[1]/div[1]/div[4]/div[1]/nav[1]/div[2]/div[2]/div[2]/a[1]
• Bounding box: x = 1338, y = 63, width = 226, height = 0
• Reported by Testaro

Take me there

Diagnoses

Here is how rule engines diagnose the Tab-focusable elements wrong issue for HTML element 110 of the DEPLOY/US more ways to give page.

1. Element was reached by Tab navigation but was not a visible focusable element

   Rule engine: Testaro (CVS Health)

   Rule: focAll