Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 5 REVIEW 3 FIX

Web Manifest

Action

Not found

FIX

Not found

No web manifest found

No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Heading Hierarchy

11 headings

REVIEW

11 headings

No H1 heading found

Every page should have one H1 that describes the page content.

H3 From first addition to final submission
H2 Get Mendeley
H2 Support
H2 About Us
H2 Cookie Preference Center
H3 Manage Consent Preferences
H4 Strictly Necessary Cookies
H4 Functional Cookies
H4 Performance Cookies
H4 Targeting Cookies
H3 Cookie List

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

Link & Button Quality

Action

4 issue(s) across 39 links and 21 buttons

REVIEW

4 issue(s) across 39 links and 21 buttons

19 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: /library; https://blog.mendeley.com/2026/04/03/4-study-tips-to-help-you-prepare-for-exa…; https://blog.mendeley.com/2026/01/12/boost-your-research-efficiency-with-mend…; https://blog.mendeley.com/2025/12/08/the-future-in-mendeley-ai-features-are-h…; https://appsource.microsoft.com/en-us/product/office/wa104382081?tab=overview; https://chrome.google.com/webstore/detail/mendeley-importer/dagcmkpagjlhakfdh…; https://data.mendeley.com/; https://service.elsevier.com/app/home/supporthub/mendeley/; http://dev.mendeley.com/; https://www.howcanishareit.com/ (+9 more)

4 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button (#322 on page); button (#336 on page); button (#352 on page); button (#368 on page)

20 link(s) with descriptive text

39 links

0 empty

0 generic text

19 new tab

4 empty buttons

Element	Text	Issue	Suggested Fix
/library	Get started on Mendeley WebOpe…	new tab	Add '(opens in new tab)' to text
https://blog.mendeley.com/2026/04/03/4-s…	Read moreOpens in a new window	new tab	Add '(opens in new tab)' to text
https://blog.mendeley.com/2026/01/12/boo…	Read moreOpens in a new window	new tab	Add '(opens in new tab)' to text
https://blog.mendeley.com/2025/12/08/the…	Read moreOpens in a new window	new tab	Add '(opens in new tab)' to text
https://appsource.microsoft.com/en-us/pr…	Mendeley for Microsoft W…	new tab	Add '(opens in new tab)' to text
https://chrome.google.com/webstore/detai…	Mendeley for your browser	new tab	Add '(opens in new tab)' to text
https://data.mendeley.com/	Datasets	new tab	Add '(opens in new tab)' to text
https://service.elsevier.com/app/home/su…	Support Center	new tab	Add '(opens in new tab)' to text
http://dev.mendeley.com/	Developers	new tab	Add '(opens in new tab)' to text
https://www.howcanishareit.com/	Responsibility Sharing	new tab	Add '(opens in new tab)' to text
https://blog.mendeley.com/	Blog	new tab	Add '(opens in new tab)' to text
https://www.elsevier.com/en-gb/about/pol…	AI Statement	new tab	Add '(opens in new tab)' to text
https://www.elsevier.com/	Elsevier	new tab	Add '(opens in new tab)' to text
/privacy/	Privacy Policy	new tab	Add '(opens in new tab)' to text
https://www.relx.com/	RELX Group™	new tab	Add '(opens in new tab)' to text
https://www.elsevier.com/legal/cookienot…	Cookie Policy, opens in a new …	new tab	Add '(opens in new tab)' to text
https://www.elsevier.com/legal/cookienot…	Cookie Policy	new tab	Add '(opens in new tab)' to text
https://support.google.com/admanager/ans…	Google Ad-Tech Vendors	new tab	Add '(opens in new tab)' to text
https://www.onetrust.com/products/cookie…	Powered by OneTrust Opens in a…	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

37 links and buttons have descriptive text

Add '(opens in new tab)' to link text or aria-label.

/library; https://blog.mendeley.com/2026/04/03/4-study-tips-to-help-you-prepare-for-exa…; https://blog.mendeley.com/2026/01/12/boost-your-research-efficiency-with-mend…; https://blog.mendeley.com/2025/12/08/the-future-in-mendeley-ai-features-are-h…; https://appsource.microsoft.com/en-us/product/office/wa104382081?tab=overview; https://chrome.google.com/webstore/detail/mendeley-importer/dagcmkpagjlhakfdh…; https://data.mendeley.com/; https://service.elsevier.com/app/home/supporthub/mendeley/; http://dev.mendeley.com/; https://www.howcanishareit.com/ (+9 more)

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

Icon-only buttons need an aria-label so screen readers can announce them.

button (#322 on page); button (#336 on page); button (#352 on page); button (#368 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Favicon & Branding

17 icon(s) detected

REVIEW

17 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

Dark-specific theme-color detected

A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.

prefers-color-scheme CSS detected in inline styles

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark Mode✓ Dark Mode Supported

color-scheme meta Not set ✗Dark theme-color #ffffff ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

A+

Landmark Structure

6 landmarks

PASS

6 landmarks

<main> landmark present

1 <nav> landmark(s) found

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Alt Text Quality

All 21 images OK

PASS

All 21 images OK

1 decorative image(s) correctly marked

20 image(s) with good alt text

21 images 20 good alt text 1 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 8 controls labeled

PASS

All 8 controls labeled

8 control(s) properly labeled

8 controls

8 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#ot-group-id-3	checkbox	Functional Cookies	for/id
#ot-group-id-2	checkbox	Performance Cookies	for/id
#ot-group-id-4	checkbox	Targeting Cookies	for/id
#vendor-search-handler	text	Cookie list search	aria-label
#chkbox-id	checkbox	checkbox label	for/id
#select-all-hosts-groups-handler	checkbox	checkbox label	for/id
#select-all-vendor-groups-handler	checkbox	checkbox label	for/id
#select-all-vendor-leg-handler	checkbox	checkbox label	for/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)

Element	Ratio	Required	FG	BG	Result
h2 Get Mendeley	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h2 Support	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h2 About Us	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h2 Cookie Preference Ce…	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h3 From first addition …	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h3 Manage Consent Prefe…	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h3 Cookie List	5.24:1	3.0:1	#000000	#7F7F7F	Pass
a Skip to main content	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Pricing	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Features	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Search	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Sign In	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Get Mendeley for fre…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Get Mendeley for fre…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
title Mendeley \| Homepage	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span The	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span free	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span all-in-one reference…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Mendeley helps you s…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Download for Linux	13.08:1	4.5:1	#000000	#CCCCCC	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 100/100 — 0 failing, 28 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.

○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.

●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

●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 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.

○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.