Skip to content
https://capgemini.com

Accessibility

· 12 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
72
GRADE
C
FIX
3
REVIEW
4
PASS
5
INFO
0
Checks
12
5 PASS 4 REVIEW 3 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
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 ✗
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
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found - Capgemini ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
B
Favicon & Branding
4 icon(s) detected
REVIEW
4 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
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
color-scheme meta tag present
The site declares support for light and dark color schemes via <meta name='color-scheme'>.
Got: dark light
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 dark light ✓Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

C
Navigation UX
Action
2 navigation pattern(s)
REVIEW
2 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Info::
Skip navigation link detected
Info::
18 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search role='search' landmark
Skip Link Skip link detected
Labeled Navigation 18 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
4 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
A+
Landmark Structure
23 landmarks
PASS
23 landmarks
Info::
<main> landmark present
Info::
18 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER header NAV "mobileNavigation" SEARCH MAIN CONTENTINFO footer
A+
Heading Hierarchy
33 headings
PASS
33 headings
Info::
Single H1 present
  • H1 The resurgence of manufacturing
  • H2 Highlights
  • H3 The Scale Effect
  • H3 Fix connectivity, restore competitiveness: Europe’s next advantage
  • H3 Five years on the road to net zero
  • H3 We deliver real value
  • H2 Latest insights
  • H3 TechnoVision 2026 guide for CTOs and CIOs
  • H3 The multi-year AI advantage: Building the enterprise of tomorrow
  • H3 Reimagining customer experience: Human-led, AI-powered
  • H2 Recent client stories
  • H3 Introducing Nora for Nortura: How to Implement a Chatbot Solution for HR Support
  • H3 KION embraces a long-term path to net-zero carbon emissions
  • H3 Scottish Water leads utilities innovation by transitioning to an Oracle Utilities Customer Cloud Service
  • H2 Latest news
  • H3 Reindustrialization moves into a more selective, strategic phase in Europe and the US
  • H3 Two-thirds of organizations rate physical AI as a high priority for the next three to five years
  • H3 Change in the composition of Capgemini’s Board of Directors proposed to the 2026 Shareholders’ Meeting
  • H3 85% of banks’ corporate clients plan to engage with a non-bank financial institution within the next year as competition with private capital intensifies
  • H2 Inside stories
  • H3 DNA analysis for wildlife conservation
  • H3 Protecting water quality in reservoirs with AI
  • H3 Diagnosing rare childhood diseases
  • H3 Discover our 2024 Integrated Annual Report
  • H4 Partner for a digital and sustainable world
  • H3 Transforming sports
  • H4 Bringing expertise and passion for innovation and technology to Tour de France, the Ryder Cup, the America’s Cup, rugby, and motorsport.
  • H3 Capgemini Research Institute
  • H4 #1 in the world six consecutive times – an industry first.
  • H3 Capgemini Invent
  • H4 Our powerhouse of innovation, design and transformation.
  • H3 Capgemini Engineering
  • H4 Helping the world’s largest innovators engineer the products and services of tomorrow
A+
Alt Text Quality
All 139 images OK
PASS
All 139 images OK
Info::
89 decorative image(s) correctly marked
Info::
50 image(s) with good alt text
139 images 50 good alt text 89 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 3 controls labeled
PASS
All 3 controls labeled
Info::
3 control(s) properly labeled
3 controls
3 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#darkModeCheckboxMobilecheckboxDark and light mode toggle, currently light modefor/id
#darkModeCheckboxDesktopcheckboxDark and light mode toggle, currently light modefor/id
#keywordtextsearcharia-label
A+
Lighthouse Accessibility Audits
Score 97/100 — 2 failing, 28 passed
PASS
97

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.

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.content-box-wrapper > div.content-box > h1.title > a.analytics-hero-banner-title
div.content-box-wrapper > div.content-box > h1.title > a.analytics-hero-banner-title div.content-box-wrapper > div.content-box > h1.title > a.analytics-hero-banner-title
div.col-md-4 > div.box-inner > p.box-desc > a div.col-md-4 > div.box-inner > p.box-desc > a
div.col-md-4 > div.box-inner > p.box-desc > a div.col-md-4 > div.box-inner > p.box-desc > 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.

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
Five years on the road to net zero div.col-md-4 > div.box > div.box-wrapper > a.box-title
Report TechnoVision 2026 guide for CTOs and CIOs div.layout-single-card > div.row > div.col-12 > a.card-link-holder
Report The multi-year AI advantage: Building the enterprise of tomorrow div.layout-two-card > div.row > div.col-12 > a.card-link-holder
Capgemini Research Institute Reimagining customer experience: Human-led, AI-pow… div.layout-two-card > div.row > div.col-12 > a.card-link-holder
Introducing Nora for Nortura: How to Implement a Chatbot Solution for HR Suppor… div.row > div.col-12 > div.slide-info > 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
●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
●`[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
●`[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
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●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
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Uses ARIA roles only on compatible elements
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○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
○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.
○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>`.
○All heading elements contain content.
○Image elements do not have `[alt]` attributes that are redundant text.
○Identical links have the same purpose.
○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