Kilotest: Diagnoses of iframe not named violation by HTML element 101 on Freedom House page

Basics

About the page

• URL: https://freedomhouse.org/
• Tested 3 days ago on 2026-10-07 at 21:42 by job 261007T2129-kjk
• Summary of results:
  • Rule engines:
    • Called: 12
    • Were able to test: 12
    • Reported any rule violations: 12
  • Violations: 1243
  • Violators: 363
  • Issues: 64
• 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: 3
• Violators: 2

About the violator

• Tag name: BODY
• Text: [not applicable]
• Start tag: <body class="path-frontpage page-node-type-page" data-aos-easing="ease" data-aos-duration="400" data-aos-delay="0" data-once="form-single-submit webform-single-submit">
• XPath: /html/body
• Bounding box: x = 0, y = 0, width = 1920, height = 6795
• Reported by ASLint

Diagnoses

Here is how rule engines diagnose the iframe not named issue for HTML element 101 of the Freedom House page.

1. Expected <code>title</code> attribute to be defined on <code>iframe</code>. However, if it is an <code>iframe</code> without valuable content for the user then add the attribute <code>aria-hidden="true"</code> in order to hide it from assistive technologies.

   Rule engine: ASLint (eSSENTIAL Accessibility)

   Rule: title_iframe