Skip to content
https://clarivate.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
56
GRADE
D
FIX
6
REVIEW
4
PASS
3
INFO
0
Checks
13
3 PASS 4 REVIEW 6 FIX
D
Landmark Structure
Action
36 landmarks
FIX
36 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
3 <nav> landmark(s) found
Warning::
3 of 3 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Warning::
Skip navigation link is missing (WCAG 2.4.1)
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
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

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more ▾

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

F
Heading Hierarchy
Action
58 headings, 6 skip(s)
FIX
58 headings, 6 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H5 Product logins
  • H1 Let our intelligencemove you
  • H2 Our solutions are trusted by millions of people around the world
  • H5 Premium Data Sets skipped
  • H5 Insights & Analytics​
  • H5 Workflow Solutions​
  • H5 Expert Services​
  • H2 Whatever your world, we’re here to help you succeed
  • H5 Academia & Government skipped
  • H5 Life Sciences & Healthcare
  • H5 Intellectual Property
  • H2 Our most popular products
  • H5 Web of Science Platform skipped
  • H5 Alma - Ex Libris
  • H5 ProQuest One Academic
  • H5 Cortellis
  • H5 Medtech 360
  • H5 IPfolio
  • H5 Derwent Patent Search (formerly Derwent Innovation)
  • H5 CompuMark trademark solutions
  • H2 What our customers think
  • H2 Unparalleled expertise
  • H5 Nandita Quaderi skipped
  • H5 Jonathan Adams
  • H5 David Pendlebury
  • H5 Juliane Ray
  • H5 Ed White
  • H5 Annya Dushine
  • H2 Insights you trust
  • H3 The Top 100 Global Innovators
  • H3 Drugs to Watch
  • H3 Highly Cited Researchers
  • H3 Rare Disease Innovation - Navigating Capital, Complexity, and Clinical Opportunity​
  • H5 Rare Disease Innovation - Navigating Capital, Complexity, and Clinical Opportunity​ skipped
  • H5 The Top 100 Global Innovators
  • H5 Drugs to Watch
  • H5 Highly Cited Researchers
  • H5 Rare Disease Innovation - Navigating Capital, Complexity, and Clinical Opportunity​
  • H5 The Top 100 Global Innovators
  • H5 Drugs to Watch
  • H5 Highly Cited Researchers
  • H5 Rare Disease Innovation - Navigating Capital, Complexity, and Clinical Opportunity​
  • H2 Latest stories
  • H5 Insight or information? What trademark leaders really need from their IP management system skipped
  • H5 The real-world impact of AI on modern IP decision making
  • H5 Who wins at the Unified Patent Court? Clear signals from two years of decisions
  • H5 Roadmap to Future Energy Innovation – Perovskite Solar Cells
  • H5 A more transparent, connected experience in Web of Science Research Assistant
  • H5 The real-world impact of AI on modern IP decision making
  • H5 Who wins at the Unified Patent Court? Clear signals from two years of decisions
  • H5 Roadmap to Future Energy Innovation – Perovskite Solar Cells
  • H5 A more transparent, connected experience in Web of Science Research Assistant
  • H5 The real-world impact of AI on modern IP decision making
  • H4 Follow us
  • H4 Contact us
  • H5 Search Clarivate
  • H4 Fraud Warning
  • H4 Federal Transparency In Coverage Rule

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

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

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

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

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

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

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: #b175e1
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
No navigation patterns
FIX
No navigation patterns
Info::
3 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 3 <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.
C
404 Error Page
Action
HTTP 404, custom page
REVIEW
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 ✓Page Title Page not found | Clarivate ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
B
Favicon & Branding
22 icon(s) detected
REVIEW
22 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
B
Web Manifest
PWA-ready
REVIEW
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: Clarivate
Info::
192x192 icon present
Info::
Display mode: standalone
PWA Install Criteria ✓ Installable
Name Clarivate ✓192×192 icon ✓512×512 icon ✗Start URL / ✓Display Mode standalone ✓
Name Clarivate Display Mode standalone Icons 6 icon(s)
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 17 fail WCAG AA
REVIEW

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

3 pass 17 fail WCAG AA
h1 Let our intelligence
1.62:1
#000000
on
#3C2D36
needs 3.0:1 (large text)
32px · bottom of viewport
h1 move you
1.62:1
#000000
on
#3C2D36
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Our solutions are trusted by millions of…
1.62:1
#000000
on
#3C2D36
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Whatever your world, we’re here to hel…
1.62:1
#000000
on
#3C2D36
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Our most popular products
1.62:1
#000000
on
#3C2D36
needs 3.0:1 (large text)
24px · bottom of viewport
h2 What our customers think
1.62:1
#000000
on
#3C2D36
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Unparalleled expertise
1.62:1
#000000
on
#3C2D36
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Insights you trust
1.62:1
#000000
on
#3C2D36
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Latest stories
1.62:1
#000000
on
#3C2D36
needs 3.0:1 (large text)
24px · bottom of viewport
h3 The Top 100 Global Innovators
1.62:1
#000000
on
#3C2D36
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Drugs to Watch
1.62:1
#000000
on
#3C2D36
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Highly Cited Researchers
1.62:1
#000000
on
#3C2D36
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Rare Disease Innovation - Navigating Cap…
1.62:1
#000000
on
#3C2D36
needs 3.0:1 (large text)
19px · bottom of viewport
title Clarivate - Leading Global Transformativ…
1.30:1
#000000
on
#202124
needs 4.5:1 (normal text)
16px · top of page (header area)
strong Support
1.77:1
#000000
on
#3F3535
needs 3.0:1 (large text)
16px · above the fold
strong Investors
2.14:1
#000000
on
#51403A
needs 3.0:1 (large text)
16px · above the fold
strong Careers
2.00:1
#000000
on
#4E3B35
needs 3.0:1 (large text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Let our intelligence1.62:13.0:1
#000000
#3C2D36
Fail
h1 move you1.62:13.0:1
#000000
#3C2D36
Fail
h2 Our solutions are tr…1.62:13.0:1
#000000
#3C2D36
Fail
h2 Whatever your world,…1.62:13.0:1
#000000
#3C2D36
Fail
h2 Our most popular pro…1.62:13.0:1
#000000
#3C2D36
Fail
h2 What our customers t…1.62:13.0:1
#000000
#3C2D36
Fail
h2 Unparalleled experti…1.62:13.0:1
#000000
#3C2D36
Fail
h2 Insights you trust1.62:13.0:1
#000000
#3C2D36
Fail
h2 Latest stories1.62:13.0:1
#000000
#3C2D36
Fail
h3 The Top 100 Global I…1.62:13.0:1
#000000
#3C2D36
Fail
h3 Drugs to Watch1.62:13.0:1
#000000
#3C2D36
Fail
h3 Highly Cited Researc…1.62:13.0:1
#000000
#3C2D36
Fail
h3 Rare Disease Innovat…1.62:13.0:1
#000000
#3C2D36
Fail
title Clarivate - Leading …1.30:14.5:1
#000000
#202124
Fail
div Discover8.63:14.5:1
#000000
#A6A6A7
Pass
strong Clarivate21.00:13.0:1
#000000
#FFFFFF
Pass
div search21.00:14.5:1
#000000
#FFFFFF
Pass
strong Support1.77:13.0:1
#000000
#3F3535
Fail
strong Investors2.14:13.0:1
#000000
#51403A
Fail
strong Careers2.00:13.0:1
#000000
#4E3B35
Fail

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+
Alt Text Quality
All 68 images OK
PASS
All 68 images OK
Info::
4 decorative image(s) correctly marked
Info::
64 image(s) with good alt text
68 images 64 good alt text 4 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 2 controls labeled
PASS
All 2 controls labeled
Info::
2 control(s) properly labeled
2 controls
2 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#customer-logins-search-inputtextSearcharia-label
searchsearchSearch fieldaria-label
A+
Lighthouse Accessibility Audits
Score 95/100 — 2 failing, 25 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

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
Premium Data Sets div.card-body > div.d-flex > div > h5.card-title
Academia & Government div.card-body > div.d-flex > div > h5.card-title
Web of Science Platform div.card-body > div.d-flex > div > h5.card-title
Nandita Quaderi div.card-body > div.d-flex > div > h5.card-title
The Top 100 Global Innovators div.card-body > div.d-flex > div > h5.card-title
Insight or information? What trademark leaders really need from their IP manage… div.card-body > div.d-flex > div > h5.card-title

These are opportunities to improve keyboard navigation in your application.

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
Standards div.col-lg-8 > ul#menu-footer-legal-menu > li#menu-item-153410 > a
Career Fraud Warning div.col-lg-8 > ul#menu-footer-legal-menu > li#menu-item-183666 > a

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
●`[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
●ARIA `progressbar` elements have accessible names
●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
●Document has a main landmark.
●Deprecated ARIA roles were not used
●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
○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.
○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.
○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