Kilotest: Diagnoses of link 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 understanding what a link points to
• Priority: highest
• Related WCAG standard: 2.4.4
• Reported by 2 rule engines (Axe + SureA11y)
• Violations: 2
• Violators: 1

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 Axe + SureA11y

Diagnoses

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

1. Links must have discernible text; Element does not have text that is visible to screen readers; aria-label attribute does not exist or is empty; aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty; Element has an empty title attribute

   Rule engine: Axe (Deque)

   Rule: link-name

2. This link has no accessible name.

   Rule engine: SureA11y (Jorge Rumoroso)

   Rule: link-name-present