Skip to content
https://deloitte.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
63
GRADE
D
FIX
4
REVIEW
5
PASS
4
INFO
0
Checks
13
4 PASS 5 REVIEW 4 FIX
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.

F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
5 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 5 <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.
B
Landmark Structure
9 landmarks
REVIEW
9 landmarks
Info::
<main> landmark present
Info::
5 <nav> landmark(s) found
Warning::
4 of 5 <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 "header navigation" 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

C
Form Accessibility
Action
3 of 18 controls have issues
REVIEW
3 of 18 controls have issues
Critical::
3 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select id="vjs_select_148">; <select id="vjs_select_167">; <select id="vjs_select_182">
Info::
15 control(s) properly labeled
18 controls
15 labeled
0 placeholder only
3 unlabeled
ControlTypeLabelMethod
Search locationinputsearch_locationaria-label
#vjs_select_98selectColorfor/id
#vjs_select_103selectOpacityfor/id
#vjs_select_113selectColorfor/id
#vjs_select_118selectOpacityfor/id
#vjs_select_128selectColorfor/id
#vjs_select_133selectOpacityfor/id
#ot-group-id-2checkboxAnalytics and performance cookiesfor/id
#ot-group-id-3checkboxFunctional cookiesfor/id
#ot-group-id-4checkboxAdvertising and targeting cookiesfor/id
#vendor-search-handlertextCookie list searcharia-label
#chkbox-idcheckboxcheckbox labelfor/id
#select-all-hosts-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-leg-handlercheckboxcheckbox labelfor/id
#vjs_select_182select(none)none
#vjs_select_148select(none)none
#vjs_select_167select(none)none

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

<select id="vjs_select_148">; <select id="vjs_select_167">; <select id="vjs_select_182">

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

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::
Navigation links present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 ✓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
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 11 fail WCAG AA
REVIEW

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

9 pass 11 fail WCAG AA
title Deloitte US | Together Makes Progress
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
span Link opens in a new tab
1.01:1
#000000
on
#030100
needs 4.5:1 (normal text)
16px · top of page (header area)
span opens in new window
1.04:1
#000000
on
#130301
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip to main content
1.06:1
#000000
on
#1B0206
needs 4.5:1 (normal text)
16px · top of page (header area)
a Who we are
1.18:1
#000000
on
#141A04
needs 4.5:1 (normal text)
16px · above the fold
a Overview
1.18:1
#000000
on
#141A06
needs 4.5:1 (normal text)
16px · above the fold
a Governance
1.19:1
#000000
on
#141B03
needs 4.5:1 (normal text)
16px · above the fold
a Recognition
1.12:1
#000000
on
#0E1403
needs 4.5:1 (normal text)
16px · above the fold
a Newsroom
1.03:1
#000000
on
#050601
needs 4.5:1 (normal text)
16px · above the fold
a Contact Us
1.01:1
#000000
on
#010200
needs 4.5:1 (normal text)
16px · above the fold
a About Deloitte
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 The SheBelieves Summ…5.24:13.0:1
#000000
#7F7F7F
Pass
h2 Advancing the game, …5.24:13.0:1
#000000
#7F7F7F
Pass
h2 Connecting the dots.…5.24:13.0:1
#000000
#7F7F7F
Pass
h2 Here’s how we use …5.24:13.0:1
#000000
#7F7F7F
Pass
h2 Privacy preference c…5.24:13.0:1
#000000
#7F7F7F
Pass
h3 Join us5.24:13.0:1
#000000
#7F7F7F
Pass
h3 Let's connect5.24:13.0:1
#000000
#7F7F7F
Pass
h3 Manage consent prefe…5.24:13.0:1
#000000
#7F7F7F
Pass
h3 Cookie List5.24:13.0:1
#000000
#7F7F7F
Pass
title Deloitte US | Togeth…1.00:14.5:1
#000000
#000000
Fail
span Link opens in a new …1.01:14.5:1
#000000
#030100
Fail
span opens in new window1.04:14.5:1
#000000
#130301
Fail
a Skip to main content1.06:14.5:1
#000000
#1B0206
Fail
a Who we are1.18:14.5:1
#000000
#141A04
Fail
a Overview1.18:14.5:1
#000000
#141A06
Fail
a Governance1.19:14.5:1
#000000
#141B03
Fail
a Recognition1.12:14.5:1
#000000
#0E1403
Fail
a Newsroom1.03:14.5:1
#000000
#050601
Fail
a Contact Us1.01:14.5:1
#000000
#010200
Fail
a About Deloitte1.00:14.5:1
#000000
#000000
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.

A+
Heading Hierarchy
33 headings
PASS
33 headings
Info::
Single H1 present
  • H3 Blockchain & Digital Assets
  • H3 Blockchain & Digital Assets
  • H3 Blockchain & Digital Assets
  • H3 Blockchain & Digital Assets
  • H3 Blockchain & Digital Assets
  • H1 The SheBelieves Summit: Where leadership meets sport
  • H2 Advancing the game, together
  • H2 Connecting the dots. That’s how progress happens.
  • H3 Our thinking
  • H3 The latest from Deloitte
  • H3 Board Practices Quarterly: Crisis management and the board
  • H3 Life & legal leadership: Build resilience through community
  • H3 AI and the future of human decision-making
  • H3 Dealing with AI’s cultural debt
  • H3 Our work
  • H4 Engineering a consolidated media supply chain for global reach
  • H4 Harnessing economic power and fueling a cleaner-energy future
  • H4 AI and analytics help a quick-service restaurant get even quicker
  • H3 Careers
  • H3 Join us
  • H3 Let's connect
  • H4 What we do
  • H4 Our thinking
  • H4 Careers
  • H5 Follow us
  • H2 Here’s how we use cookies
  • H2 Privacy preference center
  • H3 Manage consent preferences
  • H4 Strictly necessary cookies
  • H4 Analytics and performance cookies
  • H4 Functional cookies
  • H4 Advertising and targeting cookies
  • H3 Cookie List
A+
Alt Text Quality
All 23 images OK
PASS
All 23 images OK
Info::
17 decorative image(s) correctly marked
Info::
6 image(s) with good alt text
23 images 6 good alt text 17 decorative
All images have appropriate alt text.
A+
Print Stylesheet
Print styles detected
PASS
Print styles detected
Info::
External print stylesheet detected
Got: /etc.clientlibs/modern/clientlibs/clientlib-print.lc-1e606aa4c573700a4bbdb5a9f0c2ee1f-lc.min.css
Print Stylesheet ✓ Print Optimized
Print stylesheet /etc.clientlibs/modern/clientlibs/clientlib-print.lc-1e606aa4c573700a4bbdb5a9f0c2ee1f-lc.min.css ✓Inline @media print Not detected ✗
A+
Lighthouse Accessibility Audits
Score 96/100 — 2 failing, 28 passed
PASS
96

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.

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
Engineering a consolidated media supply chain for global reach Deloitte’s adva… div.dual-animation-slider > div#11db56a9 > div.cmp-dual-slider-v2__slide > ul.swiper-wrapper

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

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
Board Practices Quarterly: Crisis management and the board How do boards govern… div#-target-1-1 > div.aem-Grid > div.promo > a#promo-v3-46a0322d
Life & legal leadership: Build resilience through community In this episode, AD… div#-target-1-2 > div.aem-Grid > div.promo > a#promo-v3-737371fb
AI and the future of human decision-making As AI transforms decision-making, ho… div#-target-1-3 > div.aem-Grid > div.promo > a#promo-v3-77cd8ac3
Dealing with AI’s cultural debt AI may be creating an unnoticed, steady accumul… div#-target-1-4 > div.aem-Grid > div.promo > a#promo-v3-3ce159c0
10 reasons to join Deloitte div.button > div.cmp-button__modal > div#button-97f59b8f > a
○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.
●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 have a discernible name
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●`[lang]` attributes have a valid value
●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
○`button`, `link`, and `menuitem` elements have accessible names
○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
○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.
○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