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 5 REVIEW 7 FIX

Landmark Structure

Action

No landmarks

FIX

No landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

No <nav> landmark found

No banner (header) landmark

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.

No landmarks detected

Screen reader users have no way to navigate by region.

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

Soft 404: server returns HTTP 200 for non-existent pages

The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.

Got: Status: 200 for /beavercheck-404-test-528gr3

404 Page Quality ✗ Soft 404 (HTTP 200)

Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

favicon.ico present at site root

HTML icon links detected

No apple-touch-icon detected

iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.

✓ favicon.ico Present

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://jewishvirtuallibrary.org/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://jewishvirtuallibrary.org/manifest.json

Manifest contains invalid JSON.

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

1 headings

REVIEW

1 headings

No H1 heading found

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

H4 EXPLORE THE LIBRARY WINGS

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

Alt Text Quality

Action

6 of 6 images have issues

REVIEW

6 of 6 images have issues

6 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

6 images 6 missing

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

Link & Button Quality

Action

11 issue(s) across 20 links and 5 buttons

REVIEW

11 issue(s) across 20 links and 5 buttons

10 link(s) with no accessible text

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

Got: /; /; /; /; /; /; /; /; /; /

1 button(s) with no accessible text

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

Got: button.btn-small (#211 on page)

10 link(s) with descriptive text

20 links

10 empty

0 generic text

0 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
/	(empty)	empty	Add link text or aria-label
/	(empty)	empty	Add link text or aria-label
/	(empty)	empty	Add link text or aria-label
/	(empty)	empty	Add link text or aria-label
/	(empty)	empty	Add link text or aria-label
/	(empty)	empty	Add link text or aria-label
/	(empty)	empty	Add link text or aria-label
/	(empty)	empty	Add link text or aria-label
/	(empty)	empty	Add link text or aria-label
/	(empty)	empty	Add link text or aria-label
<button>	(empty)	empty	Add button text or aria-label

14 links and buttons have descriptive text

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

/; /; /; /; /; /; /; /; /; /

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

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

button.btn-small (#211 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

Color Contrast (Screenshot)

Action

20 text elements analyzed, 5 fail WCAG AA

REVIEW

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

15 pass 5 fail WCAG AA

title Jewish Virtual Library

1.64:1

#000000

#3F2F1D

needs 4.5:1 (normal text)

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

span Library Wings

1.74:1

#000000

#46321F

needs 4.5:1 (normal text)

16px · top of page (header area)

span About

1.65:1

#000000

#472D15

needs 4.5:1 (normal text)

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

span Bookstore

1.16:1

#000000

#1D150C

needs 4.5:1 (normal text)

16px · top of page (header area)

span Glossary

1.53:1

#000000

#3C2A12

needs 4.5:1 (normal text)

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

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
title Jewish Virtual Libra…	1.64:1	4.5:1	#000000	#3F2F1D	Fail
span Library Wings	1.74:1	4.5:1	#000000	#46321F	Fail
span About	1.65:1	4.5:1	#000000	#472D15	Fail
span Bookstore	1.16:1	4.5:1	#000000	#1D150C	Fail
span Glossary	1.53:1	4.5:1	#000000	#3C2A12	Fail
span Links	19.22:1	4.5:1	#000000	#FFF4DB	Pass
span Publications	19.22:1	4.5:1	#000000	#FFF4DB	Pass
span Timelines	19.22:1	4.5:1	#000000	#FFF4DB	Pass
span Virtual Tours	19.22:1	4.5:1	#000000	#FFF4DB	Pass
span DONATE	19.22:1	4.5:1	#000000	#FFF4DB	Pass
span SUBSCRIBE	19.22:1	4.5:1	#000000	#FFF4DB	Pass
div JEWISH VIRTUAL LIBRA…	19.22:1	4.5:1	#000000	#FFF4DB	Pass
span Dive into a treasure…	19.22:1	4.5:1	#000000	#FFF4DB	Pass
h4 EXPLORE THE LIBRARY …	19.22:1	3.0:1	#000000	#FFF4DB	Pass
div HISTORICAL TIMELINES	19.22:1	4.5:1	#000000	#FFF4DB	Pass
div Discover key moments…	19.22:1	4.5:1	#000000	#FFF4DB	Pass
span Ancient Jewish Histo…	19.22:1	4.5:1	#000000	#FFF4DB	Pass
span EXPLORE	19.22:1	4.5:1	#000000	#FFF4DB	Pass
span Modern Jewish Histor…	19.22:1	4.5:1	#000000	#FFF4DB	Pass
span EXPLORE	19.22:1	4.5:1	#000000	#FFF4DB	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.

Lighthouse Accessibility Audits

Action

Score 75/100 — 7 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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters