Kilotest: Diagnoses of button not named violation by HTML element 166 on Fair Vote contact page

Basics

About the page

• URL: https://fairvote.org/get-involved/contact-us/
• Tested 3 days ago on 2026-10-07 at 21:16 by job 261007T2112-oje
• Summary of results:
  • Rule engines:
    • Called: 12
    • Were able to test: 12
    • Reported any rule violations: 11
  • Violations: 409
  • Violators: 246
  • Issues: 48
• Download the full technical report (JSON)

About the issue

• Why it matters: User cannot get help explaining a button
• Priority: highest
• Related WCAG standard: 4.1.2
• Reported by 2 rule engines (HTML CodeSniffer + WAVE)
• Violations: 10
• Violators: 5

About the violator

• Tag name: BUTTON
• Text: News & AnalysisRead press releases, blogs, and media coverage on FairVote and our flagship reforms. … Editorial SupportOpinion & AnalysisPress ReleasesRCV Ballot MeasuresRCV Legislation
• Start tag: <button class="btn-open-submenu text-white absolute right-0 top-0 w-[68px] h-[68px] text-center" data-v-6af95c07="">
• XPath: /html/body/div[1]/header[1]/div[1]/div[2]/nav[1]/ul[1]/li[3]/button[1]
• Bounding box: [not obtained]
• Reported by HTML CodeSniffer + WAVE

Take me there

Diagnoses

Here is how rule engines diagnose the button not named issue for HTML element 166 of the Fair Vote contact page.

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

   Rule engine: HTML CodeSniffer (Squiz Labs)

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

2. Empty button

   Rule engine: WAVE (Utah State University)

   Rule: button_empty