Skip to content
https://domaintools.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
60
GRADE
D
FIX
4
REVIEW
6
PASS
3
INFO
0
Checks
13
3 PASS 6 REVIEW 4 FIX
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
F
Web Manifest
Action
Valid manifest
FIX
Valid manifest
Warning::
No name or short_name
Add a name field to identify the app.
Warning::
No 192x192 icon
A 192px icon is required for PWA installation.
PWA Install Criteria Not Installable
Name ✗192×192 icon ✗512×512 icon ✗Start URL ✗Display Mode ✗
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::
10 navigation landmark(s) detected
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 10 <nav> element(s)
Back to Top
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.
B
Landmark Structure
17 landmarks
REVIEW
17 landmarks
Info::
<main> landmark present
Info::
10 <nav> landmark(s) found
Warning::
3 of 10 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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 NAV MAIN CONTENTINFO footer

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

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
2 of 10 controls have issues
REVIEW
2 of 10 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="search" name="query" id="search">; <input type="search" name="query" id="search">
Info::
8 control(s) properly labeled
10 controls
8 labeled
2 placeholder only
0 unlabeled
ControlTypeLabelMethod
inputsubmitSearch on the websitearia-label
inputsubmitSearch on the websitearia-label
#Radio-3radionone
#radioradionone
#radioradionone
#radioradionone
#radioradionone
#radioradionone
#searchsearch(Search…)placeholder only
#searchsearch(Search…)placeholder only

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

<input type="search" name="query" id="search">; <input type="search" name="query" id="search">

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 Not Found ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
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 Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

B
Lighthouse Accessibility Audits
Score 85/100 — 5 failing, 25 passed
REVIEW
85

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.button_arrow_wrap > div.button_arrow_element > div.g_clickable_wrap > button.g_clickable_btn div.button_arrow_wrap > div.button_arrow_element > div.g_clickable_wrap > button.g_clickable_btn
div.slider_button_layout > div.button_arrow_wrap > div.g_clickable_wrap > button.g_clickable_btn div.slider_button_layout > div.button_arrow_wrap > div.g_clickable_wrap > button.g_clickable_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
div.g_btn_group > div.g_button_wrap > div.g_clickable_wrap > a.g_clickable_link div.g_btn_group > div.g_button_wrap > div.g_clickable_wrap > a.g_clickable_link

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
Reject All div.cky-notice > div.cky-notice-group > div.cky-notice-btn-wrapper > button.cky-btn
Accept All div.cky-notice > div.cky-notice-group > div.cky-notice-btn-wrapper > button.cky-btn

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
Go to slide 1 div.slider_wrap > div.slider_controls > div.slider_bullet_list > button.slider_bullet_item
Go to slide 2 div.slider_wrap > div.slider_controls > div.slider_bullet_list > button.slider_bullet_item
Go to slide 3 div.slider_wrap > div.slider_controls > div.slider_bullet_list > button.slider_bullet_item
Go to slide 4 div.slider_wrap > div.slider_controls > div.slider_bullet_list > button.slider_bullet_item

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
Load More div.integrations_content > div.cms-integrations > div.w-pagination-wrapper > a.w-pagination-next
Reseller Partner div.footer_group_wrap > div.footer_group_list > div.footer_group_item > a.footer_link_wrap
Events div.footer_group_wrap > div.footer_group_list > div.footer_group_item > a.footer_link_wrap
Careers div.footer_group_wrap > div.footer_group_list > div.footer_group_item > a.footer_link_wrap
○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
●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.
●`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
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●No element has a `[tabindex]` value greater than 0
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Uses ARIA roles only on compatible elements
●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
○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.
○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
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○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.
A+
Heading Hierarchy
16 headings
PASS
16 headings
Info::
Single H1 present
  • H1 See What Others Miss.
  • H2 DomainTools maps the Internet to bring you the most comprehensive DNS-focused threat intelligence data.
  • H2 Others Guess. We’ve Got the Data.
  • H2 Bring DomainTools to the AI SOC
  • H2 Crucial Context for Every Stage of a Domain’s Lifecycle
  • H2 Don’t React, Act First
  • H3 Detect malicious domains 10 days earlier than standard industry blocklists
  • H2 Our Edge. Your Advantage.
  • H2 Enrich any tool with the very best data
  • H2 Resources
  • H2 Navigate SOC Challenges With Your Post-RiskIQ Ally
  • H3 PRODUCTS
  • H3 Partners
  • H3 Company
  • H3 Knowledge center
  • H3 Client Resources
A+
Alt Text Quality
All 87 images OK
PASS
All 87 images OK
Info::
1 image(s) with alt text over 125 characters
Info::
7 decorative image(s) correctly marked
Info::
79 image(s) with good alt text
87 images 79 good alt text 7 decorative
IssueCount
too long1 image(s)
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 See What Others Miss…18.26:13.0:1
#000000
#EFEFEF
Pass
h2 DomainTools maps the…18.26:13.0:1
#000000
#EFEFEF
Pass
h2 Others Guess.18.26:13.0:1
#000000
#EFEFEF
Pass
h2 We’ve Got the Data18.26:13.0:1
#000000
#EFEFEF
Pass
h2 Bring DomainTools to…18.26:13.0:1
#000000
#EFEFEF
Pass
h2 Crucial Context for …18.26:13.0:1
#000000
#EFEFEF
Pass
h2 Don’t React, Act F…18.26:13.0:1
#000000
#EFEFEF
Pass
h2 Our Edge. Your Advan…18.26:13.0:1
#000000
#EFEFEF
Pass
h2 Enrich any tool with…18.26:13.0:1
#000000
#EFEFEF
Pass
h2 Navigate SOC Challen…18.26:13.0:1
#000000
#EFEFEF
Pass
h3 Detect malicious dom…18.26:13.0:1
#000000
#EFEFEF
Pass
h3 than standard indust…18.26:13.0:1
#000000
#EFEFEF
Pass
h3 PRODUCTS18.26:13.0:1
#000000
#EFEFEF
Pass
h3 Partners18.26:13.0:1
#000000
#EFEFEF
Pass
h3 Company18.26:13.0:1
#000000
#EFEFEF
Pass
h3 Knowledge center18.26:13.0:1
#000000
#EFEFEF
Pass
h3 Client Resources18.26:13.0:1
#000000
#EFEFEF
Pass
title Threat Intelligence …18.26:14.5:1
#000000
#EFEFEF
Pass
span Press Alt+1 for scre…18.26:14.5:1
#000000
#EFEFEF
Pass
a Accessibility Screen…18.26:14.5:1
#000000
#EFEFEF
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.

Send Feedback