Kilotest: Diagnoses of iframe not named violation by HTML element 70 on Portland City Club page

Basics

About the page

• URL: https://www.pdxcityclub.org/
• Tested 0 days ago on 2026-10-10 at 05:30 by job 261010T0528-evq
• Summary of results:
  • Rule engines:
    • Called: 12
    • Were able to test: 12
    • Reported any rule violations: 12
  • Violations: 718
  • Violators: 203
  • Issues: 53
• 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 1 rule engine (ASLint)
• Violations: 1
• Violators: 1

About the violator

• Tag name: BODY
• Text: [not applicable]
• Start tag: <body class="home wp-singular page-template page-template-page-templates page-template-pagebuilder page-template-page-templatespagebuilder-php page page-id-5 wp-custom-logo wp-embed-responsive wp-theme-flash siteorigin-panels siteorigin-panels-home tribe-js transparent header-sticky left-logo-right-menu full-width elementor-default elementor-kit-10392">
• XPath: /html/body
• Bounding box: x = 0, y = 50, width = 1920, height = 2809
• Reported by ASLint

Diagnoses

Here is how rule engines diagnose the iframe not named issue for HTML element 70 of the Portland City Club 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