Skip to content
https://dailychanges.domaintools.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
73
GRADE
C
FIX
8
REVIEW
4
PASS
12
INFO
0
Checks
24
12 PASS 4 REVIEW 8 FIX
D
Landmark Structure
Action
No landmarks
FIX
No landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Warning::
No <nav> landmark found
Info::
No banner (header) landmark
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.

No landmarks detected

Screen reader users have no way to navigate by region.

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

D
Tap Target Adequacy
Action
20 tap target(s) too small or too close together
FIX
20 tap target(s) too small or too close together
Warning::
20 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.
D
Mobile-Readable Font Sizes
Action
13% of visible text renders at >= 12 CSS px (107 below threshold)
FIX
13% of visible text renders at >= 12 CSS px (107 below threshold)
Warning::
107 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: <a> 10.0px ("Data"); <a> 10.0px ("Graph"); <div> 10.0px ("For the day of"); <b> 10.0px ("June 19, 2026"); <text> 10.0px ("50k").
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
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
F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://dailychanges.domaintools.com/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://dailychanges.domaintools.com/manifest.json

Manifest contains invalid JSON.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
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.

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
Form Accessibility
2 of 2 controls have issues
REVIEW
2 of 2 controls have issues
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="q" id="dc-search-input">; <input type="text" name="q" id="dc-search-input-2">
2 controls
0 labeled
2 placeholder only
0 unlabeled
ControlTypeLabelMethod
#dc-search-inputtext(Name server...)placeholder only
#dc-search-input-2text(Name server...)placeholder only

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

<input type="text" name="q" id="dc-search-input">; <input type="text" name="q" id="dc-search-input-2">

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 Page Not Found - DailyChanges.DomainTools.com ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 1 fail WCAG AA
REVIEW

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

19 pass 1 fail WCAG AA 5 pass AA only
a Most Changed
3.36:1
#000000
on
#006699
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 DailyChanges.DomainT…12.92:13.0:1
#000000
#A8D1E5
Pass
h2 Name servers with th…19.73:13.0:1
#000000
#F2F9FC
Pass
h3 Top-level Domains (T…19.18:13.0:1
#000000
#EDF6FB
Pass
title Daily DNS Changes & …20.90:14.5:1
#000000
#FDFFFD
Pass
span Search20.12:14.5:1
#000000
#FAFAFA
Pass
a Overview17.39:14.5:1
#000000
#E7EAED
Pass
a Most Changed3.36:14.5:1
#000000
#006699
Fail
a Most Changed (%)6.57:14.5:1
#000000
#3399CC
Pass
a Most New Domains6.57:14.5:1
#000000
#3399CC
Pass
a Most Transfers In6.57:14.5:1
#000000
#3399CC
Pass
a Most Transfers Out6.57:14.5:1
#000000
#3399CC
Pass
a Most Deleted Domains6.57:14.5:1
#000000
#3399CC
Pass
p DailyChanges.DomainT…21.00:14.5:1
#000000
#FFFFFF
Pass
div Click21.00:14.5:1
#000000
#FFFFFF
Pass
a here21.00:14.5:1
#000000
#FFFFFF
Pass
div to purchase a Domain…21.00:14.5:1
#000000
#FFFFFF
Pass
a Data8.39:14.5:1
#000000
#5BADD6
Pass
a Graph14.18:14.5:1
#000000
#B4DAEC
Pass
div For the day of20.17:14.5:1
#000000
#F7FBFD
Pass
b June 19, 202620.96:13.0:1
#000000
#FEFFFF
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.

B
Lighthouse Accessibility Audits
Score 83/100 — 4 failing, 16 passed
REVIEW
83

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.

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
Data div.dc-switch > ul.nav > li > a
Data Sets from DailyChanges at DomainTools.com div.footer-content > div.float-row > ul.footer-list > li.bold
Most Changed Name servers div.float-row > ul.footer-list > li > a
Name servers with the Highest % Change div.float-row > ul.footer-list > li > a
Top 50 Name servers for New Domains div.float-row > ul.footer-list > li > a
Top 50 Name servers for Transfers In div.float-row > ul.footer-list > li > a
Top 50 Name servers for Transfers Out div.float-row > ul.footer-list > li > a
Top 50 Name servers for Deleted Domains div.float-row > ul.footer-list > li > a
Top 25 Name servers for Transfers Today div.float-row > ul.footer-list > li > a
Name servers for the Top 50 Websites div.float-row > ul.footer-list > li > a
Other Research Products div.float-row > ul.footer-list > li.bold > a
Whois Search at DomainTools.com div.float-row > ul.footer-list > li > a
Reverse Name Server Lookup div.float-row > ul.footer-list > li > a
Reverse IP Lookup div.float-row > ul.footer-list > li > a
Whois History div.float-row > ul.footer-list > li > a
Hosting History div.float-row > ul.footer-list > li > a
Reverse Whois Search div.float-row > ul.footer-list > li > a
Reverse MX Lookup div.float-row > ul.footer-list > li > a
Screenshot History div.float-row > ul.footer-list > li > a
DailyChanges at DomainTools.com div.float-row > ul.footer-list > li.bold > a
Contact Us div.float-row > ul.footer-list > li > a
Support div.float-row > ul.footer-list > li > a
Terms of Service div.float-row > ul.footer-list > li > a
© 2026 DomainTools, LLC All rights reserved. Any and all use of DailyChanges.Do… body > div.footer-container > div.footer-content > div.footer-disclaimer
2026 DomainTools, LLC div.footer-container > div.footer-content > div.footer-disclaimer > b

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Top-level Domains (TLDs) Overview div.round-top-fill > div.text-top > div.float-row > h3

These are opportunities to improve keyboard navigation in your application.

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
Most Changed Name servers div.float-row > ul.footer-list > li > a
Name servers with the Highest % Change div.float-row > ul.footer-list > li > a
Top 50 Name servers for New Domains div.float-row > ul.footer-list > li > a
Top 50 Name servers for Transfers In div.float-row > ul.footer-list > li > a
Top 50 Name servers for Transfers Out div.float-row > ul.footer-list > li > a
Top 50 Name servers for Deleted Domains div.float-row > ul.footer-list > li > a
Top 25 Name servers for Transfers Today div.float-row > ul.footer-list > li > a
Name servers for the Top 50 Websites div.float-row > ul.footer-list > li > a
Other Research Products div.float-row > ul.footer-list > li.bold > a
Whois Search at DomainTools.com div.float-row > ul.footer-list > li > a
Reverse Name Server Lookup div.float-row > ul.footer-list > li > a
Reverse IP Lookup div.float-row > ul.footer-list > li > a
Whois History div.float-row > ul.footer-list > li > a
Hosting History div.float-row > ul.footer-list > li > a
Reverse Whois Search div.float-row > ul.footer-list > li > a
Reverse MX Lookup div.float-row > ul.footer-list > li > a
Screenshot History div.float-row > ul.footer-list > li > a
Contact Us div.float-row > ul.footer-list > li > a
Support div.float-row > ul.footer-list > li > a
Terms of Service div.float-row > ul.footer-list > li > a

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

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-hidden="true"]` is not present on the document `<body>`
●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.
●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.
●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
●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
●`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
●Identical links have the same purpose.
●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.
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA attributes are used as specified for the element's role
○Deprecated ARIA roles were not used
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○`[aria-hidden="true"]` elements do not contain focusable descendents
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements use only permitted ARIA attributes
○`[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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○Buttons have an accessible name
○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
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○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
○`<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.
○Elements with visible text labels have matching accessible names.
A
Heading Hierarchy
3 headings, 1 skip(s)
PASS
3 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 DailyChanges.DomainTools.com: Daily DNS Changes and Web Hosting Activity
  • H3 Top-level Domains (TLDs) Overview skipped
  • H2 Name servers with the Most Total Activity

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

A+
Heading Text Quality
All 3 heading(s) have substantive, well-formed text
PASS
All 3 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 2 images OK
PASS
All 2 images OK
Info::
1 image(s) with alt text over 125 characters
Info::
1 image(s) with good alt text
2 images 1 good alt text
IssueCount
too long1 image(s)
A
Form Input Types
2 input(s) using type=text where a specific type would help
PASS
2 input(s) using type=text where a specific type would help
Info::
Input "q" should use type="search" (currently type="text")
Field name "q" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
Info::
Input "q" should use type="search" (currently type="text")
Field name "q" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
A+
Form Input Quality
2 form control(s) checked, no input-semantic issues
PASS
2 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
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"
Info::
<html lang="en"> is set and valid
Got: en
A+
Tabindex Anti-Patterns
No explicit tabindex attributes found
PASS
No explicit tabindex attributes found
Info::
No explicit tabindex attributes found
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
No iframes on this page
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback