Skip to content
https://lulu.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
55
GRADE
D
FIX
6
REVIEW
3
PASS
4
INFO
0
Checks
13
4 PASS 3 REVIEW 6 FIX
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Info::
favicon.ico present at site root
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'>.
✓ favicon.ico Present
✗ 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::
1 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
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 1 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Heading Hierarchy
Action
24 headings, 3 skip(s)
REVIEW
24 headings, 3 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Global Publishing Technology for Businesses Built on Books
  • H3 Authors & Creators skipped
  • H3 Entrepreneurs & Startups
  • H3 Businesses & Brands
  • H3 Enterprise Publishers
  • H3 Trusted by Top Global Brands
  • H3 Publish or Print a Book
  • H3 Direct-to-Consumer Sales
  • H3 Global Book Fulfillment & Infrastructure
  • H3 Personalized Products at Scale
  • H2 How Does Lulu Work?
  • H3 Upload
  • H3 Sell
  • H3 Print
  • H3 Fulfillment
  • H3 Affiliations & Partners
  • H2 “...a game-changer for my company”
  • H2 ”
  • H4 “Working with Lulu was a game-changer for my company! They integrate so smoothly with my personal Shopify store, and their customer support has been top-notch.” skipped
  • H2 ”
  • H4 “Before switching to the Lulu API, I was spending 1–3 minutes per order manually entering customer details, addresses, and credit card info—one form at a time. Since moving to the Lulu API, it�� skipped
  • H2 “Since moving to the Lulu API, it’s night and day...”
  • H2 Security & Sustainability
  • H2 Get Started

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

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

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

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 Page Not Found | Lulu ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 4 fail WCAG AA
REVIEW

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

16 pass 4 fail WCAG AA
h1 Global Publishing Technology for Busines…
1.10:1
#FFFFFF
on
#F5F4F2
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Get Started
1.10:1
#FFFFFF
on
#F5F4F2
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Entrepreneurs & Startups
1.10:1
#FFFFFF
on
#F5F4F2
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Enterprise Publishers
1.10:1
#FFFFFF
on
#F5F4F2
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Global Publishing Te…1.10:13.0:1
#FFFFFF
#F5F4F2
Fail
h2 How Does Lulu Work?10.39:13.0:1
#303A4D
#F5F4F2
Pass
h2 “...a game-changer…5.58:13.0:1
#564FD0
#F5F4F2
Pass
h2 ”5.58:13.0:1
#564FD0
#F5F4F2
Pass
h2 ”5.58:13.0:1
#564FD0
#F5F4F2
Pass
h2 “5.58:13.0:1
#564FD0
#F5F4F2
Pass
h2 Since moving to the …5.58:13.0:1
#564FD0
#F5F4F2
Pass
h2 ”5.58:13.0:1
#564FD0
#F5F4F2
Pass
h2 Security & Sustainab…10.39:13.0:1
#303A4D
#F5F4F2
Pass
h2 Get Started1.10:13.0:1
#FFFFFF
#F5F4F2
Fail
h3 Authors & Creators10.39:13.0:1
#303A4D
#F5F4F2
Pass
h3 Entrepreneurs & Star…1.10:13.0:1
#FFFFFF
#F5F4F2
Fail
h3 Businesses & Brands10.39:13.0:1
#303A4D
#F5F4F2
Pass
h3 Enterprise Publisher…1.10:13.0:1
#FFFFFF
#F5F4F2
Fail
h3 Trusted by Top Globa…10.39:13.0:1
#303A4D
#F5F4F2
Pass
h3 Publish or Print a B…19.10:13.0:1
#000000
#F5F4F2
Pass
h3 Direct-to-Consumer S…19.10:13.0:1
#000000
#F5F4F2
Pass
h3 Global Book Fulfillm…19.10:13.0:1
#000000
#F5F4F2
Pass
h3 Personalized Product…19.10:13.0:1
#000000
#F5F4F2
Pass
h3 Upload10.39:13.0:1
#303A4D
#F5F4F2
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
4 landmarks
PASS
4 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) 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 NAV MAIN 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

A+
Alt Text Quality
All 30 images OK
PASS
All 30 images OK
Info::
30 image(s) with good alt text
30 images 30 good alt text
All images have appropriate alt text.
A+
Form Accessibility
All 1 controls labeled
PASS
All 1 controls labeled
Info::
1 control(s) properly labeled
1 controls
1 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
emailemailYour Emailaria-label
A+
Lighthouse Accessibility Audits
Score 98/100 — 2 failing, 23 passed
PASS
98

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
Authors & Creators div.NewElementCard-module_elementCard__OciVn > section.res-horizontal-padding-16 > div.RichTextContainer-module_richTextContainer__Hdr3- > h3.typo-brand-heading-h3
“Working with Lulu was a game-changer for my company! They integrate so smoothl… div.NewElementCard-module_elementCard__OciVn > section > div.RichTextContainer-module_richTextContainer__Hdr3- > h4.typo-brand-heading-h4
“Before switching to the Lulu API, I was spending 1–3 minutes per order manuall… div.NewElementCard-module_elementCard__OciVn > section > div.RichTextContainer-module_richTextContainer__Hdr3- > h4.typo-brand-heading-h4

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
Authors & Creators Publish, print, and sell professional-quality custom books … div.Grid-module_wrapperWithBgColor__I5JS8 > div.grid-12 > div.col-3 > a.NewElementCard-module_asLink__cQJKF
Entrepreneurs & Startups Build your brand and monetize your audience with ecom… div.Grid-module_wrapperWithBgColor__I5JS8 > div.grid-12 > div.col-3 > a.NewElementCard-module_asLink__cQJKF
Businesses & Brands API-enabled integrations for book printing and fulfillment… div.Grid-module_wrapperWithBgColor__I5JS8 > div.grid-12 > div.col-3 > a.NewElementCard-module_asLink__cQJKF
Enterprise Publishers Scaling print and fulfillment solutions for direct-to-co… div.Grid-module_wrapperWithBgColor__I5JS8 > div.grid-12 > div.col-3 > a.NewElementCard-module_asLink__cQJKF
○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
●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
●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
●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
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○`[aria-hidden="true"]` elements do not contain focusable descendents
○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
○`<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
○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.
○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.
○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