Skip to content
https://harpercollins.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
60
GRADE
D
FIX
5
REVIEW
2
PASS
6
INFO
0
Checks
13
6 PASS 2 REVIEW 5 FIX
F
Favicon & Branding
Action
No icons detected
FIX
No icons detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
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'>.
Critical::
No favicon or icon links detected
Your site will show the browser's generic page icon in tabs, bookmarks, and home screens.
✗ favicon.ico Missing
✗ PNG Icons Missing
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
D
Web Manifest
Action
Not found
FIX
Not found
Info::
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.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
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 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.

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.
C
Landmark Structure
Action
1 landmarks
REVIEW
1 landmarks
Info::
<main> landmark present
Warning::
No <nav> landmark found
Info::
No banner (header) landmark
Info::
No contentinfo (footer) landmark
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 (missing!) MAIN CONTENTINFO (missing!)

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

C
Lighthouse Accessibility Audits
Action
Score 74/100 — 9 failing, 22 passed
REVIEW
74

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

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
Looking for Your Next Favorite Read? Get new releases, author news, recommendat… body.sailthru-overlay-no-scroll > section#sailthru-overlay-container

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.

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

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.cart__contents > div.cart__header > div.cart__header_close > button.cart__close div.cart__contents > div.cart__header > div.cart__header_close > button.cart__close
body.sailthru-overlay-no-scroll > section#sailthru-overlay-container > div.sailthru-overlay > button.sailthru-overlay-close body.sailthru-overlay-no-scroll > section#sailthru-overlay-container > div.sailthru-overlay > button.sailthru-overlay-close

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
nav#mobileNavWhole > div.leftHeader > a.navbar-brand > img nav#mobileNavWhole > div.leftHeader > a.navbar-brand > img
div.mobileIconContain > div.iconContainer > a#mobile-account-link > img div.mobileIconContain > div.iconContainer > a#mobile-account-link > img
div > div > div.sailthru_0_0_0 > img div > div > div.sailthru_0_0_0 > img

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.container > div.row > div.col-md-10 > iframe#hc-signup div.container > div.row > div.col-md-10 > iframe#hc-signup

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.row > nav#mobileNavWhole > div.leftHeader > a.navbar-brand div.row > nav#mobileNavWhole > div.leftHeader > a.navbar-brand

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Stay up to date with new releases, author news, and reading picks—plus get 15% … body.sailthru-overlay-no-scroll > aside#shopify-section-header-promo-bar > a#header-promo-header-promo-bar > div.container
BESTSELLERS div#shopify-section-16474506515f631378 > ul#tabsMobile > li.nav-item > a.nav-link
COMING SOON div#shopify-section-16474506515f631378 > ul#tabsMobile > li.nav-item > a.nav-link
privacy notice div.col-md-10 > div.section-fine-print > p > a
privacypolicy@harpercollins.com div.col-md-10 > div.section-fine-print > p > a
Privacy Policy div.col-md-10 > div.section-fine-print > p > a
Terms of Service div.col-md-10 > div.section-fine-print > p > a
Looking for Your Next Favorite Read? div > div > div.sailthru_0_0_1 > h2.top
15% off div > div.sailthru_0_0_1 > div > strong
div.sailthru-overlay > div > div > input#sailthru-user-acquisition-email div.sailthru-overlay > div > div > input#sailthru-user-acquisition-email
privacypolicy@harpercollins.com div > div.sailthru_0_0_4 > div.legal > a

These are opportunities to improve the legibility of your content.

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
New in Memoir & Biography div.row > div.col-md-4 > a.spotlight-block > h5
BROWSE AND SHOP section.rollCall > div.roll-call-header > div.roll-call-title > h5

These are opportunities to improve keyboard navigation in your application.

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
Go to slide 1 div.browseAndShopSlider > div.row > div.swiper-pagination368c5917-cd88-40d0-8081-aa1be8e207a2 > span.swiper-pagination-bullet
Go to slide 2 div.browseAndShopSlider > div.row > div.swiper-pagination368c5917-cd88-40d0-8081-aa1be8e207a2 > span.swiper-pagination-bullet
Go to slide 3 div.browseAndShopSlider > div.row > div.swiper-pagination368c5917-cd88-40d0-8081-aa1be8e207a2 > span.swiper-pagination-bullet
Go to slide 4 div.browseAndShopSlider > div.row > div.swiper-pagination368c5917-cd88-40d0-8081-aa1be8e207a2 > span.swiper-pagination-bullet
Go to slide 5 div.browseAndShopSlider > div.row > div.swiper-pagination368c5917-cd88-40d0-8081-aa1be8e207a2 > span.swiper-pagination-bullet
Go to slide 6 div.browseAndShopSlider > div.row > div.swiper-pagination368c5917-cd88-40d0-8081-aa1be8e207a2 > span.swiper-pagination-bullet
Go to slide 7 div.browseAndShopSlider > div.row > div.swiper-pagination368c5917-cd88-40d0-8081-aa1be8e207a2 > span.swiper-pagination-bullet
Go to slide 8 div.browseAndShopSlider > div.row > div.swiper-pagination368c5917-cd88-40d0-8081-aa1be8e207a2 > span.swiper-pagination-bullet
Go to slide 9 div.browseAndShopSlider > div.row > div.swiper-pagination368c5917-cd88-40d0-8081-aa1be8e207a2 > span.swiper-pagination-bullet
Go to slide 10 div.browseAndShopSlider > div.row > div.swiper-pagination368c5917-cd88-40d0-8081-aa1be8e207a2 > span.swiper-pagination-bullet
Go to slide 1 div.browseAndShopSlider > div.row > div.swiper-pagination1586898863765 > span.swiper-pagination-bullet
Go to slide 2 div.browseAndShopSlider > div.row > div.swiper-pagination1586898863765 > span.swiper-pagination-bullet
Go to slide 3 div.browseAndShopSlider > div.row > div.swiper-pagination1586898863765 > span.swiper-pagination-bullet
Go to slide 4 div.browseAndShopSlider > div.row > div.swiper-pagination1586898863765 > span.swiper-pagination-bullet
Go to slide 5 div.browseAndShopSlider > div.row > div.swiper-pagination1586898863765 > span.swiper-pagination-bullet
Go to slide 6 div.browseAndShopSlider > div.row > div.swiper-pagination1586898863765 > span.swiper-pagination-bullet
Go to slide 7 div.browseAndShopSlider > div.row > div.swiper-pagination1586898863765 > span.swiper-pagination-bullet
Go to slide 8 div.browseAndShopSlider > div.row > div.swiper-pagination1586898863765 > span.swiper-pagination-bullet
Go to slide 9 div.browseAndShopSlider > div.row > div.swiper-pagination1586898863765 > span.swiper-pagination-bullet

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Shop Now div.swiper-container > div.swiper-wrapper > div.swiper-slide > a.fourByTwo
○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
●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
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●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.
●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
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○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
○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.
○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.
A+
Heading Hierarchy
2 headings
PASS
2 headings
Info::
Single H1 present
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H1 Your connection needs to be verified before you can proceed
  • H2 (empty)

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

A+
Alt Text Quality
No images
PASS
No images
Info::
No images on this page
No images on this page.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
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 404 Not Found – HarperCollins ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
A+
Color Contrast (Screenshot)
3 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.

3 pass
Show all checked elements (3)
ElementRatioRequiredFGBGResult
h1 Your connection need…21.00:13.0:1
#000000
#FFFFFF
Pass
title Just a moment...21.00:14.5:1
#000000
#FFFFFF
Pass
div Verification success…21.00:14.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.

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

Send Feedback