Skip to content
https://roche.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
67
GRADE
D
FIX
5
REVIEW
3
PASS
5
INFO
0
Checks
13
5 PASS 3 REVIEW 5 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
Web Manifest
Action
Valid manifest
FIX
Valid manifest
Warning::
No name or short_name
Add a name field to identify the app.
Info::
192x192 icon present
Info::
512x512 icon present
PWA Install Criteria Not Installable
Name ✗192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode ✗
Icons 8 icon(s)
D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #fff
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 ModePartial Dark Mode
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::
8 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 8 <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
Favicon & Branding
17 icon(s) detected
REVIEW
17 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
SVG favicon detected — scales perfectly to any size
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✓ SVG Favicon Present
✓ Manifest Icons Present
✓ Multiple Sizes Present
B
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
REVIEW

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

20 pass 4 pass AA only
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Doing now what patie…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 We are Roche21.00:13.0:1
#000000
#FFFFFF
Pass
h2 In the spotlight21.00:13.0:1
#000000
#FFFFFF
Pass
h2 For Investors21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Join us!21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Celebrating 50 Years…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Roche Accessibility …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Raising the bar in h…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Rare within rare: Wo…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Haemophilia treatmen…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Haemophilia A in inf…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Identifying high-ris…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Halting disease prog…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Restoring health thr…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Helpful links21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Roche websites21.00:13.0:1
#000000
#FFFFFF
Pass
title Roche - Doing now wh…4.88:14.5:1
#000000
#7E7976
Pass
a skip to content4.89:14.5:1
#000000
#7E7977
Pass
a Stories4.96:14.5:1
#000000
#7F7A78
Pass
a Careers4.96:14.5:1
#000000
#7F7A78
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
Landmark Structure
17 landmarks
PASS
17 landmarks
Info::
<main> landmark present
Info::
8 <nav> landmark(s) found
Warning::
1 of 8 <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 "secondary 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

A+
Heading Hierarchy
27 headings
PASS
27 headings
Info::
Single H1 present
  • H1 Doing now what patients need next
  • H2 We are Roche
  • H2 In the spotlight
  • H3 How we improved outcomes for patients around the world
  • H3 Roche publishes its Full Year results for 2025
  • H2 For Investors
  • H3 Reporting
  • H3 Share and Bond information
  • H3 Finance Information Tool
  • H2 Discover great stories aboutSciencePartnershipCulturePatientsSociety
  • H3 Raising the bar in haemophilia A care
  • H3 Rare within rare: Women with haemophilia
  • H3 Haemophilia treatment for all: A partnership for better access
  • H3 Haemophilia A in infants
  • H3 Identifying high-risk patients
  • H3 Halting disease progression
  • H3 Restoring health through medicines
  • H2 Join us!
  • H2 Celebrating 50 Years of Genentech
  • H2 Roche Accessibility Statement
  • H3 About Roche
  • H3 Solutions
  • H3 Innovation
  • H3 Media
  • H3 Investors
  • H3 Helpful links
  • H3 Roche websites
A
Alt Text Quality
All 18 images OK
PASS
All 18 images OK
Info::
8 image(s) with alt text over 125 characters
Info::
10 image(s) with good alt text
18 images 10 good alt text
IssueCount
too long8 image(s)
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A+
Lighthouse Accessibility Audits
Score 100/100 — 1 failing, 31 passed
PASS
100

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.

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
How we improved outcomes for patients around the world With our combined stren… div.grid__columns > div.grid__column > div.teaser > a.teaser__link-wrapper
Roche publishes its Full Year results for 2025 Roche reports 7% (CER) sales fo… div.grid__columns > div.grid__column > div.teaser > a.teaser__link-wrapper
Rare within rare: Women with haemophilia April 14, 2022 div.swiper > div#swiper-wrapper-26d2f88c7127974a > div.swiper-slide > a.story-teaser
About Roche We unite leading science and technology across diagnostics, medici… div#swiper-wrapper-85314383fe8419c1 > div.swiper-slide > div.teaser > a.teaser__link-wrapper
○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
●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
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●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 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
○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
○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.
○`[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