Skip to content
https://ditchcarbon.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
79
GRADE
C
FIX
3
REVIEW
8
PASS
13
INFO
0
Checks
24
13 PASS 8 REVIEW 3 FIX
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::
6 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 6 <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
11 landmarks
REVIEW
11 landmarks
Info::
<main> landmark present
Info::
6 <nav> landmark(s) found
Warning::
1 of 6 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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.
Page Structure — as a screen reader sees it
BANNER header NAV MAIN CONTENTINFO (missing!)

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
Mobile-Readable Font Sizes
97% of visible text renders at >= 12 CSS px (4 below threshold)
REVIEW
97% of visible text renders at >= 12 CSS px (4 below threshold)
Info::
4 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: <p> 10.0px ("Supplier-specific (primary) emissions da..."); <p> 10.0px ("Reduced manual aggregation, with emissio..."); <p> 10.0px ("CDP supplier score lifted from C to A- a..."); <div> 11.8px ("v261002.1").
C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 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
Favicon & Branding
7 icon(s) detected
REVIEW
7 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 Missing
✓ Multiple Sizes Present
B
PWA Depth
3 PWA signal(s) surfaced
REVIEW
3 PWA signal(s) surfaced
Warning::
Manifest is missing `display` -- defaults to browser, no PWA UX
When `display` is `browser` (or unset, which is the spec default), the installed app opens in a regular browser tab -- no install prompt, no standalone window, no app-shell experience. The intended values for a PWA are `standalone` (most common; full-screen, no browser chrome) or `fullscreen` (games / immersive apps). `minimal-ui` is a middle ground (basic browser controls but no address bar).
Info::
Manifest has no maskable icon
Android 12+ Adaptive Icons crop non-maskable icons to a circle or squircle -- frequently hiding important parts of the logo. Add at least one icon entry with `"purpose": "maskable"` (or `"any maskable"`) and a maskable-aware design (16% safe-zone padding around the inner mark).
Info::
Manifest is missing `theme_color`
Without `theme_color`, the install prompt and Android status bar fall back to a generic tint instead of your brand color. Add a hex color (e.g. `"theme_color": "#0066cc"`); for richer support, mirror it via `<meta name="theme-color" content="#0066cc">` so non-installed browsers also pick it up.
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.

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 17 fail WCAG AA
REVIEW

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

3 pass 17 fail WCAG AA 2 pass AA only
h1 Don’t just measure
emissions.
2.30:1
#000000
on
#274F48
needs 3.0:1 (large text)
32px · bottom of viewport
h2 From supply chain data to
2.30:1
#000000
on
#274F48
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Built on emissions profiles from
2.30:1
#000000
on
#274F48
needs 3.0:1 (large text)
24px · bottom of viewport
h2 2 million companies worldwide
2.30:1
#000000
on
#274F48
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Why organisations trust DitchCarbon for …
2.30:1
#000000
on
#274F48
needs 3.0:1 (large text)
24px · bottom of viewport
h2 What our customers are saying
2.30:1
#000000
on
#274F48
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Explore the global supplier emissions la…
2.30:1
#000000
on
#274F48
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Build a complete picture of your supply …
2.30:1
#000000
on
#274F48
needs 3.0:1 (large text)
19px · bottom of viewport
h3 See where emissions actually sit across …
2.30:1
#000000
on
#274F48
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Turn insights into measurable emissions …
2.30:1
#000000
on
#274F48
needs 3.0:1 (large text)
19px · bottom of viewport
title DitchCarbon | Scope 3 Emissions Manageme…
1.35:1
#000000
on
#16281B
needs 4.5:1 (normal text)
16px · top of page (header area)
div Platform
1.45:1
#000000
on
#182E1E
needs 4.5:1 (normal text)
16px · top of page (header area)
div Overview
1.65:1
#000000
on
#1F3823
needs 4.5:1 (normal text)
16px · top of page (header area)
p Understand and act on your supply chain …
1.89:1
#000000
on
#264227
needs 4.5:1 (normal text)
16px · top of page (header area)
div Identify
2.38:1
#000000
on
#31522E
needs 4.5:1 (normal text)
16px · above the fold
p Build a complete, reliable picture of yo…
2.95:1
#000000
on
#3C6134
needs 4.5:1 (normal text)
16px · above the fold
div Analyse
3.84:1
#000000
on
#4D733F
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Don’t just measure…2.30:13.0:1
#000000
#274F48
Fail
h2 From supply chain da…2.30:13.0:1
#000000
#274F48
Fail
h2 Built on emissions p…2.30:13.0:1
#000000
#274F48
Fail
h2 2 million companies …2.30:13.0:1
#000000
#274F48
Fail
h2 Why organisations tr…2.30:13.0:1
#000000
#274F48
Fail
h2 What our customers a…2.30:13.0:1
#000000
#274F48
Fail
h2 Explore the global s…2.30:13.0:1
#000000
#274F48
Fail
h3 Build a complete pic…2.30:13.0:1
#000000
#274F48
Fail
h3 See where emissions …2.30:13.0:1
#000000
#274F48
Fail
h3 Turn insights into m…2.30:13.0:1
#000000
#274F48
Fail
title DitchCarbon | Scope …1.35:14.5:1
#000000
#16281B
Fail
div Platform1.45:14.5:1
#000000
#182E1E
Fail
div Overview1.65:14.5:1
#000000
#1F3823
Fail
p Understand and act o…1.89:14.5:1
#000000
#264227
Fail
div Identify2.38:14.5:1
#000000
#31522E
Fail
p Build a complete, re…2.95:14.5:1
#000000
#3C6134
Fail
div Analyse3.84:14.5:1
#000000
#4D733F
Fail
p Uncover the categori…4.82:14.5:1
#000000
#5F8347
Pass
div Act5.92:14.5:1
#000000
#71924E
Pass
p Reduce emissions wit…7.07:14.5:1
#000000
#80A054
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+
Heading Hierarchy
12 headings
PASS
12 headings
Info::
Single H1 present
  • H6 Explore company emissions data at scale
  • H6 Explore company emissionsdata at scale
  • H6 Explore company emissionsdata at scale
  • H1 Don’t just measure
emissions.Reduce them.
  • H2 From supply chain data to
emissions reductions
  • H3 Build a complete picture of your supply chain emissions in days, not months
  • H3 See where emissions actually sit across your supply chain
  • H3 Turn insights into measurable emissions reductions
  • H2 Built on emissions profiles from
2 million companies worldwide
  • H2 Why organisations trust DitchCarbon for Scope 3 emissions intelligence
  • H2 What our customers are saying
  • H2 Explore the global supplier emissions landscape
A+
Heading Text Quality
All 12 heading(s) have substantive, well-formed text
PASS
All 12 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A
Alt Text Quality
All 228 images OK
PASS
All 228 images OK
Info::
6 image(s) with alt text over 125 characters
Info::
136 decorative image(s) correctly marked
Info::
86 image(s) with good alt text
228 images 86 good alt text 136 decorative
IssueCount
too long6 image(s)
A+
Form Accessibility
All 5 controls labeled
PASS
All 5 controls labeled
Info::
5 control(s) properly labeled
5 controls
5 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#radioradionone
#radioradionone
#radioradionone
#radioradionone
#radioradionone
A+
Form Input Types
5 form control(s) checked, no type mismatches
PASS
5 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
5 form control(s) checked, no input-semantic issues
PASS
5 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
66 explicit tabindex attribute(s) checked, no anti-patterns
PASS
66 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
A
Iframe Accessibility
1/3 iframe(s) missing title; 0 placeholder(s)
PASS
1/3 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
A+
Tap Target Adequacy
All tap targets meet WCAG 2.5.5/2.5.8 sizing
PASS
All tap targets meet WCAG 2.5.5/2.5.8 sizing
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
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.
A
Lighthouse Accessibility Audits
Score 93/100 — 2 failing, 23 passed
PASS
93

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
Trusted by leading Scope 3 teams worldwide div.section_home-client > div.wrapper-loop_logo > div.text-center > div.text-size-small
95 div.w-dyn-item > div.explore_card-link > div.explore_link-right-block > div
85 div.w-dyn-item > div.explore_card-link > div.explore_link-right-block > div
75 div.w-dyn-item > div.explore_card-link > div.explore_link-right-block > div
65 div.w-dyn-item > div.explore_card-link > div.explore_link-right-block > div
55 div.w-dyn-item > div.explore_card-link > div.explore_link-right-block > div
0% div.explore_card-link-wrapper > a#block-transparency_1 > div.explore_link-right-block > div
0% div.explore_card-link-wrapper > a#block-transparency_2 > div.explore_link-right-block > div
0% div.explore_card-link-wrapper > a#block-transparency_3 > div.explore_link-right-block > div
0% div.explore_card-link-wrapper > a#block-transparency_4 > div.explore_link-right-block > div
0% div.explore_card-link-wrapper > a#block-transparency_5 > div.explore_link-right-block > div

These are opportunities to improve the legibility of your content.

Names and labels

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.w-dyn-item > div.home-company_bottom-block > div.home-company_right-image > a.w-inline-block div.w-dyn-item > div.home-company_bottom-block > div.home-company_right-image > a.w-inline-block
div.header-wrapper > div.header-wrapper_left > div.card-slider_nav > a#cms-slider-left div.header-wrapper > div.header-wrapper_left > div.card-slider_nav > a#cms-slider-left
div.header-wrapper > div.header-wrapper_left > div.card-slider_nav > a#cms-slider-right div.header-wrapper > div.header-wrapper_left > div.card-slider_nav > a#cms-slider-right
div.collection-ink > div.w-dyn-item > div.explore_card-link > a.cover-link div.collection-ink > div.w-dyn-item > div.explore_card-link > a.cover-link
div.collection-ink > div.w-dyn-item > div.explore_card-link > a.cover-link div.collection-ink > div.w-dyn-item > div.explore_card-link > a.cover-link
div.collection-ink > div.w-dyn-item > div.explore_card-link > a.cover-link div.collection-ink > div.w-dyn-item > div.explore_card-link > a.cover-link
div.collection-ink > div.w-dyn-item > div.explore_card-link > a.cover-link div.collection-ink > div.w-dyn-item > div.explore_card-link > a.cover-link
div.collection-ink > div.w-dyn-item > div.explore_card-link > a.cover-link div.collection-ink > div.w-dyn-item > div.explore_card-link > a.cover-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.

○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
●`[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
●`<frame>` or `<iframe>` elements have a title
●`<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
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
○`[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
○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
○`<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
○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
○`<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.
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback