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 4 REVIEW 4 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.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

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

10 headings

REVIEW

10 headings

No H1 heading found

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

H2 Featured communities
H2 Recent uploads
H2 Why use Zenodo?
H2 Newsletter
H2 About
H2 Blog
H2 Support
H2 Developers
H2 Contribute
H2 Funded by

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

84 links, 6 buttons — all OK

REVIEW

84 links, 6 buttons — all OK

15 image-only link(s) without alt text

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

Got: a[href="https://orcid.org/0000-0002-3241-1846"]; a[href="https://orcid.org/0000-0001-5787-9130"]; a[href="https://orcid.org/0000-0001-5879-2942"]; a[href="https://orcid.org/0000-0002-1048-581X"]; a[href="https://orcid.org/0000-0002-3533-9421"]; a[href="https://orcid.org/0000-0002-8397-3881"]; a[href="https://orcid.org/0000-0003-3283-829X"]; a[href="https://orcid.org/0000-0001-8978-8495"]; a[href="https://orcid.org/0009-0002-1572-6763"]; a[href="https://orcid.org/0000-0003-0619-5630"] (+5 more)

69 link(s) with descriptive text

84 links

0 empty

0 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://orcid.org/0000-0002-3241-1846	Gowers, Richard J.: ORCID prof…	img no alt	Add alt attribute to the image
https://orcid.org/0000-0001-5787-9130	Alibay, Irfan: ORCID profile	img no alt	Add alt attribute to the image
https://orcid.org/0000-0001-5879-2942	Dotson, David L.: ORCID profil…	img no alt	Add alt attribute to the image
https://orcid.org/0000-0002-1048-581X	Pai, Shraddha: ORCID profile	img no alt	Add alt attribute to the image
https://orcid.org/0000-0002-3533-9421	Ullah, Isaac: ORCID profile	img no alt	Add alt attribute to the image
https://orcid.org/0000-0002-8397-3881	Michelaki, Kostalena: ORCID pr…	img no alt	Add alt attribute to the image
https://orcid.org/0000-0003-3283-829X	Sovacool, Kelly: ORCID profile	img no alt	Add alt attribute to the image
https://orcid.org/0000-0001-8978-8495	Koparde, Vishal: ORCID profile	img no alt	Add alt attribute to the image
https://orcid.org/0009-0002-1572-6763	van der Deijl, Lucas: ORCID pr…	img no alt	Add alt attribute to the image
https://orcid.org/0000-0003-0619-5630	SAAR, Ortal-Paz: ORCID profile	img no alt	Add alt attribute to the image
https://orcid.org/0000-0003-4566-9456	Dosoo, Korshi: ORCID profile	img no alt	Add alt attribute to the image
https://orcid.org/0000-0002-7518-3441	Haasis, Lucas: ORCID profile	img no alt	Add alt attribute to the image
https://home.cern	CERN	img no alt	Add alt attribute to the image
https://www.openaire.eu	OpenAIRE	img no alt	Add alt attribute to the image
https://commission.europa.eu/index_en	European Commission	img no alt	Add alt attribute to the image

75 links and buttons have descriptive text

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

a[href="https://orcid.org/0000-0002-3241-1846"]; a[href="https://orcid.org/0000-0001-5787-9130"]; a[href="https://orcid.org/0000-0001-5879-2942"]; a[href="https://orcid.org/0000-0002-1048-581X"]; a[href="https://orcid.org/0000-0002-3533-9421"]; a[href="https://orcid.org/0000-0002-8397-3881"]; a[href="https://orcid.org/0000-0003-3283-829X"]; a[href="https://orcid.org/0000-0001-8978-8495"]; a[href="https://orcid.org/0009-0002-1572-6763"]; a[href="https://orcid.org/0000-0003-0619-5630"] (+5 more)

Why this matters

Image-only links with no alt are unidentifiable to screen-reader users — link's destination is invisible.

Source: WCAG 2.1 SC 2.4.4

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 ✓Page Title Page not found ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Favicon & Branding

6 icon(s) detected

REVIEW

6 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

Landmark Structure

6 landmarks

PASS

6 landmarks

<main> landmark present

2 <nav> landmark(s) found

1 of 2 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

Skip navigation link present

Page Structure — as a screen reader sees it

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

A+

Alt Text Quality

All 17 images OK

PASS

All 17 images OK

16 decorative image(s) correctly marked

1 image(s) with good alt text

17 images 1 good alt text 16 decorative

All images have appropriate alt text.

Form Accessibility

1 of 4 controls have issues

PASS

1 of 4 controls have issues

1 control(s) without accessible label

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

Got: <input type="submit">

3 control(s) properly labeled

4 controls

3 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
input	text	Search records...	aria-label
#newsletter-email	email	E-mail *	for/id
#newsletter-name	text	Name	for/id
input	submit	(none)	none

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

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

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 Featured communities	18.29:1	3.0:1	#000000	#EAF0F6	Pass
h2 Recent uploads	18.29:1	3.0:1	#000000	#EAF0F6	Pass
h2 Why use Zenodo?	18.29:1	3.0:1	#000000	#EAF0F6	Pass
h2 Newsletter	18.29:1	3.0:1	#000000	#EAF0F6	Pass
h2 About	18.29:1	3.0:1	#000000	#EAF0F6	Pass
h2 Blog	18.29:1	3.0:1	#000000	#EAF0F6	Pass
h2 Support	18.29:1	3.0:1	#000000	#EAF0F6	Pass
h2 Developers	18.29:1	3.0:1	#000000	#EAF0F6	Pass
h2 Contribute	18.29:1	3.0:1	#000000	#EAF0F6	Pass
h2 Funded by	18.29:1	3.0:1	#000000	#EAF0F6	Pass
title Zenodo	9.64:1	4.5:1	#000000	#2ABBFE	Pass
a Skip to main	9.64:1	4.5:1	#000000	#2ABBFE	Pass
div ...	12.22:1	4.5:1	#000000	#82D0EF	Pass
div All Zenodo	13.26:1	4.5:1	#000000	#A9D5DE	Pass
a Communities	13.26:1	4.5:1	#000000	#A9D5DE	Pass
a My dashboard	17.33:1	4.5:1	#000000	#E4EAF0	Pass
a Log in	18.29:1	4.5:1	#000000	#EAF0F6	Pass
a Sign up	18.29:1	4.5:1	#000000	#EAF0F6	Pass
strong Planned intervention	18.29:1	3.0:1	#000000	#EAF0F6	Pass
p : On Thursday April …	18.29:1	4.5:1	#000000	#EAF0F6	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, 29 passed

PASS

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
Unni, Deepak R. `div.content > div.ui > span.creatibutor-wrap > a.creatibutor-link`
Moxon, Sierra A. T. `div.content > div.ui > span.creatibutor-wrap > a.creatibutor-link`
Bada, Michael `div.content > div.ui > span.creatibutor-wrap > a.creatibutor-link`
Wang, Bin `div.content > div.ui > span.creatibutor-wrap > a.creatibutor-link`
Wan, Yuhan `div.content > div.ui > span.creatibutor-wrap > a.creatibutor-link`
Fang, Xuefeng `div.content > div.ui > span.creatibutor-wrap > a.creatibutor-link`
Paxton, Bill `div.content > div.ui > span.creatibutor-wrap > a.creatibutor-link`
Gowers, Richard J.: ORCID profile `div.content > div.ui > span.creatibutor-wrap > a.no-text-decoration`
Alibay, Irfan: ORCID profile `div.content > div.ui > span.creatibutor-wrap > a.no-text-decoration`
Dotson, David L.: ORCID profile `div.content > div.ui > span.creatibutor-wrap > a.no-text-decoration`
Pai, Shraddha `div.content > div.ui > span.creatibutor-wrap > a.creatibutor-link`
Pai, Shraddha: ORCID profile `div.content > div.ui > span.creatibutor-wrap > a.no-text-decoration`
Ullah, Isaac `div.content > div.ui > span.creatibutor-wrap > a.creatibutor-link`
Ullah, Isaac: ORCID profile `div.content > div.ui > span.creatibutor-wrap > a.no-text-decoration`
Michelaki, Kostalena `div.content > div.ui > span.creatibutor-wrap > a.creatibutor-link`
Michelaki, Kostalena: ORCID profile `div.content > div.ui > span.creatibutor-wrap > a.no-text-decoration`
Sovacool, Kelly `div.content > div.ui > span.creatibutor-wrap > a.creatibutor-link`
Sovacool, Kelly: ORCID profile `div.content > div.ui > span.creatibutor-wrap > a.no-text-decoration`
Koparde, Vishal `div.content > div.ui > span.creatibutor-wrap > a.creatibutor-link`
Koparde, Vishal: ORCID profile `div.content > div.ui > span.creatibutor-wrap > a.no-text-decoration`
van der Deijl, Lucas `div.content > div.ui > span.creatibutor-wrap > a.creatibutor-link`
van der Deijl, Lucas: ORCID profile `div.content > div.ui > span.creatibutor-wrap > a.no-text-decoration`
SAAR, Ortal-Paz `div.content > div.ui > span.creatibutor-wrap > a.creatibutor-link`
SAAR, Ortal-Paz: ORCID profile `div.content > div.ui > span.creatibutor-wrap > a.no-text-decoration`
Dosoo, Korshi `div.content > div.ui > span.creatibutor-wrap > a.creatibutor-link`
Dosoo, Korshi: ORCID profile `div.content > div.ui > span.creatibutor-wrap > a.no-text-decoration`
Haasis, Lucas `div.content > div.ui > span.creatibutor-wrap > a.creatibutor-link`
Haasis, Lucas: ORCID profile `div.content > div.ui > span.creatibutor-wrap > a.no-text-decoration`
About `div.column > ul.ui > li.item > a`
Policies `div.column > ul.ui > li.item > a`
Principles `div.column > ul.ui > li.item > a`
Projects `div.column > ul.ui > li.item > a`
Roadmap `div.column > ul.ui > li.item > a`
Contact `div.column > ul.ui > li.item > a`
Help `div.column > ul.ui > li.item > a`
FAQ `div.column > ul.ui > li.item > a`
REST API `div.column > ul.ui > li.item > a`
OAI-PMH `div.column > ul.ui > li.item > a`
GitHub `div.column > ul.ui > li.item > a`
Donate `div.column > ul.ui > li.item > 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

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

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

●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

○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 type="image">` elements have `[alt]` text

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