Skip to content
https://penguinrandomhouse.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
64
GRADE
D
FIX
3
REVIEW
6
PASS
4
INFO
0
Checks
13
4 PASS 6 REVIEW 3 FIX
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.

F
Navigation UX
Action
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
2 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 2 <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
Alt Text Quality
Action
6 of 80 images have issues
REVIEW
6 of 80 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
1 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Warning::
5 image(s) with generic alt text
Info::
5 decorative image(s) correctly marked
Info::
69 image(s) with good alt text
80 images 69 good alt text 5 decorative 5 generic 1 missing
IssueCount
missing1 image(s)
generic5 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

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

C
Form Accessibility
Action
3 of 4 controls have issues
REVIEW
3 of 4 controls have issues
Critical::
3 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit">; <input type="checkbox" name="privacy_pref_optin" id="privacy_pref_optin">; <input type="checkbox" name="privacy_pref_optout" id="privacy_pref_optout">
Info::
1 control(s) properly labeled
4 controls
1 labeled
0 placeholder only
3 unlabeled
ControlTypeLabelMethod
#search-boxsearchSearcharia-label
inputsubmit(none)none
#privacy_pref_optincheckbox(none)none
#privacy_pref_optoutcheckbox(none)none

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

<input type="submit">; <input type="checkbox" name="privacy_pref_optin" id="privacy_pref_optin">; <input type="checkbox" name="privacy_pref_optout" id="privacy_pref_optout">

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

B
404 Error Page
HTTP 404, custom page
REVIEW
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
404 Page Quality Custom 404 Page
Status Code HTTP 404 Page Title cart Custom Styling Navigation Homepage Link Search Form
C
Favicon & Branding
Action
4 icon(s) detected
REVIEW
4 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
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'>.
Info::
Multiple icon sizes detected
favicon.ico Present
PNG Icons Present
Apple Touch Missing
SVG Favicon Missing
Manifest Icons Missing
Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 9 fail WCAG AA
REVIEW

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

11 pass 9 fail WCAG AA 3 pass AA only
h1 Must-Read Fiction by Arab and Arab Ameri…
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Cookies and Similar Technologies
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Must-Read Fiction by Arab and Arab Ameri…
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 The Most Recent Celebrity Book Club Pick…
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 The Most Recent Celebrity Book Club Pick…
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Shop Your Next Book
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Discover Your Next Read
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Categories
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Success!
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Must-Read Fiction by…1.00:13.0:1
#000000
#000000
Fail
h1 Cookies and Similar …1.00:13.0:1
#000000
#000000
Fail
h2 Must-Read Fiction by…1.00:13.0:1
#000000
#000000
Fail
h2 The Most Recent Cele…1.00:13.0:1
#000000
#000000
Fail
h2 The Most Recent Cele…1.00:13.0:1
#000000
#000000
Fail
h2 Shop Your Next Book1.00:13.0:1
#000000
#000000
Fail
h2 Discover Your Next R…1.00:13.0:1
#000000
#000000
Fail
h2 Categories1.00:13.0:1
#000000
#000000
Fail
h2 Success!1.00:13.0:1
#000000
#000000
Fail
title Penguin Random House17.79:14.5:1
#000000
#FFE8D8
Pass
a Skip to Main Content…17.79:14.5:1
#000000
#FFE8D8
Pass
div 📝 Quiz: What Book…21.00:14.5:1
#000000
#FFFFFF
Pass
div 📝 Quiz: What Book…21.00:14.5:1
#000000
#FFFFFF
Pass
p Books11.17:14.5:1
#000000
#B0C1B8
Pass
p Kids6.90:14.5:1
#000000
#AA8D8C
Pass
p Popular6.06:14.5:1
#000000
#A6817D
Pass
p Authors & Events12.33:14.5:1
#000000
#B0CCC9
Pass
p Recommendations5.85:14.5:1
#000000
#A67D7D
Pass
p Audio7.58:14.5:1
#000000
#AB9793
Pass
div How To Read More Thi…15.95:14.5:1
#000000
#F5DCC8
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+
Landmark Structure
6 landmarks
PASS
6 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "side-nav" MAIN CONTENTINFO footer
A
Heading Hierarchy
13 headings
PASS
13 headings
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H1 Must-Read Fiction by Arab and Arab American Authors
  • H2 Must-Read Fiction by Arab and Arab American Authors
  • H2 The Most Recent Celebrity Book Club Picks of 2026
  • H2 The Most Recent Celebrity Book Club Picks of 2026
  • H2 Shop Your Next Book
  • H3 new releases
  • H3 coming soon
  • H3 best sellers
  • H3 award winners
  • H2 Discover Your Next Read
  • H2 Categories
  • H2 Success!
  • H1 Cookies and Similar Technologies duplicate H1

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

A+
Print Stylesheet
Print styles detected
PASS
Print styles detected
Info::
External print stylesheet detected
Got: /wp-content/themes/penguinrandomhouse/styles-print.min.css?ver=cb20260402025234
Print Stylesheet Print Optimized
Print stylesheet /wp-content/themes/penguinrandomhouse/styles-print.min.css?ver=cb20260402025234 Inline @media print Not detected
A+
Lighthouse Accessibility Audits
Score 96/100 — 2 failing, 27 passed
PASS
96

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

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Cookies and Similar Technologies We, our affiliates, and our providers use coo… body.wp-singular > div#__tealiumGDPRecModal > div#prh_privacy_prompt
Read More div#prh_privacy_prompt > div.privacy_prompt_content > p#prh_pp_copy > span#strt_inx
I Decline All Cookies div#__tealiumGDPRecModal > div#prh_privacy_prompt > div.privacy_prompt_footer > div#consent_prompt_decline
I Agree div#__tealiumGDPRecModal > div#prh_privacy_prompt > div.privacy_prompt_footer > div#consent_prompt_submit
body.wp-singular > div#__tealiumGDPRecModal > div#prh_privacy_prompt > div#prh_mdl_close

These are opportunities to improve keyboard navigation in your application.

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
Brightly Raise kids who love to read main#mainblock > div.container > div.footer-bttm-links > a.footer-bttm-link
Out of Print Shirts, totes, socks, and more for book lovers main#mainblock > div.container > div.footer-bttm-links > a.footer-bttm-link
TASTE An online magazine for today’s home cook main#mainblock > div.container > div.footer-bttm-links > a.footer-bttm-link
Today's Top Books Want to know what people are actually reading right now? main#mainblock > div.container > div.footer-bttm-links > a.footer-bttm-link
Wonderbly Personalized books for kids and adults main#mainblock > div.container > div.footer-bttm-links > a.footer-bttm-link
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
Buttons have an accessible name
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.
`button`, `link`, and `menuitem` elements have accessible names
ARIA attributes are used as specified for the element's role
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
`[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 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
Touch targets have sufficient size and spacing.
Heading elements appear in a sequentially-descending order
Skip links are focusable.
Document has a main landmark.
Deprecated ARIA roles were not used
ARIA IDs are unique
`[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
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
Links are distinguishable without relying on color.
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
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.
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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback