Skip to content
https://unstoppabledomains.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
63
GRADE
D
FIX
3
REVIEW
6
PASS
4
INFO
0
Checks
13
4 PASS 6 REVIEW 3 FIX
D
Web Manifest
Action
Not found
FIX
Not found
Info::
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.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
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 ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
7 landmarks
REVIEW
7 landmarks
Info::
<main> landmark present
Warning::
No <nav> landmark found
Info::
No contentinfo (footer) landmark
Warning::
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
BANNER header MAIN CONTENTINFO (missing!)

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

B
Form Accessibility
4 of 4 controls have issues
REVIEW
4 of 4 controls have issues
Warning::
4 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" id="search-input">; <input type="text">; <input type="text">; <input type="text">
4 controls
0 labeled
4 placeholder only
0 unlabeled
ControlTypeLabelMethod
#search-inputtext(Search domains)placeholder only
inputtext(Search for a domain)placeholder only
inputtext(Search for a domain)placeholder only
inputtext(Enter your email here)placeholder only

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

<input type="text" id="search-input">; <input type="text">; <input type="text">; <input type="text">

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

B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Unstoppable Domains — an accredited registrar & marketplace | Unstoppable Domains ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Favicon & Branding
Action
4 icon(s) detected
REVIEW
4 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
SVG favicon detected — scales perfectly to any size
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✓ SVG Favicon Present
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
Dark-specific theme-color detected
A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.
Info::
prefers-color-scheme CSS detected in inline styles
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark Mode✓ Dark Mode Supported
color-scheme meta Not set ✗Dark theme-color #ffffff ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

A
Heading Hierarchy
19 headings
PASS
19 headings
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H1 The Smartest Way ToBuy & Sell Domains
  • H2 The modern ICANN-Accredited Registrar built for power users.
  • H3 They're building exactly what domainers have been asking for.
  • H3 Everything You WantFrom A Marketplace
  • H4 $7.99 .com Regs & Transfers*
  • H4 Afternic & Sedo Fast Transfer
  • H4 AI Assistant, API, & MCP
  • H4 Reseller & Affiliate API
  • H4 Self-Brokerage Via
  • H4 Bring Your Own Lead For 3%
  • H3 With Domain ToolsFor Power Users
  • H4 An AI AssistantFor Your Portfolio
  • H4 Free Backorders
  • H4 Automate With OurUser API
  • H4 Sell DomainsOn Your Website
  • H2 Launch a DNS TLD for Your Community
  • H3 Frequently Asked Questions
  • H1 Buy Your Domain duplicate H1
  • H2 Register At-Cost. Self-Broker For 3%

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

A+
Alt Text Quality
All 30 images OK
PASS
All 30 images OK
Info::
8 decorative image(s) correctly marked
Info::
22 image(s) with good alt text
30 images 22 good alt text 8 decorative
All images have appropriate alt text.
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 The Smartest Way To19.88:13.0:1
#000000
#F5F9FF
Pass
h1 Buy & Sell Domains19.37:13.0:1
#000000
#F1F6FF
Pass
h1 Buy Your Domain21.00:13.0:1
#000000
#FFFFFF
Pass
h2 The modern19.38:13.0:1
#000000
#F2F6FD
Pass
h2 built for power user…19.88:13.0:1
#000000
#F5F9FF
Pass
h2 Launch a DNS TLD for…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Register At-Cost. Se…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 They're building exa…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Everything You Want21.00:13.0:1
#000000
#FFFFFF
Pass
h3 From A Marketplace21.00:13.0:1
#000000
#FFFFFF
Pass
h3 With Domain Tools21.00:13.0:1
#000000
#FFFFFF
Pass
h3 For Power Users21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Frequently Asked Que…21.00:13.0:1
#000000
#FFFFFF
Pass
title Unstoppable Domains …19.88:14.5:1
#000000
#F5F9FF
Pass
a Buy19.88:14.5:1
#000000
#F5F9FF
Pass
a Sell19.88:14.5:1
#000000
#F5F9FF
Pass
a Build19.88:14.5:1
#000000
#F5F9FF
Pass
span Ctrl19.88:14.5:1
#000000
#F5F9FF
Pass
div Trusted to manage ov…19.88:14.5:1
#000000
#F5F9FF
Pass
span 1 million19.88:14.5:1
#000000
#F5F9FF
Pass

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.

A
Lighthouse Accessibility Audits
Score 92/100 — 3 failing, 26 passed
PASS
92

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

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
0 div.css-18lgmoo-headerNavContainer > div.css-184tvut-rightNavContainer > div.css-1t7v3yg-iconsContainer > a.MuiTypography-root

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

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
0 div.css-184tvut-rightNavContainer > div.css-1t7v3yg-iconsContainer > a.MuiTypography-root > button#header.goToCartButton
Search div.css-k4uv0q-page > div.css-rfiwl0-root > div.css-1esl0ei-tabs > div.css-components-homepage-HeroWithAgents-AgentModeTabs-0-active-ref
AI Site Builder div.css-k4uv0q-page > div.css-rfiwl0-root > div.css-1esl0ei-tabs > div.css-1kixnlg-tab
AI Portfolio Assistant div.css-k4uv0q-page > div.css-rfiwl0-root > div.css-1esl0ei-tabs > div.css-1kixnlg-tab
○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>`
●`[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
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●Form elements have associated labels
●`button`, `link`, and `menuitem` elements have accessible names
●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
●Links are distinguishable without relying on color.
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○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
○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
○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.
○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.
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback