Skip to content
https://merck.com

Accessibility

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

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::
1 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 1 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
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::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found - Merck.com ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✓
B
Favicon & Branding
7 icon(s) detected
REVIEW
7 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 Present
✓ Multiple Sizes Present
C
Web Manifest
Action
Valid manifest
REVIEW
Valid manifest
Warning::
No name or short_name
Add a name field to identify the app.
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name ✗192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓
Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 4 fail WCAG AA
REVIEW

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

16 pass 4 fail WCAG AA 4 pass AA only
span Search everything
1.07:1
#000000
on
#080C12
needs 4.5:1 (normal text)
16px · top of page (header area)
span Close
2.08:1
#000000
on
#513D39
needs 4.5:1 (normal text)
16px · top of page (header area)
span Menu
2.08:1
#000000
on
#4F3E3A
needs 4.5:1 (normal text)
16px · above the fold
span Close
3.00:1
#000000
on
#34615A
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 What can we help you…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Patients are our ins…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Explore our stories21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Related links21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Patients21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Investors21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Sustainability21.00:13.0:1
#000000
#FFFFFF
Pass
h3 About us21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Pipeline21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Clinical trials21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Connect with us on s…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Forward-Looking Stat…21.00:13.0:1
#000000
#FFFFFF
Pass
title Merck | Home4.65:14.5:1
#000000
#00857C
Pass
a Skip to content4.65:14.5:1
#000000
#00857C
Pass
span Search everything1.07:14.5:1
#000000
#080C12
Fail
span Close2.08:14.5:1
#000000
#513D39
Fail
span Menu2.08:14.5:1
#000000
#4F3E3A
Fail
span Close3.00:14.5:1
#000000
#34615A
Fail
a Main menu4.65:14.5:1
#000000
#00857C
Pass
a Company4.65:14.5:1
#000000
#00857C
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
5 landmarks
PASS
5 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV MAIN CONTENTINFO footer
A
Heading Hierarchy
16 headings
PASS
16 headings
Info::
Single H1 present
Warning::
3 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H4 Who we are
  • H2 What can we help you find?
  • H1 (empty)
  • H2 Patients are our inspiration as we continue the fight against cancer
  • H3 Patients
  • H3 Investors
  • H3 Sustainability
  • H2 Explore our stories
  • H3 About us
  • H3 Pipeline
  • H3 Clinical trials
  • H2 Related links
  • H3 Connect with us on social
  • H3 Forward-Looking Statement of Merck & Co., Inc., Rahway, N.J., USA
  • H3 (empty)
  • H3 (empty)

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

A+
Alt Text Quality
All 29 images OK
PASS
All 29 images OK
Info::
6 decorative image(s) correctly marked
Info::
23 image(s) with good alt text
29 images 23 good alt text 6 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 10 controls labeled
PASS
All 10 controls labeled
Info::
10 control(s) properly labeled
10 controls
10 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
stextSearch sitearia-label
#captions-foreground-color-brightcove-player-mco-b25-block-block_575ab70bc6e244ddefc011d419eca6da_component_425selectColorfor/id
#captions-foreground-opacity-brightcove-player-mco-b25-block-block_575ab70bc6e244ddefc011d419eca6da_component_425selectTransparencyfor/id
#captions-background-color-brightcove-player-mco-b25-block-block_575ab70bc6e244ddefc011d419eca6da_component_425selectColorfor/id
#captions-background-opacity-brightcove-player-mco-b25-block-block_575ab70bc6e244ddefc011d419eca6da_component_425selectTransparencyfor/id
#captions-window-color-brightcove-player-mco-b25-block-block_575ab70bc6e244ddefc011d419eca6da_component_425selectColorfor/id
#captions-window-opacity-brightcove-player-mco-b25-block-block_575ab70bc6e244ddefc011d419eca6da_component_425selectTransparencyfor/id
#captions-font-size-brightcove-player-mco-b25-block-block_575ab70bc6e244ddefc011d419eca6da_component_425selectFont Sizefor/id
#brightcove-player-mco-b25-block-block_575ab70bc6e244ddefc011d419eca6da_component_425selectText Edge Stylefor/id
#captions-font-family-brightcove-player-mco-b25-block-block_575ab70bc6e244ddefc011d419eca6da_component_425selectFont Familyfor/id
A
Lighthouse Accessibility Audits
Score 91/100 — 2 failing, 24 passed
PASS
91

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

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#site-navigation > div.wrapper > div#mastheadMenu > button#siteSearchToggle div#site-navigation > div.wrapper > div#mastheadMenu > button#siteSearchToggle

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.

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
Cookie Preferences div.menu-footer-menu-container > ul#menuFooter > li.menu-item > button#menu-item-763862

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
●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.
●`button`, `link`, and `menuitem` elements have accessible names
●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
●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
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●All heading elements contain content.
●Identical links have the same purpose.
○`[accesskey]` values are unique
○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 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 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.
○Skip links are focusable.
○No element has a `[tabindex]` value greater than 0
○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>`.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Elements with visible text labels have matching accessible names.
○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