Skip to content
https://rdcu.be

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
56
GRADE
D
FIX
6
REVIEW
3
PASS
4
INFO
0
Checks
13
4 PASS 3 REVIEW 6 FIX
F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
Soft 404: server returns HTTP 200 for non-existent pages
The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.
Got: Status: 200 for /beavercheck-404-test-bzpsb4
404 Page Quality ✗ Soft 404 (HTTP 200)
Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://rdcu.be/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://rdcu.be/manifest.json

Manifest contains invalid JSON.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
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 ModeNo Dark Mode Detected
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 ✗
D
Navigation UX
Action
2 navigation pattern(s)
FIX
2 navigation pattern(s)
Info::
Skip navigation link detected
Info::
Back-to-top link detected
Info::
5 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 5 <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.
C
Alt Text Quality
Action
14 of 28 images have issues
REVIEW
14 of 28 images have issues
Critical::
14 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
4 decorative image(s) correctly marked
Info::
10 image(s) with good alt text
28 images 10 good alt text 4 decorative 14 missing
IssueCount
missing14 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

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
Lighthouse Accessibility Audits
Score 82/100 — 5 failing, 27 passed
REVIEW
82

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.

ARIA

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
R&D Teams nav > ul#menu-use-cases > li#menu-item-32615 > a
Medical Affairs nav > ul#menu-use-cases > li#menu-item-32614 > a
Pharmacovigilance nav > ul#menu-use-cases > li#menu-item-32613 > a
Corporate Libraries & Knowledge Centers nav > ul#menu-use-cases > li#menu-item-32612 > a
Non-Profit Organizations nav > ul#menu-use-cases > li#menu-item-31849 > a
Health and Environmental Agencies nav > ul#menu-use-cases > li#menu-item-31850 > a
Regulatory Agencies nav > ul#menu-use-cases > li#menu-item-31851 > a
Government Organizations nav > ul#menu-use-cases > li#menu-item-31852 > a
Literature Management nav > ul#menu-features > li#menu-item-31504 > a
Literature Monitoring nav > ul#menu-features > li#menu-item-31855 > a
AI Assistant nav > ul#menu-features > li#menu-item-31854 > a
Literature Review nav > ul#menu-features > li#menu-item-31503 > a
Document Delivery nav > ul#menu-features > li#menu-item-32552 > a
SmartCite nav > ul#menu-features > li#menu-item-32559 > a
News nav > ul#menu-resources > li#menu-item-31512 > a
Case Studies nav > ul#menu-resources > li#menu-item-32481 > a
White Papers nav > ul#menu-resources > li#menu-item-32483 > a
Training Center nav > ul#menu-support > li#menu-item-32475 > a
Download Center nav > ul#menu-support > li#menu-item-32476 > a
Release Notes nav > ul#menu-support > li#menu-item-32477 > a
Help Center nav > ul#menu-support > li#menu-item-32501 > a
Submit a Ticket nav > ul#menu-support > li#menu-item-32479 > a
Supported Styles nav > ul#menu-support > li#menu-item-32480 > a
Terms nav > ul#menu-privacty-terms > li#menu-item-31242 > a
Privacy nav > ul#menu-privacty-terms > li#menu-item-31243 > a
Security Statement nav > ul#menu-privacty-terms > li#menu-item-31244 > a
Data Protection nav > ul#menu-privacty-terms > li#menu-item-31245 > a
Cookie Policy nav > ul#menu-privacty-terms > li#menu-item-31246 > a

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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
Use Cases div.fl-col-group > div.fl-col > div.fl-col-content > h5.fl-module

These are opportunities to improve keyboard navigation in your application.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
article.logo-wrapper > div.logo-marquee > div.logo-marquee__group > img.marquee_logo article.logo-wrapper > div.logo-marquee > div.logo-marquee__group > img.marquee_logo
article.logo-wrapper > div.logo-marquee > div.logo-marquee__group > img.marquee_logo article.logo-wrapper > div.logo-marquee > div.logo-marquee__group > img.marquee_logo
article.logo-wrapper > div.logo-marquee > div.logo-marquee__group > img.marquee_logo article.logo-wrapper > div.logo-marquee > div.logo-marquee__group > img.marquee_logo
article.logo-wrapper > div.logo-marquee > div.logo-marquee__group > img.marquee_logo article.logo-wrapper > div.logo-marquee > div.logo-marquee__group > img.marquee_logo
article.logo-wrapper > div.logo-marquee > div.logo-marquee__group > img.marquee_logo article.logo-wrapper > div.logo-marquee > div.logo-marquee__group > img.marquee_logo
article.logo-wrapper > div.logo-marquee > div.logo-marquee__group > img.marquee_logo article.logo-wrapper > div.logo-marquee > div.logo-marquee__group > img.marquee_logo
article.logo-wrapper > div.logo-marquee > div.logo-marquee__group > img.marquee_logo article.logo-wrapper > div.logo-marquee > div.logo-marquee__group > img.marquee_logo

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.fl-module-content > div.pp-social-icons > span.pp-social-icon > a div.fl-module-content > div.pp-social-icons > span.pp-social-icon > a
div.fl-module-content > div.pp-social-icons > span.pp-social-icon > a div.fl-module-content > div.pp-social-icons > span.pp-social-icon > a
div.fl-module-content > div.pp-social-icons > span.pp-social-icon > a div.fl-module-content > div.pp-social-icons > span.pp-social-icon > a
div.fl-module-content > div.pp-social-icons > span.pp-social-icon > a div.fl-module-content > div.pp-social-icons > span.pp-social-icon > 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.

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
Privacy nav > ul#menu-privacty-terms > li#menu-item-31243 > a
Security Statement nav > ul#menu-privacty-terms > li#menu-item-31244 > a
Data Protection nav > ul#menu-privacty-terms > li#menu-item-31245 > a
Cookie Policy nav > ul#menu-privacty-terms > li#menu-item-31246 > 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
●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●`[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
●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
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Uses ARIA roles only on compatible elements
●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 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.
○`[lang]` attributes have a valid value
○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.
○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.
A+
Landmark Structure
8 landmarks
PASS
8 landmarks
Info::
<main> landmark present
Info::
5 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Menu" MAIN CONTENTINFO footer
A
Heading Hierarchy
35 headings, 1 skip(s)
PASS
35 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Transform how your team works with scholarly literature
  • H2 Discover how ReadCube can revolutionize your workflow.
  • H3 Stop searching, start discovering
  • H3 Make your library work for you.
  • H3 Absorb and understand faster with AI.
  • H3 Say goodbye to fragmented workflows
  • H3 Stop searching, start discovering
  • H3 Make your library work for you.
  • H3 Absorb and understand faster with AI.
  • H3 Say goodbye to fragmented workflows
  • H4 Hundreds of companies, from startups to global leaders, trust ReadCube’s award-winning platform to transform how they work with scholarly literature.
  • H2 Built for your team, however you work.
  • H3 Corporate Libraries & Knowledge Centers
  • H3 Pharmacovigilance
  • H3 Medical Affairs
  • H3 R&D Teams
  • H3 Regulatory Agencies
  • H3 Non-Profit Organizations
  • H3 Health & Environmental Agencies
  • H3 Government Organizations
  • H2 Find a plan that works for your team
  • H3 ReadCube
  • H3 ReadCube Pro
  • H3 ReadCube SLR
  • H5 Use Cases skipped
  • H5 Features
  • H5 Resources
  • H5 Support
  • H2 Cookie settings
  • H3 Manage cookie preferences
  • H4 Strictly Necessary Cookies
  • H4 Functional Cookies
  • H4 Performance Cookies
  • H4 Targeting Cookies
  • H3 Cookie List

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

A+
Form Accessibility
All 8 controls labeled
PASS
All 8 controls labeled
Info::
8 control(s) properly labeled
8 controls
8 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#ot-group-id-C0003checkboxFunctional Cookiesfor/id
#ot-group-id-C0002checkboxPerformance Cookiesfor/id
#ot-group-id-C0004checkboxTargeting Cookiesfor/id
#vendor-search-handlertextCookie list searcharia-label
#chkbox-idcheckboxcheckbox labelfor/id
#select-all-hosts-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-leg-handlercheckboxcheckbox labelfor/id
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 how your team works …20.00:13.0:1
#000000
#FBF9F7
Pass
h2 Discover how ReadCub…20.00:13.0:1
#000000
#FBF9F7
Pass
h2 your workflow.20.00:13.0:1
#000000
#FBF9F7
Pass
h2 , however you work.20.00:13.0:1
#000000
#FBF9F7
Pass
h2 Find a plan that wor…20.00:13.0:1
#000000
#FBF9F7
Pass
h2 Cookie settings20.00:13.0:1
#000000
#FBF9F7
Pass
h3 Corporate Libraries …20.00:13.0:1
#000000
#FBF9F7
Pass
h3 Pharmacovigilance20.00:13.0:1
#000000
#FBF9F7
Pass
h3 Medical Affairs20.00:13.0:1
#000000
#FBF9F7
Pass
h3 R&D Teams20.00:13.0:1
#000000
#FBF9F7
Pass
h3 Regulatory Agencies20.00:13.0:1
#000000
#FBF9F7
Pass
h3 Non-Profit Organizat…20.00:13.0:1
#000000
#FBF9F7
Pass
h3 Health & Environment…20.00:13.0:1
#000000
#FBF9F7
Pass
h3 Government Organizat…20.00:13.0:1
#000000
#FBF9F7
Pass
h3 ReadCube20.00:13.0:1
#000000
#FBF9F7
Pass
h3 ReadCube Pro20.00:13.0:1
#000000
#FBF9F7
Pass
h3 ReadCube SLR20.00:13.0:1
#000000
#FBF9F7
Pass
h3 Manage cookie prefer…20.00:13.0:1
#000000
#FBF9F7
Pass
h3 Cookie List20.00:13.0:1
#000000
#FBF9F7
Pass
title ReadCube Literature …20.00:14.5:1
#000000
#FBF9F7
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.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback