Skip to content
https://blurb.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
57
GRADE
D
FIX
6
REVIEW
3
PASS
4
INFO
0
Checks
13
4 PASS 3 REVIEW 6 FIX
D
Favicon & Branding
Action
3 icon(s) detected
FIX
3 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::
SVG favicon detected — scales perfectly to any size
✓ favicon.ico Present
✓ PNG Icons Present
✗ Apple Touch Missing
✓ SVG Favicon Present
✗ 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::
2 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 2 <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.
B
Landmark Structure
6 landmarks
REVIEW
6 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <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.
Page Structure — as a screen reader sees it
BANNER header NAV MAIN CONTENTINFO footer

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

C
404 Error Page
Action
Could not test
REVIEW
Could not test
Info::
404 page could not be tested
The 404 page check encountered an error. This may be due to a timeout or network issue.

404 page quality check not available.

B
Lighthouse Accessibility Audits
Score 83/100 — 5 failing, 23 passed
REVIEW
83

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.

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.block > div.embla > div.embla__dots > button.embla__dot div.block > div.embla > div.embla__dots > button.embla__dot
div.block > div.embla > div.embla__dots > button.embla__dot div.block > div.embla > div.embla__dots > button.embla__dot
div.block > div.embla > div.embla__dots > button.embla__dot div.block > div.embla > div.embla__dots > button.embla__dot
div.block > div.embla > div.embla__dots > button.embla__dot div.block > div.embla > div.embla__dots > button.embla__dot
div.flex > div.embla > div.embla__dots > button.embla__dot div.flex > div.embla > div.embla__dots > button.embla__dot
div.flex > div.embla > div.embla__dots > button.embla__dot div.flex > div.embla > div.embla__dots > button.embla__dot
div.flex > div.embla > div.embla__dots > button.embla__dot div.flex > div.embla > div.embla__dots > button.embla__dot
div.flex > div.embla > div.embla__dots > button.embla__dot div.flex > div.embla > div.embla__dots > button.embla__dot
div.flex > div.embla > div.embla__dots > button.embla__dot div.flex > div.embla > div.embla__dots > button.embla__dot
div.flex > div.embla > div.embla__dots > button.embla__dot div.flex > div.embla > div.embla__dots > button.embla__dot
div.flex > div.embla > div.embla__dots > button.embla__dot div.flex > div.embla > div.embla__dots > button.embla__dot
div.flex > div.embla > div.embla__dots > button.embla__dot div.flex > div.embla > div.embla__dots > button.embla__dot
div.flex > div.embla > div.embla__dots > button.embla__dot div.flex > div.embla > div.embla__dots > button.embla__dot
div.flex > div.embla > div.embla__dots > button.embla__dot div.flex > div.embla > div.embla__dots > button.embla__dot
div.flex > div.embla > div.embla__dots > button.embla__dot div.flex > div.embla > div.embla__dots > button.embla__dot
div.flex > div.embla > div.embla__dots > button.embla__dot div.flex > div.embla > div.embla__dots > button.embla__dot

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#nav-auth-container > div.block > div.flex > a div#nav-auth-container > div.block > div.flex > a
div.text-blurb-text-inverse > div.flex > div.flex > a.text-blurb-text-inverse div.text-blurb-text-inverse > div.flex > div.flex > a.text-blurb-text-inverse
div.text-blurb-text-inverse > div.flex > div.flex > a.text-blurb-text-inverse div.text-blurb-text-inverse > div.flex > div.flex > a.text-blurb-text-inverse
div.text-blurb-text-inverse > div.flex > div.flex > a.text-blurb-text-inverse div.text-blurb-text-inverse > div.flex > div.flex > a.text-blurb-text-inverse
div.text-blurb-text-inverse > div.flex > div.flex > a.text-blurb-text-inverse div.text-blurb-text-inverse > div.flex > div.flex > a.text-blurb-text-inverse
div.text-blurb-text-inverse > div.flex > div.flex > a.text-blurb-text-inverse div.text-blurb-text-inverse > div.flex > div.flex > a.text-blurb-text-inverse

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
Privacy Policy div.osano-cm-window > div#84130079-22a3-4f1c-bda3-aa1bd3f2c0da > div.osano-cm-dialog__content > a.osano-cm-storage-policy

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
Professional bookstore-grade quality div.value-props-container > div.value-props-items > div.flex > h4.text-left

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
div.block > div.embla > div.embla__dots > button.embla__dot div.block > div.embla > div.embla__dots > button.embla__dot
div.block > div.embla > div.embla__dots > button.embla__dot div.block > div.embla > div.embla__dots > button.embla__dot
div.block > div.embla > div.embla__dots > button.embla__dot div.block > div.embla > div.embla__dots > button.embla__dot

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
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●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 with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[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
●ARIA IDs are unique
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○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
○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.
○Elements with visible text labels have matching accessible names.
○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
23 headings, 1 skip(s)
PASS
23 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 Promotional Information
  • H2 Save 20% at the Blurb Bookstore*
  • H2 Navigation menu
  • H1 Your story starts here
  • H2 Books and other products for every creative expression
  • H3 Photo Books
  • H3 Paperback & Hardcover
  • H3 Magazines
  • H3 Notebooks & Journals
  • H2 Tools and resources for makers, sellers, and businesses
  • H2 The Blurb Difference
  • H4 Professional bookstore-grade quality skipped
  • H4 Trusted printing partner
  • H4 Sustainable papers & practices
  • H4 Complete creative control
  • H2 Thanks for joining!
  • H2 Want 30% off? Sign up and save on your first book.
  • H2 Inspiring examples made with Blurb
  • H3 Branding at its best
  • H3 A travel treasure
  • H3 Refueling print
  • H2 Have questions?Get answers.
  • H2 Ready to 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

A+
Alt Text Quality
All 51 images OK
PASS
All 51 images OK
Info::
2 image(s) with alt text over 125 characters
Info::
3 decorative image(s) correctly marked
Info::
46 image(s) with good alt text
51 images 46 good alt text 3 decorative
IssueCount
too long2 image(s)
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
emailemailEmail Addressnone
A+
Color Contrast (Screenshot)
20 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.

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Your story starts he…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Promotional Informat…14.03:13.0:1
#000000
#E5D0B6
Pass
h2 Save 20% at the Blur…11.94:13.0:1
#000000
#D7C0A1
Pass
h2 Navigation menu21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Books and other prod…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Tools and resources …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 The Blurb Difference21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Thanks for joining!21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Want 30% off? Sign u…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Inspiring examples m…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Have questions?21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Get answers.21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Ready to get started…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Photo Books21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Paperback & Hardcove…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Magazines21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Notebooks & Journals21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Branding at its best21.00:13.0:1
#000000
#FFFFFF
Pass
h3 A travel treasure21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Refueling print21.00:13.0: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