Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

13 PASS 7 REVIEW 4 FIX

Favicon & Branding

Action

3 icon(s) detected

FIX

3 icon(s) detected

favicon.ico present at site root

HTML icon links detected

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 Present

✗ 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.

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

Hamburger menu detected (responsive design)

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)

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

Landmark Structure

3 landmarks

REVIEW

3 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

Link & Button Quality

1 issue(s) across 26 links and 3 buttons

REVIEW

1 issue(s) across 26 links and 3 buttons

4 link(s) open in new tab without warning

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

Got: https://chromewebstore.google.com/detail/ldns-dns-domain-tools/ehgkpjkmaichih…; https://addons.mozilla.org/en-CA/firefox/addon/ldns-dns-domain-tools/; https://chromewebstore.google.com/detail/ldns-dns-domain-tools/ehgkpjkmaichih…; https://addons.mozilla.org/en-CA/firefox/addon/ldns-dns-domain-tools/

1 button(s) with no accessible text

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

Got: button.rounded-e-lg (#99 on page)

22 link(s) with descriptive text

26 links

0 empty

0 generic text

4 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
https://chromewebstore.google.com/detail…	siGooglechrome Add to Chrome	new tab	Add '(opens in new tab)' to text
https://addons.mozilla.org/en-CA/firefox…	siFirefoxbrowser Add to Firefo…	new tab	Add '(opens in new tab)' to text
https://chromewebstore.google.com/detail…	siGooglechrome Chrome Web Stor…	new tab	Add '(opens in new tab)' to text
https://addons.mozilla.org/en-CA/firefox…	siFirefoxbrowser Firefox AMO	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label

24 links and buttons have descriptive text

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

https://chromewebstore.google.com/detail/ldns-dns-domain-tools/ehgkpjkmaichih…; https://addons.mozilla.org/en-CA/firefox/addon/ldns-dns-domain-tools/; https://chromewebstore.google.com/detail/ldns-dns-domain-tools/ehgkpjkmaichih…; https://addons.mozilla.org/en-CA/firefox/addon/ldns-dns-domain-tools/

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.rounded-e-lg (#99 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

Tap Target Adequacy

1 tap target(s) too small or too close together

REVIEW

1 tap target(s) too small or too close together

1 tap target(s) too small or too close to neighbors

WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.

Mobile-Readable Font Sizes

Action

76% of visible text renders at >= 12 CSS px (24 below threshold)

REVIEW

76% of visible text renders at >= 12 CSS px (24 below threshold)

24 text node(s) render below 12 CSS pixels on mobile

Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <span> 11.0px ("//"); <p> 11.0px ("dns · rdap · email · server · security"); <p> 11.0px ("// try"); <a> 11.0px ("ldns.com/google.com"); <a> 11.0px ("/cloudflare.com").

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Homepage link present on 404 page

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✓

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

prefers-color-scheme CSS detected in inline styles

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 Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

Lighthouse Accessibility Audits

Score 85/100 — 3 failing, 19 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.mt-8 > div.w-full > form.flex > button.rounded-e-lg `div.mt-8 > div.w-full > form.flex > button.rounded-e-lg`

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
ldns.com/google.com `div.min-w-0 > div.mt-8 > p.mt-3 > a.text-primary-500`
/cloudflare.com `div.min-w-0 > div.mt-8 > p.mt-3 > a.text-primary-500`
/github.com `div.min-w-0 > div.mt-8 > p.mt-3 > a.text-primary-500`
01 `div.grid > a.group > div.flex > span.font-mono`
02 `div.grid > a.group > div.flex > span.font-mono`
03 `div.grid > a.group > div.flex > span.font-mono`
04 `div.grid > a.group > div.flex > span.font-mono`
05 `div.grid > a.group > div.flex > span.font-mono`
GET `div.grid > div.bg-surface > p > span.text-primary-500`
GET `div.grid > div.bg-surface > p > span.text-primary-500`
GET `div.grid > div.bg-surface > p > span.text-primary-500`
GET `div.grid > div.bg-surface > p > span.text-primary-500`
GET `div.grid > div.bg-surface > p > span.text-primary-500`
GET `div.grid > div.bg-surface > p > span.text-primary-500`

These are opportunities to improve the legibility of your content.

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
Firefox AMO `div > ul.space-y-1.5 > li > a.text-xs`

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

●Document has a `<title>` element

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

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

●Links have a discernible name

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

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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

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

○`[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.

○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

○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

9 headings

PASS

9 headings

Single H1 present

H1 Look up any domain in one place.
H2 Five tools, one URL.
H3 Records
H3 Email
H3 Server
H3 Security
H3 Subdomains
H2 Every tool is also an API.
H2 One click on any tab.

A+

Heading Text Quality

All 9 heading(s) have substantive, well-formed text

PASS

All 9 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A+

Alt Text Quality

All 3 images OK

PASS

All 3 images OK

3 image(s) with good alt text

3 images 3 good alt text

All images have appropriate alt text.

Form Accessibility

1 of 1 controls have issues

PASS

1 of 1 controls have issues

1 control(s) rely on placeholder only

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

Got: <input type="search">

1 controls

0 labeled

1 placeholder only

0 unlabeled

Control	Type	Label	Method
input	search	(Example.com, domain.net, name.org…)	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

A+

Form Input Types

1 form control(s) checked, no type mismatches

PASS

1 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

1 form control(s) checked, no input-semantic issues

PASS

1 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

No autofill-eligible form controls (no name/email/tel/address fields)

A+

Document Language

Lang attribute set to "en"

PASS

Lang attribute set to "en"

<html lang="en"> is set and valid

Got: en

A+

Tabindex Anti-Patterns

No explicit tabindex attributes found

PASS

No explicit tabindex attributes found

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

No `<meta name="theme-color">` -- browser chrome falls back to default

Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.

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)

Element	Ratio	Required	FG	BG	Result
h1 Look up any domain	20.12:1	3.0:1	#000000	#FBFAF7	Pass
h2 Five tools, one URL.	20.12:1	3.0:1	#000000	#FBFAF7	Pass
h2 Every tool is also a…	19.98:1	3.0:1	#000000	#FBF9F6	Pass
h2 One click on any tab…	19.98:1	3.0:1	#000000	#FBF9F6	Pass
h3 Records	20.12:1	3.0:1	#000000	#FBFAF7	Pass
h3 Email	19.98:1	3.0:1	#000000	#FBF9F6	Pass
h3 Server	19.98:1	3.0:1	#000000	#FBF9F6	Pass
h3 Security	19.98:1	3.0:1	#000000	#FBF9F6	Pass
h3 Subdomains	19.98:1	3.0:1	#000000	#FBF9F6	Pass
title Free DNS, RDAP, Emai…	20.13:1	4.5:1	#000000	#FBFAF8	Pass
span LDNS	20.13:1	4.5:1	#000000	#FBFAF8	Pass
span extension	20.12:1	4.5:1	#000000	#FBFAF7	Pass
a about	20.12:1	4.5:1	#000000	#FBFAF7	Pass
p dns · rdap · email…	20.12:1	4.5:1	#000000	#FBFAF7	Pass
span in one place.	20.12:1	4.5:1	#000000	#FBFAF7	Pass
p DNS records, registr…	20.12:1	4.5:1	#000000	#FBFAF7	Pass
p // try	20.12:1	4.5:1	#000000	#FBFAF7	Pass
a ldns.com/google.com	20.12:1	4.5:1	#000000	#FBFAF7	Pass
a /cloudflare.com	20.12:1	4.5:1	#000000	#FBFAF7	Pass
p , or	20.12:1	4.5:1	#000000	#FBFAF7	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.

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