Skip to content
https://dupont.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
40
GRADE
F
FIX
8
REVIEW
4
PASS
1
INFO
0
Checks
13
1 PASS 4 REVIEW 8 FIX
F
Heading Hierarchy
Action
49 headings, 2 skip(s)
FIX
49 headings, 2 skip(s)
Warning::
Multiple H1 headings (7 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
11 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H5 Request processing
  • H1 Discover DuPont: Explore the innovations that define who we are and shape what’s possible
  • H1 DuPont Announces New 2035 Sustainability Goals duplicate H1
  • H1 DuPont Wins Two 2026 Edison Awards™ duplicate H1
  • H1 Discover DuPont: Explore the innovations that define who we are and shape what’s possible duplicate H1
  • H1 DuPont Announces New 2035 Sustainability Goals duplicate H1
  • H1 DuPont Wins Two 2026 Edison Awards™ duplicate H1
  • H1 Discover DuPont: Explore the innovations that define who we are and shape what’s possible duplicate H1
  • H2 (empty)
  • H2 DuPont is a leading advanced solutions provider focused on markets that shape the future—healthcare, water, and advanced industrials.
  • H2 Providing essential innovations with leading brands to key markets:
  • H3 Our Core Values are foundational to everything we do and every decision we make every day.
  • H3 (empty)
  • H5 We put safety & respect first skipped
  • H5 We act with integrity & accountability
  • H5 We grow & improve every day
  • H5 We solve problems for customers
  • H2 Our 2035 Sustainability Goals:
  • H3 Whether you're looking for our locations, learning about career opportunities, or want to do business with us, keep exploring the possibilities below.
  • H3 (empty)
  • H5 Browse our brands & products skipped
  • H5 Browse our brands & products
  • H5 (empty)
  • H5 Browse our industries
  • H5 Browse our industries
  • H5 (empty)
  • H5 Find a location
  • H5 Find a location
  • H5 (empty)
  • H5 Learn about careers
  • H5 Learn about careers
  • H5 (empty)
  • H5 Contact our help center
  • H5 Contact our help center
  • H5 (empty)
  • H5 Learn about us
  • H5 Learn about us
  • H5 (empty)
  • H5 See our science & innovation
  • H5 See our science & innovation
  • H5 (empty)
  • H5 Search our product finder
  • H5 Search our product finder
  • H5 (empty)
  • H4 Our Company
  • H4 Industries & Solutions
  • H4 Support
  • H4 Compliance
  • H5 Confirm Signout

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

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

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

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

F
Alt Text Quality
Action
15 of 22 images have issues
FIX
15 of 22 images have issues
Critical::
15 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
8 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
2 decorative image(s) correctly marked
Info::
5 image(s) with good alt text
22 images 5 good alt text 2 decorative 15 missing
IssueCount
missing15 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 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::
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 Missing
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
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
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::
1 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 1 <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.
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
Info::
No banner (header) 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 (missing!) NAV MAIN (missing!) ASIDE "Open Cookie Preferences Modal" 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
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 404 Page Not Found | DuPont ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 16 fail WCAG AA
REVIEW

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

4 pass 16 fail WCAG AA
h1 Discover DuPont: Explore the innovations…
2.85:1
#FFFFFF
on
#999999
needs 3.0:1 (large text)
32px · bottom of viewport · over background image/gradient
h1 DuPont Announces New 2035 Sustainability…
2.85:1
#FFFFFF
on
#999999
needs 3.0:1 (large text)
32px · bottom of viewport · over background image/gradient
h1 DuPont Wins Two 2026 Edison Awards™
2.85:1
#FFFFFF
on
#999999
needs 3.0:1 (large text)
32px · bottom of viewport · over background image/gradient
h1 Discover DuPont: Explore the innovations…
2.85:1
#FFFFFF
on
#999999
needs 3.0:1 (large text)
32px · bottom of viewport · over background image/gradient
h1 DuPont Announces New 2035 Sustainability…
2.85:1
#FFFFFF
on
#999999
needs 3.0:1 (large text)
32px · bottom of viewport · over background image/gradient
h1 DuPont Wins Two 2026 Edison Awards™
2.85:1
#FFFFFF
on
#999999
needs 3.0:1 (large text)
32px · bottom of viewport · over background image/gradient
h1 Discover DuPont: Explore the innovations…
2.85:1
#FFFFFF
on
#999999
needs 3.0:1 (large text)
32px · bottom of viewport · over background image/gradient
a Sign Up
3.47:1
#000000
on
#5A6562
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
a Industries & Solutions
2.11:1
#000000
on
#374640
needs 4.5:1 (normal text)
16px · top of page (header area)
a Industries & Solutions
2.34:1
#000000
on
#404C44
needs 4.5:1 (normal text)
16px · above the fold
a Aerospace & Aircraft
2.43:1
#000000
on
#454E46
needs 4.5:1 (normal text)
16px · above the fold
a View all Industries & Solutions
2.62:1
#000000
on
#4D5248
needs 4.5:1 (normal text)
16px · above the fold
a Automotive
2.03:1
#000000
on
#46402C
needs 4.5:1 (normal text)
16px · above the fold
a View all Industries & Solutions
1.86:1
#000000
on
#423A24
needs 4.5:1 (normal text)
16px · above the fold
a Building & Construction
1.50:1
#000000
on
#312C18
needs 4.5:1 (normal text)
16px · above the fold
a View all Industries & Solutions
1.33:1
#000000
on
#242314
needs 4.5:1 (normal text)
16px · above the fold

8 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Discover DuPont: Exp…2.85:13.0:1
#FFFFFF
#999999
Fail
h1 DuPont Announces New…2.85:13.0:1
#FFFFFF
#999999
Fail
h1 DuPont Wins Two 2026…2.85:13.0:1
#FFFFFF
#999999
Fail
h1 Discover DuPont: Exp…2.85:13.0:1
#FFFFFF
#999999
Fail
h1 DuPont Announces New…2.85:13.0:1
#FFFFFF
#999999
Fail
h1 DuPont Wins Two 2026…2.85:13.0:1
#FFFFFF
#999999
Fail
h1 Discover DuPont: Exp…2.85:13.0:1
#FFFFFF
#999999
Fail
h2 DuPont is a leading …7.37:13.0:1
#000000
#999999
Pass
h2 Providing essential …7.37:13.0:1
#000000
#999999
Pass
title Home | DuPont7.37:14.5:1
#000000
#999999
Pass
a Sign In7.37:14.5:1
#000000
#999999
Pass
a Sign Up3.47:14.5:1
#000000
#5A6562
Fail
a Industries & Solutio…2.11:14.5:1
#000000
#374640
Fail
a Industries & Solutio…2.34:14.5:1
#000000
#404C44
Fail
a Aerospace & Aircraft2.43:14.5:1
#000000
#454E46
Fail
a View all Industries …2.62:14.5:1
#000000
#4D5248
Fail
a Automotive2.03:14.5:1
#000000
#46402C
Fail
a View all Industries …1.86:14.5:1
#000000
#423A24
Fail
a Building & Construct…1.50:14.5:1
#000000
#312C18
Fail
a View all Industries …1.33:14.5:1
#000000
#242314
Fail

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.

C
Lighthouse Accessibility Audits
Action
Score 78/100 — 7 failing, 27 passed
REVIEW
78

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
Legal Notices & Terms of Use div.col-sm-12 > ul.footer-list-legal > li > a
Privacy div.col-sm-12 > ul.footer-list-legal > li > a
Site Map div.col-sm-12 > ul.footer-list-legal > li > a
Accessibility div.col-sm-12 > ul.footer-list-legal > li > a
ACCEPT ALL div.mainContent > div > div.pdynamicbutton > a.call
REJECT ALL div.mainContent > div > div.pdynamicbutton > a.required
MANAGE COOKIES » div.mainContent > div > div.pdynamicbutton > a.shp
Privacy Policy div > div.footer > div.left > a#privacyPolicyAnchor
Tracker Details Page div > div.footer > div.left > a
Powered by div > div.footer > div.right > label

These are opportunities to improve the legibility of your content.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body#corporate-editable-page-4a98861a6d > div#pop-div2012639048716905332 > div#pop-div303983712242929486 > div#pop-frame06179396321046385 body#corporate-editable-page-4a98861a6d > div#pop-div2012639048716905332 > div#pop-div303983712242929486 > div#pop-frame06179396321046385

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
We put safety & respect first div.row > div.list-item > div.list-container > h5.full
Browse our brands & products div.list-item > div.card-image > div.card-text > h5

These are opportunities to improve keyboard navigation in your application.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.component-navigation--logo > div#userMobileIcon > a#profileNavTrigger > img.non_login_user div.component-navigation--logo > div#userMobileIcon > a#profileNavTrigger > img.non_login_user
ul.component-navigation--items-bottom > li > a.search > img ul.component-navigation--items-bottom > li > a.search > img
div.owl-item > div.card-view > div.row > img.OF-cover div.owl-item > div.card-view > div.row > img.OF-cover
div.owl-item > div.card-view > div.row > img.OF-cover div.owl-item > div.card-view > div.row > img.OF-cover
div.owl-item > div.card-view > div.row > img.OF-cover div.owl-item > div.card-view > div.row > img.OF-cover
div.owl-item > div.card-view > div.row > img.OF-cover div.owl-item > div.card-view > div.row > img.OF-cover
div.owl-item > div.card-view > div.row > img.OF-cover div.owl-item > div.card-view > div.row > img.OF-cover
div.owl-item > div.card-view > div.row > img.OF-cover div.owl-item > div.card-view > div.row > img.OF-cover
ul > li > a > img ul > li > a > img
ul > li > a > img ul > li > a > img
ul > li > a > img ul > li > a > img
ul > li > a > img ul > li > a > img
ul > li > a > img ul > li > a > img

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
nav > div.component-navigation--logo > div.hamburger > input nav > div.component-navigation--logo > div.hamburger > input

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
nav > div.component-navigation--logo > div#userMobileIcon > a#profileNavTrigger nav > div.component-navigation--logo > div#userMobileIcon > a#profileNavTrigger
div.col-sm-12 > ul > li > a div.col-sm-12 > ul > li > a
div > div.footer > div.right > a div > div.footer > div.right > a

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.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Search Product Finder English div.container > nav > div.component-navigation--items > ul.component-navigation--items-bottom
Legal Notices & Terms of Use Privacy Site Map Accessibility Cookie Preferences div.container > div#margin-top > div.col-sm-12 > ul.footer-list-legal

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

○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
●`[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
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Touch targets have sufficient size and spacing.
●`[lang]` attributes have a valid value
●Document has a main landmark.
●Deprecated ARIA roles were not used
●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.
○`[accesskey]` values are unique
○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.
○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>`.
○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
Form Accessibility
1 of 1 controls have issues
PASS
1 of 1 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="checkbox">
1 controls
0 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
inputcheckbox(none)none

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

<input type="checkbox">

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

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

Send Feedback