Skip to content
https://novartis.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
71
GRADE
C
FIX
2
REVIEW
6
PASS
5
INFO
0
Checks
13
5 PASS 6 REVIEW 2 FIX
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: #ffffff
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.

F
Navigation UX
Action
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
7 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 7 <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
Landmark Structure
Action
9 landmarks
REVIEW
9 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
7 <nav> landmark(s) found
Warning::
2 of 7 <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 (missing!) CONTENTINFO footer

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

B
Alt Text Quality
2 of 25 images have issues
REVIEW
2 of 25 images have issues
Critical::
2 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
23 image(s) with good alt text
25 images 23 good alt text 2 missing
IssueCount
missing2 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 5 controls have issues
REVIEW
3 of 5 controls have issues
Critical::
3 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit" id="edit-submit-global-search">; <input type="submit" name="op" id="edit-button">; <input type="submit" id="edit-submit--2">
Info::
2 control(s) properly labeled
5 controls
2 labeled
0 placeholder only
3 unlabeled
ControlTypeLabelMethod
#edit-keywordtextSite Searchfor/id
#edit-keystextFooter Site Searchfor/id
#edit-buttonsubmit(none)none
#edit-submit-global-searchsubmit(none)none
#edit-submit--2submit(none)none

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

<input type="submit" id="edit-submit-global-search">; <input type="submit" name="op" id="edit-button">; <input type="submit" id="edit-submit--2">

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 Page Not Found | Novartis ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Favicon & Branding
Action
7 icon(s) detected
REVIEW
7 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::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
A
Heading Hierarchy
15 headings
PASS
15 headings
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H1 Reimagining medicine, together.
  • H2 Discover our medicines
  • H2 Explore our science
  • H2 Learn about our impact
  • H2 Join our team
  • H2 Latest news
  • H3 Novartis announces expansion of community health programs to close gaps in heart disease and cancer care, targeting more than 30 countries by 2030
  • H3 Novartis IgAN data in New England Journal of Medicine show Fabhalta® slowed kidney function decline by 49.3%
  • H3 Novartis agrees to acquire Excellergy, Inc., building on allergy leadership with next-generation anti-IgE innovation
  • H2 Manufacturing expansion in the United States
  • H2 Bringing breakthroughs to more patients
  • H1 Live. Magazine duplicate H1
  • H2 Annual reporting suite
  • H2 Resource links
  • H2 Novartis

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

A+
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: Novartis
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria ✓ Installable
Name Novartis ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode standalone ✓
Name Novartis Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)
A+
Print Stylesheet
Print styles detected
PASS
Print styles detected
Info::
External print stylesheet detected
Got: /sites/novartiscom/files/css/css_kpVXoafu3J4M1GfxRIw8hYKC_EwS9CZYaKu89Fk2Yp4.css?delta=2&language=en&theme=cosmos&include=eJx1kFtuAyEMRTfEzEhNpS7HMuDM0AGMbNMkuy959iPqF_j4dX1RlQxS_aZgLEtQnVECfB6-Pg7ghXeq0DDGVFfgI9hGcEwVa0iYQUh7NgVDn8l5MiMBOjdWiqMsj1CXlSoJZueZTU2wgUeRxMuRpbzTNbPHPKld8tjpAmthXbLJ81vGyjQp5aF4isIt8qk-k5pT2B2dbTTvS5TeMM-P0NUAGevacSW494-LXyRwryaXV8Y1FFyHsk2fg_7I3GvrPifdKDqlYdkG2BJgNw5cWiaj5R_ulG_uFYoJ4aps6H5D87C6jNqLGpXFo5L7SZEYqPjh7o7ZuuDyeO_UnWiMWLFQ7Td75xNNVzBdyXQUrkY1_gI1vcVa&0=tdwrnx
Print Stylesheet ✓ Print Optimized
Print stylesheet /sites/novartiscom/files/css/css_kpVXoafu3J4M1GfxRIw8hYKC_EwS9CZYaKu89Fk2Yp4.css?delta=2&language=en&theme=cosmos&include=eJx1kFtuAyEMRTfEzEhNpS7HMuDM0AGMbNMkuy959iPqF_j4dX1RlQxS_aZgLEtQnVECfB6-Pg7ghXeq0DDGVFfgI9hGcEwVa0iYQUh7NgVDn8l5MiMBOjdWiqMsj1CXlSoJZueZTU2wgUeRxMuRpbzTNbPHPKld8tjpAmthXbLJ81vGyjQp5aF4isIt8qk-k5pT2B2dbTTvS5TeMM-P0NUAGevacSW494-LXyRwryaXV8Y1FFyHsk2fg_7I3GvrPifdKDqlYdkG2BJgNw5cWiaj5R_ulG_uFYoJ4aps6H5D87C6jNqLGpXFo5L7SZEYqPjh7o7ZuuDyeO_UnWiMWLFQ7Td75xNNVzBdyXQUrkY1_gI1vcVa&0=tdwrnx ✓Inline @media print Not detected ✗
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 Reimagining medicine…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Live. Magazine21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Discover our medicin…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Explore our science21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Learn about our impa…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Join our team21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Latest news21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Manufacturing expans…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Bringing breakthroug…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Annual reporting sui…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Resource links21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Novartis21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Novartis announces e…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Novartis IgAN data i…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Novartis agrees to a…21.00:13.0:1
#000000
#FFFFFF
Pass
title Novartis20.47:14.5:1
#000000
#FCFCFC
Pass
a Skip to main content20.47:14.5:1
#000000
#FCFCFC
Pass
span Search20.29:14.5:1
#000000
#FBFBFB
Pass
label Site Search20.47:14.5:1
#000000
#FCFCFC
Pass
button Global20.47:14.5:1
#000000
#FCFCFC
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 97/100 — 1 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.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Terms of use div.bottom-organsim > ul.clearfix > li.nav-item > a.nav-link
Privacy div.bottom-organsim > ul.clearfix > li.nav-item > a.nav-link
Cookie Settings div.bottom-organsim > ul.clearfix > li.nav-item > a.ot-sdk-show-settings
Contacts div.bottom-organsim > ul.clearfix > li.nav-item > a.nav-link
Locations div.bottom-organsim > ul.clearfix > li.nav-item > a.nav-link
Site map div.bottom-organsim > ul.clearfix > li.nav-item > a.nav-link
Open source div.bottom-organsim > ul.clearfix > li.nav-item > a.nav-link
Web accessibility div.bottom-organsim > ul.clearfix > li.nav-item > a.nav-link

These items highlight common accessibility best practices.

○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
●Input buttons have discernible text.
●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
●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
●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
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[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 type="image">` elements have `[alt]` text
○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.
○`[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