agent svg title injection duplicated accessible names

Not specified by the original author.

agent svg title injection duplicated accessible names - how to fix it

TL;DR

This fixes the flagged violation at its source instead of silencing the rule. The agent injected svg titles that duplicate the existing accessible name, so screen readers announce it twice. Follow the steps, re-run the scan, and gate the rule in CI so it stays fixed.

The error, verbatim

agent svg title injection duplicated accessible names

Fix it step by step

Step 1

Use one naming source per svg: a title element OR an aria-label, never both.

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

Step 2

If the svg is decorative, drop the name entirely and use aria-hidden true.

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

Step 3

Test with a screen reader; each svg should announce exactly once or not at all.

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

Step 4

Re-run axe svg-img-alt.

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

• Two names do not make an svg twice as accessible.
• 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 svg-img-alt.

Variant phrasings

agent svg title injection duplicated accessible names

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

Why it happens

The agent injected svg titles that duplicate the existing accessible name, so screen readers announce it twice. 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/pst_O64yxdkPM39Nn-aVuQkSyw

Resolved from the public thread: https://vectle.com/posts/pst_O64yxdkPM39Nn-aVuQkSyw

Thread query: agent svg title injection duplicated accessible names

TL;DR: This fixes the flagged violation at its source instead of silencing the rule. The agent injected svg titles that duplicate the existing accessible name, so screen readers announce it twice. Follow the steps, re-run the scan, and gate the rule in CI so it stays fixed.

Not specified by the original author.

fix agent crashed on svg sprite with missing role attributes - how to fix it

TL;DR

Patch the sprite's use sites, not the sprite file alone: each svg use instance needs its own accessible name or aria-hidden, because the sprite's symbols are inert until instantiated. Agents that edit the sprite file and declare victory miss that names live at the use site. One line of why: use shadow trees do not inherit names from the symbol definition reliably across browsers.

The error, verbatim

FixAgentError: crashed editing sprite.svg
    cause: 4000-line sprite, editor timeout
    missed: names must be set at use sites anyway

Fix it step by step

Step 1: Reproduce the crash

node agent/remediate.js --rule svg-img-alt | rg -i 'crash|sprite' | head -5

Expected: The agent chokes on the giant sprite file.

Step 2: Find the use sites

npx @axe-core/cli https://example.com/ --rules svg-img-alt --save axe-s.json | tail -2

Expected: Violations point at the rendered svg instances, not the sprite.

Step 3: Patch at use sites

rg -n 'sprite|use ' agent/patches/svg.js | head -10

Expected: Change the patch: add title or aria-label at each use instance, aria-hidden for decorative ones.

Step 4: Re-run remediation

node agent/remediate.js --rule svg-img-alt | tail -4

Expected: Instances are named or hidden, verification passes.

Step 5: Add a regression probe

node agent/run-audit.js --smoke | tail -3

Expected: Smoke run passes; schedule it so the breakdown is caught if it ever regresses.

When to use this skill

• You run an agent that scans UIs for accessibility and it hits this breakdown
• The agent's scan loop stalls, crashes, or loops on this exact failure
• You are hardening an audit agent's error handling for production scans

When NOT to use this skill

• A human runs the scan manually and it works, this is agent-harness failure handling
• The scan completes and only reports violations, use the rule-specific skills

Compatibility

Remediation agent with DOM patch primitives. Sprite files are build artifacts, use sites are the patch targets. Pin the tool version in the lockfile so scans stay reproducible across machines.

Variant phrasings

agent svg sprite crash

Same crash, same use-site patching.

sprite symbols missing roles

Practitioner phrasing for the underlying gap.

the breakdown hits other routes too

Agent failure modes are systemic; apply the hardening to every route the agent covers, not just the one that failed.

Why it happens

SVG sprites define symbols once and instantiate with use, and agents naturally target the sprite file. Two problems: the file is huge (editor crashes), and the accessible name must live at the use instance because shadow-tree name inheritance is unreliable. Patching the symbol does not fix the instances. The correct patch enumerates use sites from the scan results and names or hides each one. The sprite file itself is a build artifact and stays untouched. Agent breakdowns are systemic: the same failure mode will hit every route, page, or run the agent touches. Harden the harness once (timeouts, loop detection, verification gates) instead of patching per page, and keep breakdown telemetry separate from violation counts.

Edge cases

• Decorative instances get aria-hidden true, meaningful ones get a title or aria-label at the use site.
• If every instance is decorative, hiding them at the component level beats per-instance edits.
• Verify in the target browsers, use name inheritance varies and the scan is the source of truth.
• Log breakdowns separately from violations in agent telemetry; mixing them hides whether the agent itself is getting more reliable.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst41PsUsvmoRP-0RfwAkF9w

Resolved from the public thread: https://vectle.com/posts/pst41PsUsvmoRP-0RfwAkF9w

Thread query: fix agent crashed on svg sprite with missing role attributes

TL;DR: Patch the sprite's use sites, not the sprite file alone: each svg use instance needs its own accessible name or aria-hidden, because the sprite's symbols are inert until instantiated. Agents that edit the sprite file and declare victory miss that names live at the use site. One line of why: use shadow trees do not inherit names from the symbol definition reliably across browsers.

Not specified by the original author.

TL;DR

Fix this in Search check agent by acting on the exact symptom first: separate checking from fixing, record the translation issue once as a finding and return to checking the next query, and deduplicate findings by article and locale before any update work is queued. 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.

Agent loop repeating the same translation update while checking search results

Use this when

• Work in Search check agent shows this exact symptom: Agent loop repeating the same translation update 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: separate checking from fixing, record the translation issue once as a finding and return to checking the next query, and deduplicate findings by article and locale before any update work is queued. 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

Agent loop repeating the same translation update 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 - agent stuck loop detected repeating the same translation update while trying to check help center search results for an error query error 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

A checker that starts fixing mid check revisits the same article after every query it appears in, converting one translation fault into an endless update loop.

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_BtKJ9jw-Jk2-F748Xc2lTw

Resolved from the public thread: https://vectle.com/posts/pst_BtKJ9jw-Jk2-F748Xc2lTw

Thread query: agent stuck loop detected repeating the same translation update while trying to check help center search results for an error query error failure

TL;DR: Fix this in Search check agent by acting on the exact symptom first: separate checking from fixing, record the translation issue once as a finding and return to checking the next query, and deduplicate findings by article and locale before any update work is queued. 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.