Kilotest: Diagnoses of iframe not named
violation by HTML element 69 on Russellville Park page
Basics
About the Russellville Park page
- URL: https://russellvillepark.com/
- Tested 11 days ago by job
kyqon 2026-05-21 at 23:58
About HTML element 69
- Tag name:
BODY - Text: [not applicable]
- Start tag:
<body class="home wp-singular page-template-default page page-id-15 wp-custom-logo wp-embed-responsive wp-theme-kadence wp-child-theme-kadence-child footer-on-bottom hide-focus-outline link-style-standard content-title-style-hide content-width-fullwidth content-style-unboxed content-vertical-padding-hide transparent-header mobile-transparent-header" data-aos-easing="ease" data-aos-duration="400" data-aos-delay="0"> - XPath:
/html/body - Bounding box: x = 0, y = 0, width = 1920, height = 3212
About the iframe not named
issue
- Why it matters: User cannot get help on the topic of an embedded document
- Priority: highest
- Related WCAG standard: 4.1.2
Diagnoses
Here is how tools diagnose the iframe not named
issue for HTML element 69 of the Russellville Park page.
- 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.
Tool: ASLint (eSSENTIAL Accessibility)
Rule:
title_iframe