svg alt text error role img title element not read bug

Not specified by the original author.

axe-core svg-img-alt missing accessible name error - how to fix it

TL;DR

Give the svg an accessible name: a title element inside the svg, an aria-label on the svg, or mark it decorative with aria-hidden true. If the svg is the only content of a link or button, the svg needs the name. One line of why: svg with img role is announced like an image, and an image with no name is noise to a screen reader.

The error, verbatim

{
  "id": "svg-img-alt",
  "impact": "serious",
  "help": "svg elements with an img role must have an alternative text",
  "nodes": [
    { "target": [".logo-svg"], "failureSummary": "Fix any of the following: Element does not have an accessible name" }
  ]
}

Fix it step by step

Step 1: Reproduce on one page

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

Expected: Violations array contains svg-img-alt with the svg selectors.

Step 2: Check which svgs are meaningful vs decorative

rg -n --glob '*.{jsx,tsx,vue}' 'svg' src/components | head -30

Expected: A list of svg usages to triage: logos and icons that convey meaning need names, decorative flourishes get aria-hidden.

Step 3: Name the meaningful ones, hide the decorative ones

node -e "console.log('edit: add title or aria-label to meaningful svgs, aria-hidden true to decorative ones')"

Expected: Placeholder check that you touched the right files, the real verification is the re-scan.

Step 4: Re-scan

npx @axe-core/cli https://example.com --rules svg-img-alt

Expected: Exit code 0, 0 violations. Screen reader announces the logo name and skips the decorative svgs.

Step 5: Gate the rule in CI

npx @axe-core/cli https://example.com --exit | tail -3

Expected: Non-zero exit while any violation remains; add this command to CI so the fix never regresses.

When to use this skill

• Your axe-core report lists this exact rule id under violations
• You are clearing automated WCAG 2.1 AA failures before a release or audit
• A CI a11y gate (pa11y-ci, lighthouse CI, cypress-axe) is red because of this rule

When NOT to use this skill

• The issue only shows up in manual screen-reader testing and axe reports zero violations for the rule
• You are doing a full manual WCAG audit, this skill covers the single automated rule only
• The page is a third-party embed you cannot edit, flag it to the vendor instead

Compatibility

axe-core 4.8+ (rule svg-img-alt, WCAG 1.1.1). Same rule in axe DevTools, pa11y, and lighthouse v10+. Pin the tool version in the lockfile so scans stay reproducible across machines.

Variant phrasings

svg elements with an img role must have alternative text

The help text wording, same fix.

axe logo svg no accessible name

The classic instance: a linked logo svg with no title.

axe DevTools flags the same rule

The browser extension runs the same rule engine; fix once and it clears in every runner.

Why it happens

Inline svgs that carry role img (explicitly or via a link/button context) are treated as images, but unlike img elements they have no alt attribute convention, so authors forget the name entirely. Icon systems that sprite svgs with use elements are the worst offenders: the use shadow content rarely carries a title. Axe only flags svgs with an img role, so purely decorative inline svgs without a role pass silently, which is why teams are surprised when the rule fires on some svgs and not others. The same violation usually repeats on every page built from the same template, so fix the component or template once instead of patching pages. After the fix, re-scan the whole site, not just the one page, to confirm the template-level change cleared them all.

Edge cases

• A title element as the first child of svg is the most robust name across browsers, aria-label on svg works too but test your target browsers.
• svgs referenced by use inherit nothing automatically, put the title in the use instance or an aria-label on the use element.
• If the svg sits inside a button that already has an aria-label, mark the svg aria-hidden true so the name is not announced twice.
• Fix every instance of the rule before moving on; a half-fixed rule across templates re-fails the next full scan.

Provenance

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

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

Thread query: axe-core svg-img-alt missing accessible name error

TL;DR: Give the svg an accessible name: a title element inside the svg, an aria-label on the svg, or mark it decorative with aria-hidden true. If the svg is the only content of a link or button, the svg needs the name. One line of why: svg with img role is announced like an image, and an image with no name is noise to a screen reader.

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.

axe-core object-alt error object element missing alt text - how to fix it

TL;DR

An [object] element that embeds content needs a text alternative: either fallback content inside the element or an aria-label. Add descriptive fallback between the tags, for example [object data="/charts/q3.svg"]Q3 revenue chart: revenue grew 12%.[/object]. If the object embeds something interactive or essential, consider whether a native [img] with alt or inline SVG with a title would serve better.

In practice, the best fix for most object-alt violations is to stop using [object]. The element's fallback behavior was designed for plugin content (Flash, Java applets), and modern equivalents ([img], [video], inline [svg], [iframe]) all have better accessibility stories. Reserve [object] for the rare case where you genuinely need its nested-fallback behavior.

The verbatim error looks like this:

axe-core 4.x
Rule: object-alt (serious)
"Object elements must have alternate text"

Element: [object data="/charts/q3.svg" type="image/svg+xml"][/object]
  No alternate text or fallback content.

Steps

1. Reproduce with the single rule:

npx @axe-core/cli https://example.com/reports --rules object-alt

Expected: each object without alt text or fallback is listed.

2. Decide whether [object] is the right element. For a static image, [img alt="..."] is simpler and better supported. For SVG, inline [svg] with a [title] child is more accessible. Only keep [object] when you need its fallback behavior.
3. Add fallback content inside the element:

[object data="/charts/q3.svg" type="image/svg+xml"]
  Q3 revenue chart: revenue grew 12% quarter over quarter.
[/object]

Fallback content shows when the object fails to load AND serves as the text alternative.

4. Re-run the focused scan. Expected output: 0 violations for object-alt.
5. Test with the object source blocked (offline or 404) to confirm the fallback text actually renders.
6. Evaluate replacements before adding fallback text. For SVG: inline the [svg] with a [title] child. For images: use [img alt]. For documents: link to the file with descriptive link text instead of embedding it.
7. If [object] must stay, write fallback content that works as both a loading failure message and a text alternative. Test both: block the object URL and confirm the fallback renders, then check the accessible name with a screen reader.

When to use

• Axe flags object-alt on embedded objects.
• A page embeds SVG, PDF, or media via [object] with no fallback.
• Legacy content uses [object] for Flash-era embeds that were never updated.

When not to use

• The content is a static image (use [img] with alt instead).
• The content is decorative (question whether it should be embedded at all).
• The object embeds an entire application (that is closer to frame-title territory: name it and make the app itself accessible).

Why it happens

The [object] element predates modern embedding patterns, and its accessibility support is uneven across browsers. Fallback content inside the tags is the most reliable text alternative because it renders both when the resource fails and as the accessible name. Without it, assistive tech announces an empty embedded object.

[object] is a plugin-era element whose accessibility mappings were never as consistent as [img] or [iframe]. Browser vendors prioritized the elements developers actually use, so [object] got the least testing. The axe rule exists because authors keep reaching for [object] for SVG embedding out of old habit, even though inline SVG is better in every way.

Edge cases

• aria-label on [object] works in some browser/screen-reader combinations but fallback content is more robust. Use both if you must keep [object].
• An [object] with no data attribute and no content is dead markup. Remove it.
• PDF embeds via [object] need the PDF itself to be tagged and accessible; the fallback text is not a substitute for an accessible document.
• Nested [object] fallbacks (object inside object) are legal; keep each level's fallback meaningful.
• An [object] used for HTML embedding is essentially a worse [iframe]. Prefer [iframe] with a title.
• Fallback content inside [object] can itself contain links (for example, 'Download the PDF'), which is a legitimate and useful pattern.
• Empty [object] elements with no data attribute are dead code. Remove them; do not write fallback text for nothing.

Provenance

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

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

Thread query: axe-core object-alt error object element missing alt text

TL;DR: An [object] element that embeds content needs a text alternative: either fallback content inside the element or an aria-label. Add descriptive fallback between the tags, for example [object data="/charts/q3.svg"]Q3 revenue chart: revenue grew 12%.[/object]. If the object embeds something interactive or essential, consider whether a native [img] with alt or inline SVG with a title would serve better.