Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

1 PASS 6 REVIEW 6 FIX

Link & Button Quality

Action

17 issue(s) across 161 links and 9 buttons

FIX

17 issue(s) across 161 links and 9 buttons

14 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: /; /order/cart; /; /order/cart; https://www.nameclub.com/?utm_source=dynadot&utm_campaign=nc-callouts&utm_med…; /; https://www.facebook.com/Dynadot/; https://instagram.com/dynadot/; https://www.linkedin.com/company/dynadot; https://www.twitter.com/dynadot (+4 more)

2 image-only link(s) without alt text

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

Got: a[href="https://www.dynadot.com/domain/ai-search"]; a[href="https://www.dynadot.com/domain/bulk-search"]

5 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://www.dynadot.com/domain/you?utm_source=promobar&utm_campaign=AMAZON%20…; https://www.dynadot.com/zh/domain/transfer?utm_source=promobar&utm_campaign=C…; https://www.dynadot.com/domain/you?utm_source=promobar&utm_campaign=AMAZON%20…; https://www.dynadot.com/zh/domain/transfer?utm_source=promobar&utm_campaign=C…; https://www.nameclub.com/?utm_source=dynadot&utm_campaign=nc-callouts&utm_med…

3 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.btn (#192 on page); button.mega-switch-btn (#195 on page); button.mega-switch-btn (#220 on page)

140 link(s) with descriptive text

161 links

14 empty

0 generic text

5 new tab

3 empty buttons

Element	Text	Issue	Suggested Fix
https://www.dynadot.com/domain/you?utm_s…	🌱 Be the difference. Claim …	new tab	Add '(opens in new tab)' to text
https://www.dynadot.com/zh/domain/transf…	Fresh start this spring 🌸 T…	new tab	Add '(opens in new tab)' to text
/	(empty)	empty	Add link text or aria-label
/order/cart	(empty)	empty	Add link text or aria-label
/	(empty)	empty	Add link text or aria-label
/order/cart	(empty)	empty	Add link text or aria-label
https://www.nameclub.com/?utm_source=dyn…	(empty)	empty	Add link text or aria-label
https://www.dynadot.com/domain/you?utm_s…	🌱 Be the difference. Claim …	new tab	Add '(opens in new tab)' to text
https://www.dynadot.com/zh/domain/transf…	Fresh start this spring 🌸 T…	new tab	Add '(opens in new tab)' to text
https://www.dynadot.com/domain/ai-search	AI Search	img no alt	Add alt attribute to the image
https://www.dynadot.com/domain/bulk-sear…	Bulk Search	img no alt	Add alt attribute to the image
https://www.nameclub.com/?utm_source=dyn…	Visit Our Premium Marketplace	new tab	Add '(opens in new tab)' to text
/	(empty)	empty	Add link text or aria-label
https://www.facebook.com/Dynadot/	(empty)	empty	Add link text or aria-label
https://instagram.com/dynadot/	(empty)	empty	Add link text or aria-label
https://www.linkedin.com/company/dynadot	(empty)	empty	Add link text or aria-label
https://www.twitter.com/dynadot	(empty)	empty	Add link text or aria-label
https://www.youtube.com/user/teamdynadot	(empty)	empty	Add link text or aria-label
https://www.reddit.com/r/dynadot/	(empty)	empty	Add link text or aria-label
https://apps.apple.com/us/app/dynadot-do…	(empty)	empty	Add link text or aria-label
https://play.google.com/store/apps/detai…	(empty)	empty	Add link text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

146 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

/; /order/cart; /; /order/cart; https://www.nameclub.com/?utm_source=dynadot&utm_campaign=nc-callouts&utm_med…; /; https://www.facebook.com/Dynadot/; https://instagram.com/dynadot/; https://www.linkedin.com/company/dynadot; https://www.twitter.com/dynadot (+4 more)

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

a[href="https://www.dynadot.com/domain/ai-search"]; a[href="https://www.dynadot.com/domain/bulk-search"]

Why this matters

Image-only links with no alt are unidentifiable to screen-reader users — link's destination is invisible.

Source: WCAG 2.1 SC 2.4.4

Add '(opens in new tab)' to link text or aria-label.

https://www.dynadot.com/domain/you?utm_source=promobar&utm_campaign=AMAZON%20…; https://www.dynadot.com/zh/domain/transfer?utm_source=promobar&utm_campaign=C…; https://www.dynadot.com/domain/you?utm_source=promobar&utm_campaign=AMAZON%20…; https://www.dynadot.com/zh/domain/transfer?utm_source=promobar&utm_campaign=C…; https://www.nameclub.com/?utm_source=dynadot&utm_campaign=nc-callouts&utm_med…

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

Icon-only buttons need an aria-label so screen readers can announce them.

button.btn (#192 on page); button.mega-switch-btn (#195 on page); button.mega-switch-btn (#220 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

favicon.ico present at site root

No apple-touch-icon detected

iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.

✓ favicon.ico Present

✗ PNG Icons Missing

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Not found

FIX

Not found

No web manifest found

No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark ModeNo Dark Mode Detected

color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

Print Stylesheet

Action

No print styles

FIX

No print styles

No print-specific styles detected

When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.

Print Stylesheet No Print Styles

Print stylesheet Not found ✗Inline @media print Not detected ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

1 navigation landmark(s) detected

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 1 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

Landmark Structure

4 landmarks

REVIEW

4 landmarks

<main> landmark present

1 <nav> landmark(s) found

No banner (header) landmark

Skip navigation link is missing (WCAG 2.4.1)

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Page Structure — as a screen reader sees it

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more ▾

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

Alt Text Quality

Action

40 of 88 images have issues

REVIEW

40 of 88 images have issues

40 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

5 decorative image(s) correctly marked

43 image(s) with good alt text

88 images 43 good alt text 5 decorative 40 missing

Issue	Count
missing	40 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

Form Accessibility

2 of 2 controls have issues

REVIEW

2 of 2 controls have issues

2 control(s) rely on placeholder only

Placeholder text disappears on focus and is not a reliable label.

Got: <input type="text" name="page_search_domain" id="home-search-result-domain-input">; <input type="text">

2 controls

0 labeled

2 placeholder only

0 unlabeled

Control	Type	Label	Method
#home-search-result-domain-input	text	(Search for a domain)	placeholder only
input	text	(Enter email)	placeholder only

Placeholder text disappears on focus and is not a reliable label.

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page Not Found | Dynadot - We'll Help You Get Back on Track ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Color Contrast (Screenshot)

Action

20 text elements analyzed, 8 fail WCAG AA

REVIEW

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

12 pass 8 fail WCAG AA 5 pass AA only

title Buy a Domain Name - Register, Manage, an…

1.17:1

#000000

#031242

needs 4.5:1 (normal text)

16px · top of page (header area)

a 🌱 Be the difference. Claim .YOU for E…

1.17:1

#000000

#031242

needs 4.5:1 (normal text)

16px · top of page (header area)

span Aftermarket

4.47:1

#000000

#0577C7

needs 4.5:1 (normal text)

16px · above the fold

span Tools

4.05:1

#000000

#0570BC

needs 4.5:1 (normal text)

16px · above the fold

span Resources

3.53:1

#000000

#0466B0

needs 4.5:1 (normal text)

16px · mid-page

span Support

3.05:1

#000000

#015CA2

needs 4.5:1 (normal text)

16px · mid-page

div USD ($)

2.64:1

#000000

#015294

needs 4.5:1 (normal text)

16px · mid-page

div English

2.25:1

#000000

#014787

needs 4.5:1 (normal text)

16px · mid-page

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Your Super-Powered D…	19.89:1	3.0:1	#000000	#FFF8EC	Pass
h2 Unlock	19.89:1	3.0:1	#000000	#FFF8EC	Pass
h2 Power	19.89:1	3.0:1	#000000	#FFF8EC	Pass
title Buy a Domain Name - …	1.17:1	4.5:1	#000000	#031242	Fail
a 🌱 Be the differen…	1.17:1	4.5:1	#000000	#031242	Fail
a Fresh start this spr…	7.54:1	4.5:1	#000000	#0FA2F8	Pass
span Domains	7.54:1	4.5:1	#000000	#0DA2F8	Pass
span Aftermarket	7.45:1	4.5:1	#000000	#09A1F7	Pass
span Tools	7.24:1	4.5:1	#000000	#029EF7	Pass
span Resources	6.90:1	4.5:1	#000000	#009AF2	Pass
span Support	6.44:1	4.5:1	#000000	#0194EB	Pass
span EN - USD ($)	6.04:1	4.5:1	#000000	#038FE3	Pass
span Login	5.49:1	4.5:1	#000000	#0587DB	Pass
span Domains	5.01:1	4.5:1	#000000	#0580D1	Pass
span Aftermarket	4.47:1	4.5:1	#000000	#0577C7	Fail
span Tools	4.05:1	4.5:1	#000000	#0570BC	Fail
span Resources	3.53:1	4.5:1	#000000	#0466B0	Fail
span Support	3.05:1	4.5:1	#000000	#015CA2	Fail
div USD ($)	2.64:1	4.5:1	#000000	#015294	Fail
div English	2.25:1	4.5:1	#000000	#014787	Fail

Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.

Lighthouse Accessibility Audits

Score 84/100 — 3 failing, 16 passed

REVIEW

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.nav-right > div > div > button.btn `div.nav-right > div > div > button.btn`
div.nav-right > div.navbar-right-shopping-cart > a.dyna-tooltip__trigger > button.btn `div.nav-right > div.navbar-right-shopping-cart > a.dyna-tooltip__trigger > button.btn`
div.navbar > div.nav-right > div.navbar-mega-btn > button.mega-switch-btn `div.navbar > div.nav-right > div.navbar-mega-btn > button.mega-switch-btn`
div.mega-menu-mobile > div.dynadot-logo > div.mega-top-btn-bar > button.mega-switch-btn `div.mega-menu-mobile > div.dynadot-logo > div.mega-top-btn-bar > button.mega-switch-btn`

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
nav > div.navbar > div.ctl-logo > a.router-link-active `nav > div.navbar > div.ctl-logo > a.router-link-active`
div.navbar > div.nav-right > div.navbar-right-shopping-cart > a.dyna-tooltip__trigger `div.navbar > div.nav-right > div.navbar-right-shopping-cart > a.dyna-tooltip__trigger`
div.mega-menu-mobile > div.dynadot-logo > div > a.router-link-active `div.mega-menu-mobile > div.dynadot-logo > div > a.router-link-active`
div.dynadot-logo > div.mega-top-btn-bar > div.person-bar > a `div.dynadot-logo > div.mega-top-btn-bar > div.person-bar > a`
div.footer-content > div.footer-gather > div.footer-logo > a.router-link-active `div.footer-content > div.footer-gather > div.footer-logo > a.router-link-active`
div.footer-content > div.footer-gather > div.footer-icon > a `div.footer-content > div.footer-gather > div.footer-icon > a`
div.footer-content > div.footer-gather > div.footer-icon > a `div.footer-content > div.footer-gather > div.footer-icon > a`
div.footer-content > div.footer-gather > div.footer-icon > a `div.footer-content > div.footer-gather > div.footer-icon > a`
div.footer-content > div.footer-gather > div.footer-icon > a `div.footer-content > div.footer-gather > div.footer-icon > a`
div.footer-content > div.footer-gather > div.footer-icon > a `div.footer-content > div.footer-gather > div.footer-icon > a`
div.footer-content > div.footer-gather > div.footer-icon > a `div.footer-content > div.footer-gather > div.footer-icon > a`
div.app-icon > span > span > a `div.app-icon > span > span > a`
div.app-icon > span > span > a `div.app-icon > span > span > a`

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.app-icon > span > span > a `div.app-icon > span > span > a`
div.app-icon > span > span > a `div.app-icon > span > span > a`

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Image elements have `[alt]` attributes

●Form elements have associated labels

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●ARIA attributes are used as specified for the element's role

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Deprecated ARIA roles were not used

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○`[role]`s have all required `[aria-*]` attributes

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○`[role]` values are valid

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Links are distinguishable without relying on color.

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○No element has a `[tabindex]` value greater than 0

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Identical links have the same purpose.

○Elements with visible text labels have matching accessible names.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

A+

Heading Hierarchy

2 headings

PASS

2 headings

Single H1 present

H1 Your Super-Powered Domain Marketplace
H2 Unlock Premium Domain Power

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.