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

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

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

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)

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

Form Accessibility

2 of 5 controls have issues

REVIEW

2 of 5 controls have issues

2 control(s) without accessible label

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

Got: <input type="radio" name="toggle" id="search-toggle">; <input type="image" name="submit">

3 control(s) properly labeled

5 controls

3 labeled

0 placeholder only

2 unlabeled

Control	Type	Label	Method
#search-close	radio	X	for/id
#about-toggle	checkbox	About▼	for/id
query	text	Search books	aria-label
#search-toggle	radio	(none)	none
submit	image	(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

86 links, 1 buttons — all OK

REVIEW

86 links, 1 buttons — all OK

20 image-only link(s) without alt text

66 link(s) with descriptive text

86 links

0 empty

0 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/ebooks/78386	The Platypus by Harry Burrell	img no alt	Add alt attribute to the image
/ebooks/78385	Salon soittaja by Larin-Kyöst…	img no alt	Add alt attribute to the image
/ebooks/78384	A geographical and commercial …	img no alt	Add alt attribute to the image
/ebooks/78383	Empfindungen aus meinem Leben …	img no alt	Add alt attribute to the image
/ebooks/78382	A doorway in Fairyland by Laur…	img no alt	Add alt attribute to the image
/ebooks/78381	An odd couple by Mrs. Oliphant	img no alt	Add alt attribute to the image
/ebooks/78380	Anarchism is not enough by Lau…	img no alt	Add alt attribute to the image
/ebooks/78379	Réflexions sur Stendhal by Re…	img no alt	Add alt attribute to the image
/ebooks/78378	Lord Lister 0045: Het gestolen…	img no alt	Add alt attribute to the image
/ebooks/78377	My past and thoughts, vol. 6 (…	img no alt	Add alt attribute to the image
/ebooks/84	Frankenstein; or, the modern p…	img no alt	Add alt attribute to the image
/ebooks/45304	The City of God, Volume I by S…	img no alt	Add alt attribute to the image
/ebooks/2701	Moby Dick; Or, The Whale by He…	img no alt	Add alt attribute to the image
/ebooks/1342	Pride and Prejudice by Jane Au…	img no alt	Add alt attribute to the image
/ebooks/1513	Romeo and Juliet by William Sh…	img no alt	Add alt attribute to the image
/ebooks/768	Wuthering Heights by Emily Bro…	img no alt	Add alt attribute to the image
/ebooks/11	Alice's Adventures in Wonderla…	img no alt	Add alt attribute to the image
/ebooks/64317	The Great Gatsby by F. Scott F…	img no alt	Add alt attribute to the image
/ebooks/100	The Complete Works of William …	img no alt	Add alt attribute to the image
/ebooks/37683	Chambers's Twentieth Century D…	img no alt	Add alt attribute to the image

67 links and buttons have descriptive text

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 404 | Project Gutenberg ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Landmark Structure

4 landmarks

PASS

4 landmarks

<main> landmark present

1 <nav> landmark(s) 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

9 headings, 1 skip(s)

PASS

9 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 Project Gutenberg is a library of over 75,000 free eBooks
H3 Find Free eBooks skipped
H3 Project Gutenberg
H3 Get Help
H3 How to Help
H3 Special Areas
H3 Audio Books
H3 Our Social Media
H3 News Feeds of new eBooks

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

A+

Alt Text Quality

All 28 images OK

PASS

All 28 images OK

20 decorative image(s) correctly marked

8 image(s) with good alt text

28 images 8 good alt text 20 decorative

All images have appropriate alt text.

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
h1 Project Gutenberg is…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Find Free eBooks	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Project Gutenberg	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Get Help	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 How to Help	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Special Areas	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Audio Books	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Our Social Media	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 News Feeds of new eB…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Free eBooks \| Projec…	10.16:1	4.5:1	#000000	#7EBED0	Pass
button Go!	10.16:1	4.5:1	#000000	#7EBED0	Pass
a Donate	14.88:1	4.5:1	#000000	#C7DDE3	Pass
label About	14.88:1	4.5:1	#000000	#C7DDE3	Pass
span ▼	17.43:1	4.5:1	#000000	#E0ECF0	Pass
a About Project Gutenb…	17.43:1	4.5:1	#000000	#E0ECF0	Pass
a Reading Options & Ki…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Contact Us	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a History & Philosophy	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Help Pages	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Offline Catalogs	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.

A+

Lighthouse Accessibility Audits

Score 98/100 — 1 failing, 24 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
Find Free eBooks `div.homepage > div.info-box-container > div.info-box > 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

●Image elements have `[alt]` attributes

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

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

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[accesskey]` values are unique

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

○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

○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 buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

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

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