Skip to content
https://openlibrary.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
67
GRADE
D
FIX
4
REVIEW
4
PASS
5
INFO
0
Checks
13
5 PASS 4 REVIEW 4 FIX
D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #e2dcc5
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark ModePartial Dark Mode
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
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 ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
5 landmarks
REVIEW
5 landmarks
Info::
<main> landmark present
Warning::
No <nav> landmark found
Warning::
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
BANNER header MAIN ASIDE CONTENTINFO footer

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

B
Heading Hierarchy
13 headings
REVIEW
13 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H2 Preview Book
  • H2 Welcome to Open Library
  • H2 Books We Love
  • H2 Recently Returned
  • H2 Browse by Subject
  • H2 Around the Library
  • H2 About the Project
  • H3 Latest Blog Posts
  • H2 Open Library
  • H2 Discover
  • H2 Develop
  • H2 Help
  • H2 Change Website Language

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

B
Favicon & Branding
11 icon(s) detected
REVIEW
11 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 1 fail WCAG AA
REVIEW

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

19 pass 1 fail WCAG AA
title Welcome to Open Library | Open Library
1.66:1
#000000
on
#333333
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Preview Book10.92:13.0:1
#000000
#BBBCAE
Pass
h2 Welcome to Open Libr…10.92:13.0:1
#000000
#BBBCAE
Pass
h2 Around the Library10.92:13.0:1
#000000
#BBBCAE
Pass
h2 About the Project10.92:13.0:1
#000000
#BBBCAE
Pass
h2 Open Library10.92:13.0:1
#000000
#BBBCAE
Pass
h2 Discover10.92:13.0:1
#000000
#BBBCAE
Pass
h2 Develop10.92:13.0:1
#000000
#BBBCAE
Pass
h2 Help10.92:13.0:1
#000000
#BBBCAE
Pass
h2 Change Website Langu…10.92:13.0:1
#000000
#BBBCAE
Pass
title Welcome to Open Libr…1.66:14.5:1
#000000
#333333
Fail
div It looks like you're…17.00:14.5:1
#000000
#EDE7D6
Pass
a Donate17.68:14.5:1
#000000
#F2EBDB
Pass
span ♥15.28:14.5:1
#000000
#E2DCC5
Pass
span English (en)10.92:14.5:1
#000000
#BBBCAE
Pass
a العربية (ar)10.92:14.5:1
#000000
#BBBCAE
Pass
a Čeština (cs)10.92:14.5:1
#000000
#BBBCAE
Pass
a Deutsch (de)10.92:14.5:1
#000000
#BBBCAE
Pass
a English (en)10.92:14.5:1
#000000
#BBBCAE
Pass
a Español (es)10.92:14.5:1
#000000
#BBBCAE
Pass
a Français (fr)10.92:14.5:1
#000000
#BBBCAE
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+
Alt Text Quality
All 72 images OK
PASS
All 72 images OK
Info::
29 decorative image(s) correctly marked
Info::
43 image(s) with good alt text
72 images 43 good alt text 29 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 3 controls labeled
PASS
All 3 controls labeled
Info::
3 control(s) properly labeled
3 controls
3 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
selectselectAllnone
qtextSearcharia-label
inputsubmitSearch submitaria-label
A
404 Error Page
HTTP 404, custom page
PASS
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title /beavercheck-404-test-w85b9u is not found | Open Library ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
A+
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: Open Library: A page for every book published
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria ✓ Installable
Name Open Library: A page for every book published ✓192×192 icon ✓512×512 icon ✓Start URL /?source=pwa ✓Display Mode standalone ✓
Name Open Library: A page for every book published Display Mode standalone Theme Color #e2dcc5 Background Color #e2dcc5 Icons 4 icon(s)
A
Lighthouse Accessibility Audits
Score 94/100 — 2 failing, 32 passed
PASS
94

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

When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Read Free Library Books Online Millions of books available through Controlled … div.carousel-container > div.carousel > div.slick-list > div.slick-track
Borrow Checked Out Borrow Read Preview Only Borrow Read Preview Only Locate Rea… div.carousel-container > div.carousel > div.slick-list > div.slick-track
Read Checked Out Read Read Read Read Audiobook Borrow Read Checked Out Borrow B… div.carousel-container > div.carousel > div.slick-list > div.slick-track
Borrow Borrow Borrow Borrow Borrow Borrow Borrow Borrow Borrow Borrow Borrow Bo… div.carousel-container > div.carousel > div.slick-list > div.slick-track
Borrow Borrow Borrow Borrow Borrow Borrow Borrow Borrow Borrow Borrow Borrow Lo… div.carousel-container > div.carousel > div.slick-list > div.slick-track
Art 129,779 Books Science Fiction 20,982 Books Fantasy 14,387 Books Biogr… div.carousel-container > div.carousel > div.slick-list > div.slick-track

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.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Home div > ul > li > a
Books div > ul > li > a
Authors div > ul > li > a
Subjects div > ul > li > a
Collections div > ul > li > a
Developer Center div > ul > li > a
API Documentation div > ul > li > a
Bulk Data Dumps div > ul > li > a
Help Center div > ul > li > a
Contact Us div > ul > li > a
العربية (ar) div > ul.locale-options > li > a
Čeština (cs) div > ul.locale-options > li > a
Deutsch (de) div > ul.locale-options > li > a
English (en) div > ul.locale-options > li > a
Español (es) div > ul.locale-options > li > a
Français (fr) div > ul.locale-options > li > a
हिंदी (hi) div > ul.locale-options > li > a
Hrvatski (hr) div > ul.locale-options > li > a
Italiano (it) div > ul.locale-options > li > a
Português (pt) div > ul.locale-options > li > a
Română (ro) div > ul.locale-options > li > a
Sardu (sc) div > ul.locale-options > li > a
తెలుగు (te) div > ul.locale-options > li > a
Українська (uk) div > ul.locale-options > li > a

These items highlight common accessibility best practices.

○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
●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
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●Input buttons have discernible text.
●`[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
●ARIA toggle fields have accessible names
●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 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
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with the `role=text` attribute do not have focusable descendents.
○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 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.
○`<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.
○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.

Send Feedback