Skip to content
https://bcg.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
52
GRADE
F
FIX
7
REVIEW
2
PASS
4
INFO
0
Checks
13
4 PASS 2 REVIEW 7 FIX
D
404 Error Page
Action
HTTP 404, custom page
FIX
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Info::
favicon.ico present at site root
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 Present
✗ PNG Icons Missing
✗ 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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
2 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 2 <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.
B
Alt Text Quality
8 of 97 images have issues
REVIEW
8 of 97 images have issues
Warning::
8 image(s) with filename as alt text
Info::
59 decorative image(s) correctly marked
Info::
30 image(s) with good alt text
97 images 30 good alt text 59 decorative 8 generic
IssueCount
filename8 image(s)
B
Form Accessibility
2 of 5 controls have issues
REVIEW
2 of 5 controls have issues
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="q">; <input type="text" name="q">
Info::
3 control(s) properly labeled
5 controls
3 labeled
2 placeholder only
0 unlabeled
ControlTypeLabelMethod
tabs-dropdown-select-selectView other itemsaria-label
tabs-dropdown-select-selectView other itemsaria-label
#35339166-0310-4b90-b633-7c92d75e1e39emailPlease provide an email address.aria-label
qtext(Type to search)placeholder only
qtext(Type to search)placeholder only

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

<input type="text" name="q">; <input type="text" name="q">

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

A
Landmark Structure
6 landmarks
PASS
6 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
1 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV 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

A
Heading Hierarchy
53 headings, 1 skip(s)
PASS
53 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Unlocking the Potential of Those Who Advance the World
  • H3 AI Has Made Work Reinvention a CEO Mandate skipped
  • H3 AI Has Made Work Reinvention a CEO Mandate
  • H3 BCG Treasury Benchmarking Survey: Activating the Balance Sheet
  • H3 BCG Treasury Benchmarking Survey: Activating the Balance Sheet
  • H3 The 2026 Insurance Value Creators Report: An Early Look at Returns
  • H3 The 2026 Insurance Value Creators Report: An Early Look at Returns
  • H3 Always-On Merchandising: How AI Agents Are Transforming Retail
  • H3 Always-On Merchandising: How AI Agents Are Transforming Retail
  • H3 How Physical AI Is Reshaping Robotics Today—and What Comes Next
  • H3 How Physical AI Is Reshaping Robotics Today—and What Comes Next
  • H3 From Ambition to Action: Redesigning Education for an AI-Driven Economy
  • H3 From Ambition to Action: Redesigning Education for an AI-Driven Economy
  • H2 How can we assist you today?
  • H2 Artificial Intelligence
  • H2 Business and Organizational Purpose
  • H2 Business Resilience
  • H2 Business Transformation
  • H2 Climate Change and Sustainability
  • H2 Corporate Finance and Strategy
  • H2 Cost Management
  • H2 Customer Insights
  • H2 Digital, Technology, and Data
  • H2 Inclusive Advantage
  • H2 Innovation Strategy and Delivery
  • H2 International Business
  • H2 M&A, Transactions, and PMI
  • H2 Manufacturing
  • H2 Marketing and Sales
  • H2 Operations
  • H2 Organization Strategy
  • H2 People Strategy
  • H2 Pricing and Revenue Management
  • H2 Risk Management and Compliance
  • H2 Social Impact
  • H2 Aerospace and Defense
  • H2 Automotive Industry
  • H2 Consumer Products Industry
  • H2 Education
  • H2 Energy
  • H2 Financial Institutions
  • H2 Health Care Industry
  • H2 Industrial Goods
  • H2 Insurance Industry
  • H2 Principal Investors and Private Equity
  • H2 Public Sector
  • H2 Retail Industry
  • H2 Technology, Media, and Telecommunications
  • H2 Transportation and Logistics
  • H2 Travel and Tourism
  • H2 Urban Planning
  • H2 Go Beyond the Expected
  • H3 BCG’s most inspiring thought leadership on issues shaping the future of business and society

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+
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 Unlocking the Potent…7.37:13.0:1
#000000
#999999
Pass
h2 How can we assist yo…7.37:13.0:1
#000000
#999999
Pass
h3 BCG’s most inspiri…7.37:13.0:1
#000000
#999999
Pass
title Strategic Management…7.37:14.5:1
#000000
#999999
Pass
a Skip to Main7.37:14.5:1
#000000
#999999
Pass
div Log in7.37:14.5:1
#000000
#999999
Pass
span Log error7.37:14.5:1
#000000
#999999
Pass
span View Profile7.37:14.5:1
#000000
#999999
Pass
a Edit Profile7.37:14.5:1
#000000
#999999
Pass
a Manage Subscriptions7.37:14.5:1
#000000
#999999
Pass
a My Saved Content7.37:14.5:1
#000000
#999999
Pass
a Logout7.37:14.5:1
#000000
#999999
Pass
span Our Services7.37:14.5:1
#000000
#999999
Pass
span Industries7.37:14.5:1
#000000
#999999
Pass
span Industries7.37:14.5:1
#000000
#999999
Pass
p Learn how we draw on…7.37:14.5:1
#000000
#999999
Pass
span Aerospace and Defens…7.37:14.5:1
#000000
#999999
Pass
span Aerospace and Defens…7.37:14.5:1
#000000
#999999
Pass
div Aerospace and Defens…7.37:14.5:1
#000000
#999999
Pass
p Our aerospace and de…7.37:14.5:1
#000000
#999999
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, 29 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

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-outerdiv02146140333402632 > div#pop-div208256299583615798 > div#pop-div302859657040405812 > iframe#pop-frame05035885624081321 div#pop-outerdiv02146140333402632 > div#pop-div208256299583615798 > div#pop-div302859657040405812 > iframe#pop-frame05035885624081321

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
AI Has Made Work Reinvention a CEO Mandate div.Promo20 > div.Promo-content > div.Promo-title__wrapper > h3.Promo-title

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
LOG IN section.Page-headerMenuRight > login-dropdown.user-info > div.login-container > button.login-button
○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
●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.
●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
●ARIA input fields have accessible names
●Elements use only permitted ARIA attributes
●Background and foreground colors have a sufficient contrast ratio
●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
●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.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements 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
○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
○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.
○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