Kilotest: Diagnoses of control not named violation by HTML element 212 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: BUTTON
• Text: [not applicable]
• Start tag: <button type="submit" class="tw:!inline-flex tw:!items-center tw:!justify-center tw:!px-4 tw:!h-[38px] tw:!transition-colors tw:!font-medium tw:sm:!text-sm tw:!shadow-sm tw:!text-white tw:!bg-blue-500 tw:!border tw:!border-blue-500 tw:hover:!bg-blue-600 tw:hover:!border-blue-600 tw:focus:!outline-none tw:focus:!ring-2 tw:focus:!ring-offset-2 tw:focus:!ring-blue-500 tw:!rounded-md tw:!rounded-tl-none tw:!rounded-bl-none">
• XPath: [not obtained]
• Bounding box: x = 1070, y = 66, width = 50, height = 38
• Reported by Accessibility Checker

Diagnoses

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

1. Form control element <button> has no associated label

   Rule engine: Accessibility Checker (IBM)

   Rule: input_label_exists