Skip to content
https://dnb.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
60
GRADE
D
FIX
5
REVIEW
3
PASS
5
INFO
0
Checks
13
5 PASS 3 REVIEW 5 FIX
F
404 Error Page
Action
HTTP 404, bare page
FIX
HTTP 404, bare page
Info::
Correct 404 status code returned
Got: HTTP 404
Warning::
Bare server default 404 page
The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.
404 Page Quality Default 404 Page
Status Code HTTP 404 ✓Page Title 404 Not Found ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #000000
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 ModePartial Dark Mode
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::
1 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
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 1 <nav> element(s)
Back to Top
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.
C
Landmark Structure
Action
3 landmarks
REVIEW
3 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
1 <nav> landmark(s) found
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 (missing!) CONTENTINFO footer

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

B
Form Accessibility
2 of 3 controls have issues
REVIEW
2 of 3 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select name="country">
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="email" name="email">
Info::
1 control(s) properly labeled
3 controls
1 labeled
1 placeholder only
1 unlabeled
ControlTypeLabelMethod
#trustarc-lang-selectselectSelect languagefor/id
emailemail(Email *)placeholder only
countryselect(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<select name="country">

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

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

<input type="email" name="email">

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
Favicon & Branding
6 icon(s) detected
REVIEW
6 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
A
Heading Hierarchy
46 headings, 1 skip(s)
PASS
46 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Intelligent Data to Drive Business Performance
  • H2 Power Your AI Workflows with Our Unparalleled Data
  • H2 Find Solutions to Fit Your Business Need
  • H3 Select Business Need
  • H4 Manage Your Risk
  • H4 Grow Your Business
  • H4 Control Your Cost
  • H4 Small Business
  • H4 Enterprise
  • H4 Public Sector
  • H4 Small Business
  • H4 Enterprise
  • H4 Small Business
  • H4 Enterprise
  • H3 Reduce Your Risk
  • H5 Face Financial Risk Head On skipped
  • H5 Prevent Supplier Disruption
  • H5 Manage and Monitor Compliance Risk
  • H5 Manage Risk at the Federal Level
  • H5 Manage Risk Closer to Home
  • H5 Protect Your Business from Vendor & Supplier Risk
  • H5 Check Up on Your Business Credit
  • H5 Seek to Improve Business Credit
  • H5 Harness the Power of Responsible AI
  • H5 Reduce Your Fraud Exposure
  • H5 Keep Sustainability Risk at Bay
  • H5 Improve Your Online Presence
  • H5 Reach Your Ideal Customers
  • H5 Close Deals with Better Sales Intel
  • H5 Optimize Your Marketing Strategy
  • H5 Accelerate Growth with Trusted Data
  • H2 Accelerate Performance and Achieve Your Business Goals
  • H3 Look Up or Apply for a D‑U‑N‑S Number
  • H2 Expert Insights for Business Leaders
  • H2 Human-at-the-Helm: A Practical Model for the Agentic Era
  • H2 How Predictive Sales Intelligence Is Rewriting the B2B Buyer Journey
  • H2 Navigating Disruptions to the Strait of Hormuz 2026
  • H2 New Bankruptcy Data Reveals Business Vulnerabilities
  • H2 D&B Survey: Business Optimism and Financial Confidence Declining
  • H2 Ethical Blind Spots in AI Data Preparation
  • H2 What Customers Are Saying
  • H2 See Where Data Can Take You
  • H2 Let's get in touch
  • H2 Solutions and Insights
  • H2 Company
  • H2 Support

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+
Alt Text Quality
All 54 images OK
PASS
All 54 images OK
Info::
6 decorative image(s) correctly marked
Info::
48 image(s) with good alt text
54 images 48 good alt text 6 decorative
All images have appropriate alt text.
A+
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: DNB Marketing Website
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria ✓ Installable
Name DNB Marketing Website ✓192×192 icon ✓512×512 icon ✓Start URL /content/dnb-marketing-website/us/en/home.html ✓Display Mode standalone ✓
Name DNB Marketing Website Display Mode standalone Theme Color #000000 Background Color #ffffff Icons 3 icon(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 Intelligent Data to …8.45:13.0:1
#000000
#A1A5A6
Pass
h2 Power Your AI Workfl…8.55:13.0:1
#000000
#A2A6A7
Pass
h2 Find Solutions to Fi…9.28:13.0:1
#000000
#A9ADAE
Pass
h2 Accelerate Performan…9.28:13.0:1
#000000
#A9ADAE
Pass
h2 Expert Insights for …9.28:13.0:1
#000000
#A9ADAE
Pass
h2 Human-at-the-Helm: A…9.28:13.0:1
#000000
#A9ADAE
Pass
h2 How Predictive Sales…9.28:13.0:1
#000000
#A9ADAE
Pass
h2 Navigating Disruptio…9.28:13.0:1
#000000
#A9ADAE
Pass
h2 New Bankruptcy Data …9.28:13.0:1
#000000
#A9ADAE
Pass
h2 D&B Survey: Business…9.28:13.0:1
#000000
#A9ADAE
Pass
h2 Ethical Blind Spots …9.28:13.0:1
#000000
#A9ADAE
Pass
h2 What Customers Are S…9.28:13.0:1
#000000
#A9ADAE
Pass
h2 See Where Data Can T…9.28:13.0:1
#000000
#A9ADAE
Pass
h2 Let's get in touch9.28:13.0:1
#000000
#A9ADAE
Pass
h2 Solutions and Insigh…9.28:13.0:1
#000000
#A9ADAE
Pass
h2 Company9.28:13.0:1
#000000
#A9ADAE
Pass
h2 Support9.28:13.0:1
#000000
#A9ADAE
Pass
h3 Select Business Need9.28:13.0:1
#000000
#A9ADAE
Pass
h3 Reduce Your Risk9.28:13.0:1
#000000
#A9ADAE
Pass
h3 Look Up or Apply for…9.28:13.0:1
#000000
#A9ADAE
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 95/100 — 3 failing, 28 passed
PASS
95

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.

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
Face Financial Risk Head On div.solutions-tool_productsDetailContainer__GFz1d > div.solutions-tool_productsDetailList__7+hpD > div.solutions-tool_productContainer__FXOwx > h5.solutions-tool_productTitle__K0+dK

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
Trust Centre div.footer_subContainer__-Khfg > ul.footer_subLinks__+pn7L > li > a
Accessibility div.footer_subContainer__-Khfg > ul.footer_subLinks__+pn7L > li > a

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
Manage Your Risk div.defaultLayoutInner > div.solutions-tool_selectionResultContainer__H3NXP > div.solutions-tool_cardContainer__sdmrc > button.solutions-tool_card__k+PU8
Grow Your Business div.defaultLayoutInner > div.solutions-tool_selectionResultContainer__H3NXP > div.solutions-tool_cardContainer__sdmrc > button.solutions-tool_card__k+PU8
Control Your Cost div.defaultLayoutInner > div.solutions-tool_selectionResultContainer__H3NXP > div.solutions-tool_cardContainer__sdmrc > button.solutions-tool_card__k+PU8
○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
●`[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
●`[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
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[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.
●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
●No element has a `[tabindex]` value greater than 0
●`[lang]` attributes have a valid value
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
○`[accesskey]` values are unique
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○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
○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
○Form elements have associated labels
○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.
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback