fix agent crashed on svg sprite with missing role attributes

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.