Kilotest: Diagnoses of invalid landmark child of navigation role violation by HTML element 104 on Sightsavers contact page

Basics

About the page

• URL: https://www.sightsavers.org/contact-us/
• Tested 3 days ago on 2026-10-07 at 22:09 by job 261007T2147-2zs
• Summary of results:
  • Rule engines:
    • Called: 12
    • Were able to test: 12
    • Reported any rule violations: 11
  • Violations: 574
  • Violators: 268
  • Issues: 56
• Download the full technical report (JSON)

About the issue

• Why it matters: User cannot get help on how some of the page is organized
• Priority: highest
• Related WCAG standard: 1.3.6
• Reported by 1 rule engine (ASLint)
• Violations: 2
• Violators: 2

About the violator

• Tag name: NAV
• Text: Type search term here … }
• Start tag: <nav class="c-nav-mobile" role="navigation" aria-hidden="true">
• XPath: /html/body/header[1]/div[1]/div[1]/div[1]/nav[1]
• Bounding box: [not obtained]
• Reported by ASLint

Take me there

Diagnoses

Here is how rule engines diagnose the invalid landmark child of navigation role issue for HTML element 104 of the Sightsavers contact page.

1. This element must only contain <code>region</code> or <code>search</code> landmarks.

   Rule engine: ASLint (eSSENTIAL Accessibility)

   Rule: navigation_landmark_restrictions