Kilotest: Diagnoses of button not named violation by HTML element 256 on Freedom Forum contact page

Basics

About the page

• URL: https://www.freedomforum.org/contact-us/
• Tested 3 days ago on 2026-10-07 at 21:31 by job 261007T2113-pny
• Summary of results:
  • Rule engines:
    • Called: 12
    • Were able to test: 12
    • Reported any rule violations: 12
  • Violations: 399
  • Violators: 164
  • Issues: 51
• 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 4 rule engines (Alfa + HTML CodeSniffer + Pour + SureA11y)
• Violations: 4
• Violators: 2

About the violator

• Tag name: A
• Text: [not applicable]
• Start tag: <a itemprop="sameAs" href="https://twitter.com/1stForAll/" target="_blank" title="" aria-label="" role="button" rel="noopener noreferrer external">
• XPath: [not obtained]
• Bounding box: x = 360, y = 1312, width = 30, height = 30
• Reported by HTML CodeSniffer + Pour + SureA11y

Diagnoses

Here is how rule engines diagnose the button not named issue for HTML element 256 of the Freedom Forum contact page.

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

   Rule engine: HTML CodeSniffer (Squiz Labs)

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

2. Buttons must have an accessible name

   Rule engine: Pour (David Yarham and Geoffrey Crofte)

   Rule: button-name

3. This button has no accessible name.

   Rule engine: SureA11y (Jorge Rumoroso)

   Rule: button-name-present