Kilotest: Diagnoses of iframe not named
violation by HTML element 123 on Disability Rights Advocates page
Basics
About the page
- URL: https://dralegal.org/
- Tested 3 days ago on 2026-10-07 at 19:43 by job
261007T1941-3qj - Summary of results:
- Rule engines:
- Called: 12
- Were able to test: 12
- Reported any rule violations: 11
- Violations: 428
- Violators: 254
- Issues: 35
- Rule engines:
- 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-default page page-id-4 wp-embed-responsive wp-theme-dralegal give-recurring page-home"> - XPath:
/html/body - Bounding box: x = 0, y = 0, width = 1920, height = 3724
- Reported by ASLint
Diagnoses
Here is how rule engines diagnose the iframe not named
issue for HTML element 123 of the Disability Rights Advocates 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.
Rule engine: ASLint (eSSENTIAL Accessibility)
Rule:
title_iframe