Kilotest: Diagnoses of control not named violation by HTML element 485 on Charity Navigator search page

Basics

About the page

• URL: https://www.charitynavigator.org/search
• Tested 3 days ago on 2026-10-07 at 19:48 by job 261007T1941-dku
• Summary of results:
  • Rule engines:
    • Called: 12
    • Were able to test: 12
    • Reported any rule violations: 12
  • Violations: 1528
  • Violators: 476
  • Issues: 67
• Download the full technical report (JSON)

About the issue

• Why it matters: User cannot get help on how to operate a form item
• Priority: highest
• Related WCAG standard: 1.3.1
• Reported by 7 rule engines (Accessibility Checker + Alfa + Axe + HTML CodeSniffer + Pour + QualWeb + WAVE)
• Violations: 20
• Violators: 7

About the violator

• Tag name: INPUT
• Text: [not applicable]
• Start tag: <input type="text" class="search" placeholder="Select Cause(s)" aria-autocomplete="list" style="">
• XPath: /html/body/div[3]/div[1]/div[3]/div[2]/div[2]/div[1]/div[1]/div[1]/a[1]/ul[1]/li[1]/input[1]
• Bounding box: x = 285, y = 302, width = 270, height = 38
• Reported by HTML CodeSniffer + Pour + WAVE

Diagnoses

Here is how rule engines diagnose the control not named issue for HTML element 485 of the Charity Navigator search page.

1. This form field should be labelled in some way. Use the label element (either with a "for" attribute or wrapped around the form field), or "title", "aria-label" or "aria-labelledby" attributes as appropriate.

   Rule engine: HTML CodeSniffer (Squiz Labs)

   Rule: E-WCAG2AAA.Principle1.Guideline1_3.1_3_1.F68

2. Every form field needs a label

   Rule engine: Pour (David Yarham and Geoffrey Crofte)

   Rule: form-label

3. Missing form label

   Rule engine: WAVE (Utah State University)

   Rule: label_missing