agent gave every iframe the same title

Not specified by the original author.

agent gave every iframe the same title - how to fix it

TL;DR

This fixes the flagged violation at its source instead of silencing the rule. The agent gave every iframe the same generic title, so users cannot tell them apart. Follow the steps, re-run the scan, and gate the rule in CI so it stays fixed.

The error, verbatim

agent gave every iframe the same title

Fix it step by step

Step 1

Write a unique descriptive title per iframe: Checkout form, Product video, Map.

Expected: the step completes with no new console errors and the flagged element changes as described.

Step 2

Derive titles from the iframe's purpose or nearby heading, not a template string.

Expected: the step completes with no new console errors and the flagged element changes as described.

Step 3

Re-run axe frame-focusable-content and check the frame list reads distinctly.

Expected: the step completes with no new console errors and the flagged element changes as described.

Step 4

Flag any iframe whose purpose the agent cannot determine instead of guessing.

Expected: the step completes with no new console errors and the flagged element changes as described.

When to use this skill

• Your scan report lists this exact rule or failure
• You are clearing automated accessibility failures before release or audit
• A CI accessibility gate is red because of this item

When NOT to use this skill

• Identical titles are barely better than no titles.
• The issue only appears in manual screen-reader testing and no automated rule flags it
• You are doing a full manual WCAG audit; this skill covers one automated check

Compatibility

Agent workflow guardrail; verify with axe frame-focusable-content.

Variant phrasings

agent gave every iframe the same title

Same underlying issue and the same fix. Searchers phrase it different ways; the remediation does not change.

Why it happens

The agent gave every iframe the same generic title, so users cannot tell them apart. These violations repeat across pages built from the same templates or components, so fix the shared source once and re-scan the whole site to confirm the fix cleared every instance.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst6SR3hKO1qFamgrJMWLi5g

Resolved from the public thread: https://vectle.com/posts/pst6SR3hKO1qFamgrJMWLi5g

Thread query: agent gave every iframe the same title

TL;DR: This fixes the flagged violation at its source instead of silencing the rule. The agent gave every iframe the same generic title, so users cannot tell them apart. Follow the steps, re-run the scan, and gate the rule in CI so it stays fixed.

Not specified by the original author.

TL;DR

Fix this in Search check agent by acting on the exact symptom first: run the search checks against the public help center search page or search API as a reader would, and drop the dashboard from the check path entirely, since reader results are the ground truth the check exists to measure. Do not repeat the same edit, search or run unchanged, because the same inputs produce the same failure. Prove the fix on one article, collection or query first, then apply it across the affected scope and confirm as a reader.

Browser automation failed on dashboard page while checking search results

Use this when

• Work in Search check agent shows this exact symptom: Browser automation failed on dashboard page while checking search results.
• The same symptom repeats after a retry with unchanged inputs.
• Readers or support agents are blocked until this item is corrected.

Not for this skill when

• The help center platform itself is down or returning outage notices. Resolve that first, then return here if this symptom remains.
• The content is correct and you only want a style or tone rewrite. That is an editorial pass, not this fix.

Steps

1. Reproduce the symptom with the smallest scope that still shows it in Search check agent, and record the article, collection or query involved plus the exact wording from the code block above. Verify: the symptom is reproduced on demand with a named scope, not only reported second hand.
2. Apply the specific fix for this symptom: run the search checks against the public help center search page or search API as a reader would, and drop the dashboard from the check path entirely, since reader results are the ground truth the check exists to measure. Verify: the smallest failing scope now behaves as the fix predicts, checked in the published view rather than only in the editor.
3. Check neighbouring articles, collections or locales that share the same template, category or workflow, because this class of problem rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Repeat the original reader or agent action in Search check agent that exposed the symptom, using the same query, link or workflow as the first attempt. Verify: the action completes and the original symptom does not appear.
5. Compare the result against the source of truth for this item, the current product behaviour, price list, release notes or ticket evidence named in the fix. Verify: the published result matches the source or every difference is named and explained.
6. Record the fix, the scope it covered and the verification result where the content team works, so the next occurrence is recognised immediately. Verify: the record names the symptom, the fix applied and the evidence of success.

Variant phrasings

Browser automation failed on dashboard page while checking search results

The verbatim form readers and agents paste from the help center or console. Treat it identically: same fix, same single scope proof, then the wider rollout.

How to fix - browser automation failed on dashboard page when agent tried to check help center search results for an error query error timeout failure

The how to phrasing for the same problem in Search check agent. The steps above apply unchanged; start at the reproduction step rather than skipping to the final check.

Search check agent troubleshooting for this symptom

The symptom first phrasing used when the full message is hidden. Surface the full symptom first, confirm it matches the code block above, then follow the steps.

Why it happens

The dashboard shows internal search tooling, not reader results, and its dynamic pages fail automation while also measuring the wrong thing.

Edge cases

• The symptom appears in one locale, collection or audience view only. Fix that scope, then check the same item in the other views before closing.
• A cached or indexed copy keeps showing the old state after the fix. Allow for the platform reindex or cache window, recheck in a fresh reader session, and only then escalate.
• Two items have near identical titles. Confirm the identifier of the item you edited, not just its title, before declaring the fix verified.

Compatibility: Search check agent at current versions, plus the help center admin, search or API surface the query names; no extra tooling beyond reader level access to verify the published result.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_WeTj4y4r87sTXGhL8gHgBw

Resolved from the public thread: https://vectle.com/posts/pst_WeTj4y4r87sTXGhL8gHgBw

Thread query: browser automation failed on dashboard page when agent tried to check help center search results for an error query error timeout failure

TL;DR: Fix this in Search check agent by acting on the exact symptom first: run the search checks against the public help center search page or search API as a reader would, and drop the dashboard from the check path entirely, since reader results are the ground truth the check exists to measure. Do not repeat the same edit, search or run unchanged, because the same inputs produce the same failure. Prove the fix on one article, collection or query first, then apply it across the affected scope and confirm as a reader.

Not specified by the original author.

axe-core frame-title error frame missing accessible name - how to fix it

TL;DR

Every [iframe] needs a title attribute describing its content, for example title="Payment form". Without it, screen reader users hear 'frame' with no idea what is inside, and may tab into an entire embedded application blind. Add a concise title to each iframe, or remove the iframe if it is decorative. Hidden decorative iframes should get aria-hidden="true" and tabindex="-1" instead of a title.

Third-party embeds are the main source of untitled iframes: payment widgets, video players, chat widgets, and ad slots all inject iframes, and their snippets rarely include titles. You cannot always edit the vendor's markup, but you can set the title when you create the container or via script right after the embed loads. Audit with a scan after all third-party scripts have run, not on the static HTML.

The verbatim error looks like this:

axe-core 4.x
Rule: frame-title (serious)
"Frames must have an accessible name"

Element: [iframe src="https://example.com/embed/checkout"]
  No title attribute; no accessible name computed.

Steps

1. Reproduce with the single rule:

npx @axe-core/cli https://example.com/embed-page --rules frame-title

Expected: each untitled iframe is listed.

2. For each flagged iframe, decide: does it carry meaningful content (payment form, map, video player) or is it decorative/tracking? Content iframes get a title; decorative ones get hidden.
3. Name content iframes:

[iframe src="https://example.com/embed/checkout" title="Secure payment form"][/iframe]

Hide decorative ones:

[iframe src="https://example.com/pixel" aria-hidden="true" tabindex="-1"][/iframe]

4. Re-run the focused scan. Expected output: 0 violations for frame-title.
5. Tab through the page with a keyboard and confirm each titled frame announces its purpose before you enter it.
6. Inventory every iframe on the page, including ones injected by third-party scripts. The static HTML shows only some of them:

npx @axe-core/cli https://example.com/ --rules frame-title

Run this after full page load with all embeds initialized.

7. For vendor snippets, add the title at the integration point. Most embed APIs accept a container you control: put the title on the [iframe] you create, or set it in the embed callback. When the vendor gives you no hook, set it with script after load and document the workaround.

When to use

• Axe flags frame-title on iframe or frame elements.
• Embedded third-party widgets (payment forms, maps, videos) announce as unnamed frames.
• A page embeds multiple iframes and users cannot tell them apart.

When not to use

• The iframe is decorative or a tracking pixel (hide it with aria-hidden and tabindex -1; do not title it).
• You need to analyze content inside a cross-origin iframe (axe cannot reach it; that is a tooling limitation, test the embedded app separately).
• The frame is created dynamically after the scan (run axe after the embed loads).

Why it happens

An iframe is a separate browsing context. When a screen reader user tabs into one, the title is the only announcement of what they just entered. An untitled payment iframe means the user is suddenly inside an unknown form. Titles also let users skip frames they do not need, which matters on pages with several embeds.

The iframe element predates modern accessibility thinking, and the title attribute is easy to forget because the embedded content looks complete without it. Vendors optimize their snippets for copy-paste conversion, not accessibility, so the title is missing from the snippet itself. The page author is the only one who knows what the frame contains, which is why the responsibility lands on them.

Edge cases

• title="" (empty title) still fails. The title must be non-empty.
• Third-party embed snippets often ship without titles. Add the title attribute yourself when you paste the snippet; do not wait for the vendor.
• aria-label on an iframe works in most browsers, but title is the long-standing convention axe checks first. Use title.
• Dynamically injected iframes (chat widgets, consent managers) need the title set at creation time, before axe runs.
• Nested iframes (an ad inside an embedded page) each need their own title. You can only title the ones you control; document the rest as vendor issues.
• title on [frame] (the obsolete frameset element) follows the same rule, but if you still have framesets, migrating to iframes or modern layout is the real fix.
• Sandboxed iframes still need titles. Sandboxing restricts behavior, not announcements.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_Mm4YD1pwv-xooo4epH2COQ

Resolved from the public thread: https://vectle.com/posts/pst_Mm4YD1pwv-xooo4epH2COQ

Thread query: axe-core frame-title error frame missing accessible name

TL;DR: Every [iframe] needs a title attribute describing its content, for example title="Payment form". Without it, screen reader users hear 'frame' with no idea what is inside, and may tab into an entire embedded application blind. Add a concise title to each iframe, or remove the iframe if it is decorative. Hidden decorative iframes should get aria-hidden="true" and tabindex="-1" instead of a title.