Accessibility audit of name.com — scanned on Feb 20, 2026
Technology5 issues found across 2 categories
Links must have discernible text so screen reader users understand their purpose.
WCAG 2.4.4<a href="/"><a href="/">Add text content, aria-label, or aria-labelledby to links. Avoid empty <a> tags.
Form elements must have associated labels so users know what information to enter.
WCAG 1.3.1<input type="text" name="(no name)">Add <label> elements with matching for attributes, or use aria-label.
Buttons must have discernible text for screen reader users.
WCAG 4.1.2<button>Add text content, aria-label, or title to all <button> elements.
Iframes must have title attributes describing their content.
WCAG 2.4.1<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-T7VNSFS">Add descriptive title attributes to all <iframe> elements.
ARIA attributes must be valid and used correctly to work with assistive technologies.
WCAG 4.1.2<div aria-labelledby="n-expand-v-2-0-0"> (missing ref)<div aria-labelledby="n-expand-v-2-3-0-0"> (missing ref)Review and correct ARIA roles, states, and properties according to the WAI-ARIA specification.
Here are the most impactful changes name.com should make to improve accessibility:
Add text content, aria-label, or aria-labelledby to links. Avoid empty <a> tags.
Add <label> elements with matching for attributes, or use aria-label.
Add text content, aria-label, or title to all <button> elements.
name.com scored 39/100 (grade D) on our accessibility audit. This score reflects automated checks against WCAG 2.1 Level AA criteria.
Our scan found 5 accessibility issues on name.com. Full WCAG compliance requires addressing all critical and major issues identified above.
The European Accessibility Act requires websites to meet WCAG 2.1 AA standards. Check the detailed report above to see name.com's compliance status.
See the full issue list above with severity levels, affected elements, and recommended fixes for name.com.
Get a free accessibility report for your website in seconds.