Kilotest: Diagnoses of iframe not named violation by HTML element 405 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 on the topic of an embedded page
• Priority: highest
• Related WCAG standard: 4.1.2
• Reported by 3 rule engines (Accessibility Checker + ASLint + HTML CodeSniffer)
• Violations: 5
• Violators: 3

About the violator

• Tag name: IFRAME
• Text: Skip to content … © 2026 Freedom Forum
• Start tag: <iframe id="bugherd_embed_communication_frame" name="embedCommunication" sandbox="allow-scripts allow-popups allow-same-origin allow-popups-to-escape-sandbox allow-storage-access-by-user-activation" src="https://sidebar.bugherd.com/sidebar/embed_html?apikey=fekvc9fgxnkordetkfxifg" style="display: none; border-width: medium; border-style: none; border-color: currentcolor; border-image: none; position: fixed; z-index: 2147483647; right: 0px; height: 144px; width: 330px; top: calc(100% - 154px);">
• XPath: /html/body/iframe[2]
• Bounding box: [not obtained]
• Reported by HTML CodeSniffer

Diagnoses

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

1. Iframe element requires a non-empty title attribute that identifies the frame.

   Rule engine: HTML CodeSniffer (Squiz Labs)

   Rule: E-WCAG2AAA.Principle2.Guideline2_4.2_4_1.H64.1