Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

4 PASS 5 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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

1 navigation landmark(s) detected

Hamburger menu detected (responsive design)

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 1 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

Landmark Structure

5 landmarks

REVIEW

5 landmarks

<main> landmark present

1 <nav> landmark(s) found

No contentinfo (footer) landmark

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

15 headings

REVIEW

15 headings

No H1 heading found

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

H2 Cookie Preference Center
H2 Cookie Preference Center
H3 Cookie Settings
H3 Strictly Necessary Cookies
H3 Functional Cookies
H3 Performance and Analytics Cookies
H3 Social Media Cookies
H3 Advertising Cookies
H4 Cookie Settings
H4 Strictly Necessary Cookies
H4 Functional Cookies
H4 Performance and Analytics Cookies
H4 Social Media Cookies
H4 Advertising 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

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title JSTOR: Page not found ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✓

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

Color Contrast (Screenshot)

Action

20 text elements analyzed, 2 fail WCAG AA

REVIEW

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

18 pass 2 fail WCAG AA

title JSTOR Home

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

mfe-header-pharos-link Skip to main content

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Cookie Preference Ce…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Cookie Preference Ce…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Cookie Settings	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Strictly Necessary C…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Functional Cookies	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Performance and Anal…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Social Media Cookies	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Advertising Cookies	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Cookie List	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title JSTOR Home	1.00:1	4.5:1	#000000	#000000	Fail
mfe-header-pharos-link Skip to main content	1.00:1	4.5:1	#000000	#000000	Fail
mfe-header-pharos-dropdown-menu-item Get support	21.00:1	4.5:1	#000000	#FFFFFF	Pass
mfe-header-pharos-dropdown-menu-item Help logging in	21.00:1	4.5:1	#000000	#FFFFFF	Pass
mfe-header-pharos-dropdown-menu-item Contact us	21.00:1	4.5:1	#000000	#FFFFFF	Pass
mfe-access-workflow-pharos-button Log in	21.00:1	4.5:1	#000000	#FFFFFF	Pass
mfe-access-workflow-pharos-button Register	21.00:1	4.5:1	#000000	#FFFFFF	Pass
mfe-header-pharos-sidenav-link Workspace	21.00:1	4.5:1	#000000	#FFFFFF	Pass
mfe-header-pharos-sidenav-link Advanced Search	21.00:1	4.5:1	#000000	#FFFFFF	Pass
mfe-header-pharos-sidenav-link By subject	21.00:1	4.5:1	#000000	#FFFFFF	Pass
mfe-header-pharos-sidenav-link By title	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.

Alt Text Quality

All 29 images OK

PASS

All 29 images OK

3 image(s) with alt text over 125 characters

6 decorative image(s) correctly marked

20 image(s) with good alt text

29 images 20 good alt text 6 decorative

Issue	Count
too long	3 image(s)

A+

Form Accessibility

All 9 controls labeled

PASS

All 9 controls labeled

9 control(s) properly labeled

9 controls

9 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#ot-group-id-C0003	checkbox	Functional Cookies	for/id
#ot-group-id-C0002	checkbox	Performance and Analytics Cookies	for/id
#ot-group-id-C0005	checkbox	Social Media Cookies	for/id
#ot-group-id-C0004	checkbox	Advertising Cookies	for/id
#vendor-search-handler	text	Cookie list search	aria-label
#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
#chkbox-id	checkbox	checkbox label	for/id

Link & Button Quality

3 links, 14 buttons — all OK

PASS

3 links, 14 buttons — all OK

2 link(s) open in new tab without warning

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

Got: https://www.ithaka.org/cookies; https://www.onetrust.com/products/cookie-consent/

1 link(s) with descriptive text

3 links

0 empty

0 generic text

2 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.ithaka.org/cookies	More information about your pr…	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

15 links and buttons have descriptive text

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

https://www.ithaka.org/cookies; https://www.onetrust.com/products/cookie-consent/

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

A+

Lighthouse Accessibility Audits

Score 100/100 — 0 failing, 27 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

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

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

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

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

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