Kilotest: Diagnoses of input not named violation by HTML element 505 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 what information to enter in a form item
• Priority: highest
• Related WCAG standard: 4.1.2
• Reported by 1 rule engine (HTML CodeSniffer)
• Violations: 3
• Violators: 3

About the violator

• Tag name: INPUT
• Text: Select State … b
• Start tag: <input class="tw-relative tw-w-full tw-inline-flex tw-justify-between tw-cursor-default tw-border tw-text-gray-800 tw-bg-white tw-py-2 tw-px-4 tw-text-left tw-shadow-sm focus:blue-400 tw-text-sm tw-rounded-md tw-border-gray-500" id="select-states" role="combobox" type="text" aria-expanded="false" aria-autocomplete="list" data-headlessui-state="" style="">
• XPath: /html/body/div[3]/div[1]/div[3]/div[2]/div[2]/div[4]/div[1]/div[1]/input[1]
• Bounding box: x = 1119, y = 302, width = 246, height = 38
• Reported by HTML CodeSniffer

Diagnoses

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

1. This textinput element does not have a name available to an accessibility API. Valid names are: label element, title attribute, aria-label attribute, aria-labelledby attribute.

   Rule engine: HTML CodeSniffer (Squiz Labs)

   Rule: E-WCAG2AAA.Principle4.Guideline4_1.4_1_2.H91.InputText.Name