Visible static iframe has no recognised name
ShipReady found one or more visible iframe elements in complete static HTML without a title or another recognised naming signal.
Why it matters
A short name can help a visitor understand the purpose of an embedded document such as a map or video.
How ShipReady detects it
What it inspects
On a successful, untruncated HTTP 200 page, ShipReady inspects static iframe start tags. It does not fetch or execute their embedded resources.
What triggers a finding
The rule triggers when an iframe has no title, aria-label, or aria-labelledby attribute and is not marked aria-hidden=true, hidden, display:none, visibility:hidden, or zero width or height under the scanner's static attribute checks.
What the evidence shows
The scanner observed one or more iframe elements that passed its visible-frame heuristic without a recognised naming attribute.
Limits of this check
ShipReady does not render CSS, execute JavaScript, inspect embedded content, determine whether a frame is useful to every visitor, or perform a complete accessibility audit.
How to fix it
Name meaningful embedded content
Add a concise title or other appropriate accessible name that describes the embed's purpose. Keep utility frames excluded from assistive technology when that is intentional.
How to verify the change
Review the deployed embedded experience
Inspect each affected frame in the served page and test representative embeds with accessibility tools.
Expected: Meaningful visible frames have a useful accessible name and intentionally hidden utility frames remain hidden.