Kilotest: Diagnoses of iframe not named violation by HTML element 876 on 350 Sacramento page

Here is how tools diagnose the iframe not named issue for HTML element 876 of the 350 Sacramento page.

Basics

• 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
• About the 350 Sacramento page
  • URL: https://350sacramento.org/
  • Tested on 2026-04-02 at 14:10
• About HTML element 876
  • Take me there
  • Tag name: IFRAME
  • Text: Skip to main content … tiktok
  • Start tag: <iframe height="1" width="1" style="position: absolute; top: 0px; left: 0px; border-width: medium; border-style: none; border-color: currentcolor; border-image: initial; visibility: hidden;">
  • XPath: /html/body/iframe[1]
  • Bounding box: x = 0, y = 0, width = 1, height = 1

Diagnoses

1. Iframe element requires a non-empty title attribute that identifies the frame.

   Tool: HTML CodeSniffer (Squiz Labs)

   Rule: E-WCAG2AAA.Principle2.Guideline2_4.2_4_1.H64.1

2. Inline frame does not have a 'title' attribute

   Tool: Accessibility Checker (IBM)

   Rule: frame_title_exists

3. Iframe element requires a non-empty title attribute that identifies the frame.

   Tool: WallyAX (Wally)