Inline SVGs lack accessible names, making them unreadable by screen readers and harming accessibility.
By Seoxpert Editorial · Published
SVGs are widely used for icons and illustrations. Without accessible names, screen readers can't describe their purpose, confusing users who rely on assistive technology. This impacts both accessibility compliance and user experience, and can indirectly affect SEO by reducing site usability.
Screen reader users may miss important information or become confused by SVGs without accessible names.
The issue is detected by scanning for inline <svg> elements missing a <title> child, aria-label, or aria-labelledby, and not marked aria-hidden="true".
Problem: SVG without accessible name
<svg width="24" height="24"><path d="..."/></svg>Fix: Add a <title> for meaningful SVG
<svg width="24" height="24"><title>Download</title><path d="..."/></svg>Fix: Use aria-label for meaningful SVG
<svg width="24" height="24" aria-label="Download"><path d="..."/></svg>Fix: Decorative SVG with aria-hidden
<svg width="24" height="24" aria-hidden="true" focusable="false"><path d="..."/></svg>If the SVG conveys information or meaning (like an icon or illustration), it needs an accessible name. If it's purely decorative, use aria-hidden="true".
Yes, aria-label on the <svg> is an acceptable alternative to a <title> for providing an accessible name.
Screen readers may skip the SVG or read its path data, confusing users and reducing accessibility.
role="img" is optional but can help clarify the SVG's purpose when paired with an accessible name.
Run a scan to see if Inline SVGs Missing Accessible Name affects your pages.
Scan my website →