Skip to content
https://bain.com

Accessibility

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

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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
3 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 3 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
C
Heading Hierarchy
Action
78 headings, 1 skip(s)
REVIEW
78 headings, 1 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H4 Offices
  • H5 North & Latin America
  • H5 Europe & Africa
  • H5 Middle East
  • H5 Asia & Australia
  • H4 Select your region and language
  • H5 Global
  • H5 North & Latin America
  • H5 Europe, Middle East, & Africa
  • H5 Asia & Australia
  • H4 You have no saved items.
  • H4 Industries
  • H5 Media & Entertainment
  • H5 Private Equity
  • H5 Telecommunications
  • H4 Consulting Services
  • H4 Insights
  • H5 Featured topics
  • H4 About
  • H5 Further: Our global responsibility
  • H4 Careers
  • H5 Work with Us
  • H5 Life at Bain
  • H5 Hiring Process
  • H4 Offices
  • H5 North & Latin America
  • H5 Europe & Africa
  • H5 Middle East
  • H5 Asia & Australia
  • H4 Select your region and language
  • H5 Global
  • H5 North & Latin America
  • H5 Europe, Middle East, & Africa
  • H5 Asia & Australia
  • H4 You have no saved items.
  • H4 Industries
  • H4 Consulting Services
  • H4 Insights
  • H5 Featured topics
  • H4 About
  • H5 Further: Our global responsibility
  • H6 Popular Searches
  • H6 Your Previous Searches
  • H6 Recently Visited Pages
  • H2 CFOs Funded the AI Revolution. Now They’re Joining It.
  • H2 CFOs Funded the AI Revolution. Now They’re Joining It.
  • H2 Unlock the Value of Industrial Intelligence
  • H2 Unlock the Value of Industrial Intelligence
  • H2 Delivering Growth in a World That Won’t Sit Still
  • H2 Delivering Growth in a World That Won’t Sit Still
  • H2 Why Agentic AI Demands a New Architecture
  • H2 Why Agentic AI Demands a New Architecture
  • H2 We champion the bold to achieve the extraordinary.
  • H2 Bold steps forward.
  • H3 Featured client success story
  • H4 Banca Investis Transforms Customer Dialogue with a Generative AI Engine
  • H4 Banca Investis Transforms Customer Dialogue with a Generative AI Engine
  • H2 500+
  • H2 7
  • H3 Featured client success story
  • H4 An EPC Leader Transforms Itself Amid Intense Volatility
  • H2 $300M
  • H2 2.5x
  • H3 Featured client success story
  • H4 The Hera Group Prepares to Power Up with Generative AI
  • H4 The Hera Group Prepares to Power Up with Generative AI
  • H2 150
  • H2 5
  • H3 Featured client success story
  • H4 How NatWest Is Scaling Customer Engagement with AI
  • H2 90%
  • H2 Zero
  • H2 AI’s Evolution: What Good Looks Like Now
  • H3 Our Latest Insights
  • H5 Claude Mythos and the AI Cybersecurity Wake-Up Call skipped
  • H5 From Roadmap to Reality: Phasing Agentic AI into Production
  • H2 What can we help you achieve?
  • H2 Where will your career take you?

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

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

C
Alt Text Quality
Action
4 of 37 images have issues
REVIEW
4 of 37 images have issues
Critical::
4 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
32 decorative image(s) correctly marked
Info::
1 image(s) with good alt text
37 images 1 good alt text 32 decorative 4 missing
IssueCount
missing4 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

C
Form Accessibility
Action
3 of 67 controls have issues
REVIEW
3 of 67 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_696">; <select id="vjs_select_715">; <select id="vjs_select_730">
Info::
64 control(s) properly labeled
67 controls
64 labeled
0 placeholder only
3 unlabeled
ControlTypeLabelMethod
#nav-site-search-inputinputSearch insights, services, and experts"for/id
#over_195radioAdvanced Manufacturing & Servicesfor/id
#over_178radioAerospace & Defensefor/id
#over_186radioAgribusinessfor/id
#over_176radioAutomotivefor/id
#over_196radioAviationfor/id
#over_180radioChemicalsfor/id
#over_191radioConstruction & Infrastructurefor/id
#over_170radioConsumer Productsfor/id
#over_173radioEnergy & Natural Resourcesfor/id
#over_200radioFinancial Servicesfor/id
#over_187radioHealthcare & Life Sciencesfor/id
#over_172radioMachinery & Equipmentfor/id
#over_193radioMedia & Entertainmentfor/id
#over_174radioMiningfor/id
#over_179radioOil & Gasfor/id
#over_171radioPaper & Packagingfor/id
#over_168radioPrivate Equityfor/id
#over_177radioRetailfor/id
#over_181radioSocial Impactfor/id
#over_175radioTechnologyfor/id
#over_194radioTelecommunicationsfor/id
#over_435radioChange Managementfor/id
#over_437radioCost Reductionfor/id
#over_4605radioCustomer Experiencefor/id
#over_4607radioData Analyticsfor/id
#over_4608radioDigital Strategyfor/id
#over_4606radioInnovationfor/id
#over_438radioMarket Expansionfor/id
#over_4603radioOperationsfor/id
#over_434radioOrganizationfor/id
#over_436radioRevenue Growthfor/id
#over_4604radioSales & Marketingfor/id
#over_439radioTransformationfor/id
#cat_177radioRetailfor/id
#cat_168radioPrivate Equityfor/id
#cat_195radioAdvanced Manufacturing & Servicesfor/id
#cat_175radioTechnologyfor/id
#cat_179radioOil & Gasfor/id
#cat_187radioHealthcare & Life Sciencesfor/id
#cat_180radioChemicalsfor/id
#cat_170radioConsumer Productsfor/id
#cat_174radioMiningfor/id
#cat_200radioFinancial Servicesfor/id
#cat_4607radioData Analyticsfor/id
#cat_435radioChange Managementfor/id
#cat_437radioCost Reductionfor/id
#cat_4605radioCustomer Experiencefor/id
#cat_4608radioDigital Strategyfor/id
#cat_4606radioInnovationfor/id
#cat_438radioMarket Expansionfor/id
#cat_4603radioOperationsfor/id
#cat_434radioOrganizationfor/id
#cat_436radioRevenue Growthfor/id
#vjs_select_646selectColorfor/id
#vjs_select_651selectOpacityfor/id
#vjs_select_661selectColorfor/id
#vjs_select_666selectOpacityfor/id
#vjs_select_676selectColorfor/id
#vjs_select_681selectOpacityfor/id
#Email2emailYour email addressnone
privacy-policycheckboxnone
#Emailemail*for/id
#mktoCheckbox_10108_0checkbox*I have read the Privacy Policy and agree to its terms.for/id
#vjs_select_715select(none)none
#vjs_select_730select(none)none
#vjs_select_696select(none)none

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

<select id="vjs_select_696">; <select id="vjs_select_715">; <select id="vjs_select_730">

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

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 Error | Bain & Company Custom Styling Navigation Homepage Link Search Form
B
Favicon & Branding
26 icon(s) detected
REVIEW
26 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
A+
Landmark Structure
11 landmarks
PASS
11 landmarks
Info::
<main> landmark present
Info::
3 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Utility Navigation" MAIN CONTENTINFO footer
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
h2 CFOs Funded the AI R…7.28:13.0:1
#000000
#989898
Pass
h2 CFOs Funded the AI R…7.28:13.0:1
#000000
#989898
Pass
h2 Unlock the Value of …7.28:13.0:1
#000000
#989898
Pass
h2 Unlock the Value of …7.28:13.0:1
#000000
#989898
Pass
h2 Delivering Growth in…7.28:13.0:1
#000000
#989898
Pass
h2 Delivering Growth in…7.28:13.0:1
#000000
#989898
Pass
h2 Why Agentic AI Deman…7.28:13.0:1
#000000
#989898
Pass
h2 Why Agentic AI Deman…7.28:13.0:1
#000000
#989898
Pass
h2 We champion the bold…7.28:13.0:1
#000000
#989898
Pass
h2 Bold steps forward.7.28:13.0:1
#000000
#989898
Pass
h2 500+7.28:13.0:1
#000000
#989898
Pass
h2 $300M7.28:13.0:1
#000000
#989898
Pass
h2 2.5x7.28:13.0:1
#000000
#989898
Pass
h2 1507.28:13.0:1
#000000
#989898
Pass
h2 90%7.28:13.0:1
#000000
#989898
Pass
h2 Zero7.28:13.0:1
#000000
#989898
Pass
h2 AI’s Evolution: Wh…7.28:13.0:1
#000000
#989898
Pass
h2 What can we help you…7.28:13.0:1
#000000
#989898
Pass
h2 Where will your care…7.28:13.0:1
#000000
#989898
Pass
h3 Featured client succ…7.28:13.0:1
#000000
#989898
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 96/100 — 3 failing, 32 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.

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
div#pop-outerdiv01324287338026574 > div#pop-div2011491378183956336 > div#pop-div305473878237723729 > div#pop-frame047696292254098216 div#pop-outerdiv01324287338026574 > div#pop-div2011491378183956336 > div#pop-div305473878237723729 > div#pop-frame047696292254098216

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
Claude Mythos and the AI Cybersecurity Wake-Up Call div.card__content-container > div.card__content > a > h5

These are opportunities to improve keyboard navigation in your application.

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
Hannover Messe 2026 Unlock the Value of Industrial Intelligence MEET US AT THE… div#slick-slide31 > div > div.hero__slide > a.hero__text-content
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
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
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
Touch targets have sufficient size and spacing.
`[lang]` attributes have a valid value
Skip links are focusable.
Document has a main landmark.
Deprecated ARIA roles were not used
`<video>` elements contain a `<track>` element with `[kind="captions"]`
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 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
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
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.
Uses ARIA roles only on compatible elements
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