Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

6 PASS 3 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 ✗

Alt Text Quality

2 of 5 images have issues

REVIEW

2 of 5 images have issues

2 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

3 image(s) with good alt text

5 images 3 good alt text 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

Favicon & Branding

Action

4 icon(s) detected

REVIEW

4 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

Apple touch icon present

SVG favicon detected — scales perfectly to any size

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✓ SVG Favicon Present

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 8 fail WCAG AA

REVIEW

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

12 pass 8 fail WCAG AA

a Our mission and vision

2.48:1

#000000

#4D4D4D

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

a Research integrity and publication ethic…

1.21:1

#000000

#1A1A1A

needs 4.5:1 (normal text)

16px · above the fold

a Sustainability

1.21:1

#000000

#1A1A1A

needs 4.5:1 (normal text)

16px · above the fold

a The Executive Team

1.33:1

#000000

#21222E

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

a The Board of Directors

1.60:1

#000000

#4A2627

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

a The Scientific Advisory Council

1.21:1

#000000

#1A1A1A

needs 4.5:1 (normal text)

16px · above the fold

a Governance

1.21:1

#000000

#1A1A1A

needs 4.5:1 (normal text)

16px · above the fold

a Careers at PLOS

1.21:1

#000000

#1A1A1A

needs 4.5:1 (normal text)

16px · above the fold

3 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 We believe in a bett…	7.37:1	3.0:1	#000000	#999999	Pass
h2 A catalyst for bette…	7.37:1	3.0:1	#000000	#999999	Pass
h2 Open science	7.37:1	3.0:1	#000000	#999999	Pass
h3 PLOS is a non-profit…	7.37:1	3.0:1	#000000	#999999	Pass
h3 Open science publish…	7.37:1	3.0:1	#000000	#999999	Pass
h3 Open science policy	7.37:1	3.0:1	#000000	#999999	Pass
h3 Open science practic…	7.37:1	3.0:1	#000000	#999999	Pass
h3 Cookie Preference Ce…	7.37:1	3.0:1	#000000	#999999	Pass
h3 Customize Your Cooki…	7.37:1	3.0:1	#000000	#999999	Pass
title Leading the future o…	7.37:1	4.5:1	#000000	#999999	Pass
a Skip to content	7.37:1	4.5:1	#000000	#999999	Pass
a About	7.37:1	4.5:1	#000000	#999999	Pass
a Our mission and visi…	2.48:1	4.5:1	#000000	#4D4D4D	Fail
a Research integrity a…	1.21:1	4.5:1	#000000	#1A1A1A	Fail
a Sustainability	1.21:1	4.5:1	#000000	#1A1A1A	Fail
a The Executive Team	1.33:1	4.5:1	#000000	#21222E	Fail
a The Board of Directo…	1.60:1	4.5:1	#000000	#4A2627	Fail
a The Scientific Advis…	1.21:1	4.5:1	#000000	#1A1A1A	Fail
a Governance	1.21:1	4.5:1	#000000	#1A1A1A	Fail
a Careers at PLOS	1.21:1	4.5:1	#000000	#1A1A1A	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+

Landmark Structure

4 landmarks

PASS

4 landmarks

<main> landmark present

1 <nav> landmark(s) found

Skip navigation link present

Page Structure — as a screen reader sees it

Heading Hierarchy

12 headings, 1 skip(s)

PASS

12 headings, 1 skip(s)

Single H1 present

Heading level skipped: H1 → H3 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H1 We believe in a better future where science is open to all, for all
H3 PLOS is a non-profit organization on a mission to drive open science forward with measurable, meaningful change in research publishing, policy and practice. skipped
H2 A catalyst for better
H2 Open science
H3 Open science publishing
H4 Pave the way
H3 Open science policy
H4 Advocate for change
H3 Open science practice
H4 Share and inspire
H3 Cookie Preference Center
H3 Customize Your Cookie Preference

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

Form Accessibility

1 of 5 controls have issues

PASS

1 of 5 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">

4 control(s) properly labeled

5 controls

4 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#s	search	Search:	for/id
#switch0	checkbox	OnOff	for/id
#switch1	checkbox	OnOff	for/id
#switch2	checkbox	OnOff	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

Link & Button Quality

1 issue(s) across 98 links and 3 buttons

PASS

1 issue(s) across 98 links and 3 buttons

1 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: https://plos.org/open-science/ ("Read more")

1 link(s) open in new tab without warning

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

Got: https://plos.org/cookies-policy

96 link(s) with descriptive text

98 links

0 empty

1 generic text

1 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://plos.org/open-science/	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: Open Science
https://plos.org/cookies-policy	For more information about the…	new tab	Add '(opens in new tab)' to text

99 links and buttons have descriptive text

Generic link text like 'click here' doesn't describe the destination.

https://plos.org/open-science/ ("Read more")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

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

https://plos.org/cookies-policy

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

404 Error Page

HTTP 404, custom page

PASS

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

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Linkedin ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

A+

Lighthouse Accessibility Audits

Score 99/100 — 1 failing, 27 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.

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
PLOS is a non-profit organization on a mission to drive open science forward wi… `div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > h3`

These are opportunities to improve keyboard navigation in your application.

○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

●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

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<frame>` or `<iframe>` elements have a title

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

●Touch targets have sufficient size and spacing.

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○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

○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

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

○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

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

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