Kilotest: Diagnoses of button not named violation by HTML element 1024 on Open Secrets page

Basics

About the page

• URL: https://www.opensecrets.org/
• Tested 3 days ago on 2026-10-07 at 19:57 by job 261007T1941-pfb
• Summary of results:
  • Rule engines:
    • Called: 12
    • Were able to test: 12
    • Reported any rule violations: 12
  • Violations: 2429
  • Violators: 1331
  • Issues: 75
• 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 6 rule engines (Alfa + Axe + HTML CodeSniffer + Pour + QualWeb + SureA11y)
• Violations: 17
• Violators: 11

About the violator

• Tag name: BUTTON
• Text: Uncover lobbying efforts
• Start tag: <button name="" type="button" class="dc-btn dc-btn__small-icon-only dc-btn--light dc-btn--borderless">
• XPath: /html/body/div[4]/div[2]/div[1]/div[1]/div[1]/ul[1]/li[9]/div[1]/a[1]/button[1]
• Bounding box: x = 1524, y = 1442, width = 46, height = 38
• Reported by Pour + QualWeb + SureA11y

Diagnoses

Here is how rule engines diagnose the button not named issue for HTML element 1024 of the Open Secrets page.

1. Buttons must have an accessible name

   Rule engine: Pour (David Yarham and Geoffrey Crofte)

   Rule: button-name

2. [failed] The test target doesn't have an accessible name, or it's empty ('').

   Rule engine: QualWeb (University of Lisbon)

   Rule: QW-ACT-R11

3. This button has no accessible name.

   Rule engine: SureA11y (Jorge Rumoroso)

   Rule: button-name-present