Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

1 PASS 6 REVIEW 6 FIX

Alt Text Quality

Action

2 of 2 images have issues

FIX

2 of 2 images have issues

2 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

2 image-in-link without alt text

An image inside a link with no alt creates an empty link.

2 images 2 missing

Issue	Count
missing	2 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

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

404 Error Page

Action

HTTP 400, custom page

FIX

HTTP 400, custom page

Unexpected status code: HTTP 400

Expected HTTP 404 but received 400. This may confuse search engine crawlers.

Got: HTTP 400

Custom styled 404 page

Navigation links present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 400 ✗Page Title Error: Not a DOI ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗

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 ✗

Landmark Structure

4 landmarks

REVIEW

4 landmarks

<main> landmark present

No <nav> landmark found

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

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

Heading Hierarchy

2 headings

REVIEW

2 headings

No H1 heading found

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

H2 Resolve a DOI Name
H2 More information on DOI resolution:

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

Form Accessibility

2 of 2 controls have issues

REVIEW

2 of 2 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">

1 control(s) rely on placeholder only

Placeholder text disappears on focus and is not a reliable label.

Got: <input type="text" name="hdl" id="nameID">

2 controls

0 labeled

1 placeholder only

1 unlabeled

Control	Type	Label	Method
#nameID	text	(10.nnnnnn/example)	placeholder only
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

Placeholder text disappears on focus and is not a reliable label.

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

Link & Button Quality

Action

6 issue(s) across 13 links and 1 buttons

REVIEW

6 issue(s) across 13 links and 1 buttons

5 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: https://www.doi.org; https://www.doi.org; https://twitter.com/DOI_Foundation; https://www.linkedin.com/company/doi-foundation-inc/; mailto:info@doi.org

1 link(s) open in new tab without warning

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

Got: https://creativecommons.org/licenses/by/4.0/

1 button(s) with no accessible text

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

Got: input[type="submit"].submit (#44 on page)

7 link(s) with descriptive text

13 links

5 empty

0 generic text

1 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
https://www.doi.org	(empty)	empty	Add link text or aria-label
https://www.doi.org	(empty)	empty	Add link text or aria-label
https://creativecommons.org/licenses/by/…	Creative Commons Attribution 4…	new tab	Add '(opens in new tab)' to text
https://twitter.com/DOI_Foundation	(empty)	empty	Add link text or aria-label
https://www.linkedin.com/company/doi-fou…	(empty)	empty	Add link text or aria-label
mailto:info@doi.org	(empty)	empty	Add link text or aria-label
<input>	(empty)	empty	Add button text or aria-label

7 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

https://www.doi.org; https://www.doi.org; https://twitter.com/DOI_Foundation; https://www.linkedin.com/company/doi-foundation-inc/; mailto:info@doi.org

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

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

https://creativecommons.org/licenses/by/4.0/

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.

input[type="submit"].submit (#44 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

Favicon & Branding

7 icon(s) detected

REVIEW

7 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

Lighthouse Accessibility Audits

Action

Score 79/100 — 4 failing, 17 passed

REVIEW

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

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more about valid ARIA attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
RESOLVE A DOI NAME Type or paste a known DOI name exactly—including its prefix … `body.generic-page > main`

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
10. `section.home-resolve > div.subtext > p > code`
doi.org/ `section.home-resolve > div.subtext > p > code`
Creative Commons Attribution 4.0 International License `div.row > div.col > p > a`

These are opportunities to improve the legibility of your content.

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
div.row > div.col > a > img.header-logo `div.row > div.col > a > img.header-logo`
div.row > div.col > a > img.footer-logo `div.row > div.col > a > img.footer-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
header > div.row > div.col > a `header > div.row > div.col > a`
footer > div.row > div.col > a `footer > div.row > div.col > a`
div.col > ul.socials-footer > li > a `div.col > ul.socials-footer > li > a`
div.col > ul.socials-footer > li > a `div.col > ul.socials-footer > li > a`
div.col > ul.socials-footer > li > a `div.col > ul.socials-footer > li > 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.

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

●`[aria-*]` attributes have valid values

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

●ARIA attributes are used as specified for the element's role

●Elements use only permitted ARIA attributes

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

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Deprecated ARIA roles were not used

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○`[aria-hidden="true"]` elements do not contain focusable descendents

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○`[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]`s are contained by their required parent element

○`[role]` values are valid

○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

○Buttons have an accessible name

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

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

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Identical links have the same purpose.

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

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 Resolve a DOI Name	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 More information on …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Resolve a DOI Name	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span VISIT DOI.ORG	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Type or paste a know…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p DOIs include a prefi…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
code 10.	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p ) and a suffix, sepa…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p ). Prefacing the DOI…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
code doi.org/	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p will turn it into an…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a https://doi.org/10.3…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p . …	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p Send questions or co…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a info@doi.org	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Further documentatio…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a DOI Resolution Facts…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a The DOI Handbook	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Privacy Policy	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p Copyright © 2026 DO…	21.00:1	4.5:1	#000000	#FFFFFF	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.