Skip to content
https://hachettebookgroup.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
58
GRADE
D
FIX
6
REVIEW
4
PASS
3
INFO
0
Checks
13
3 PASS 4 REVIEW 6 FIX
D
Landmark Structure
Action
20 landmarks
FIX
20 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
10 <nav> landmark(s) found
Warning::
1 of 10 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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.
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER header NAV SEARCH MAIN (missing!) CONTENTINFO footer

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

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

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

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 ✗
D
Navigation UX
Action
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Info::
10 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search role='search' landmark
Skip Link
Labeled Navigation 10 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Novel Suspects Logo ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
B
Favicon & Branding
4 icon(s) detected
REVIEW
4 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 Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 15 fail WCAG AA
REVIEW

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

5 pass 15 fail WCAG AA 4 pass AA only
h1 Hachette Book Group Homepage
2.77:1
#000000
on
#245A70
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Promotion
2.91:1
#000000
on
#4D595E
needs 3.0:1 (large text)
24px · top of page (header area) · over background image/gradient
h2 Search
2.77:1
#000000
on
#245A70
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Site Preferences
2.77:1
#000000
on
#245A70
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Hachette Book Group
2.77:1
#000000
on
#245A70
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Carousel pagination
2.77:1
#000000
on
#245A70
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Carousel pagination
2.77:1
#000000
on
#245A70
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Banned & Challenged Books
2.77:1
#000000
on
#245A70
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Our Authors
2.77:1
#000000
on
#245A70
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Carousel pagination
2.77:1
#000000
on
#245A70
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Discover More
2.77:1
#000000
on
#245A70
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Footer
2.77:1
#000000
on
#245A70
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Shopping Cart
2.77:1
#000000
on
#245A70
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Social Media
2.77:1
#000000
on
#245A70
needs 3.0:1 (large text)
19px · bottom of viewport
title Hachette Book Group
1.46:1
#000000
on
#122D38
needs 4.5:1 (normal text)
16px · top of page (header area)

1 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)
ElementRatioRequiredFGBGResult
h1 Hachette Book Group …2.77:13.0:1
#000000
#245A70
Fail
h2 Promotion2.91:13.0:1
#000000
#4D595E
Fail
h2 Explore Hachette Boo…4.69:13.0:1
#000000
#717975
Pass
h2 Search2.77:13.0:1
#000000
#245A70
Fail
h2 Site Preferences2.77:13.0:1
#000000
#245A70
Fail
h2 Hachette Book Group2.77:13.0:1
#000000
#245A70
Fail
h2 Carousel pagination2.77:13.0:1
#000000
#245A70
Fail
h2 Carousel pagination2.77:13.0:1
#000000
#245A70
Fail
h2 Banned & Challenged …2.77:13.0:1
#000000
#245A70
Fail
h2 Our Authors2.77:13.0:1
#000000
#245A70
Fail
h2 Carousel pagination2.77:13.0:1
#000000
#245A70
Fail
h2 Discover More2.77:13.0:1
#000000
#245A70
Fail
h2 Footer2.77:13.0:1
#000000
#245A70
Fail
h2 Shopping Cart2.77:13.0:1
#000000
#245A70
Fail
h3 Social Media2.77:13.0:1
#000000
#245A70
Fail
title Hachette Book Group1.46:14.5:1
#000000
#122D38
Fail
a Use code MOM26 for 2…4.65:14.5:1
#000000
#747778
Pass
span Close menu4.63:14.5:1
#000000
#707874
Pass
span menu4.71:14.5:1
#000000
#727976
Pass
a Genres4.69:14.5:1
#000000
#717975
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.

B
Lighthouse Accessibility Audits
Score 86/100 — 4 failing, 25 passed
REVIEW
86

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

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
× div#page > div#privacy_collapse > div.panel-body > div#headingOne

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
× div.panel-body > div#headingOne > h4.panel-title > button#closePrivacyOptInOut

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.

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
× div#privacy_collapse > div.panel-body > div#headingOne > h4.panel-title

These are opportunities to improve keyboard navigation in your application.

Names and labels

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.site-header__main > div.site-header__container > button.user-account__button > a div.site-header__main > div.site-header__container > button.user-account__button > a

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.

○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]` values are valid
●`[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
●`[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.
●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
●Image elements do not have `[alt]` attributes that are redundant text.
●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 input fields 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 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
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○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
○Identical links have the same purpose.
○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
22 headings, 1 skip(s)
PASS
22 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 Promotion
  • H2 Explore Hachette Book Group menu
  • H2 Search
  • H2 Site Preferences
  • H2 Hachette Book Group menu
  • H4 × skipped
  • H1 Hachette Book Group Homepage
  • H2 Inspiring Reads for Autism Awareness Month
  • H2 Carousel pagination
  • H2 Carousel pagination
  • H2 Sign up to receive emails from Hachette Book Group.
  • H2 Banned & Challenged Books
  • H2 Our Authors
  • H2 Carousel pagination
  • H2 Discover More
  • H2 Footer
  • H3 Social Media
  • H2 Get recommended reads, deals, and more from Hachette.
  • H3 About About
  • H3 Resources Resources
  • H3 Terms and Policies Terms and Policies
  • H2 Shopping Cart

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 116 images OK
PASS
All 116 images OK
Info::
10 decorative image(s) correctly marked
Info::
106 image(s) with good alt text
116 images 106 good alt text 10 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 5 controls labeled
PASS
All 5 controls labeled
Info::
5 control(s) properly labeled
5 controls
5 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#search-form-25searchSearch Hachettefor/id
#user-preferences-currency-usdradionone
#user-preferences-currency-cadradionone
#email_01KM0X9F7F2DWDXA0P8XEVCMPKemailYour email addressfor/id
#email_01KM0WJFVS2C05J0M065BMXB8PemailEmailfor/id
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback