Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

4 PASS 3 REVIEW 6 FIX

Link & Button Quality

Action

5 issue(s) across 104 links and 3 buttons

FIX

5 issue(s) across 104 links and 3 buttons

3 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: a (#145 on page); https://www.facebook.com/IndieBound/; https://www.instagram.com/americanbooksellers/

2 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: independent-bookstore-day ("Learn more"); /indies-choice-book-awards ("Learn more")

8 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://www.facebook.com/IndieBound/; https://twitter.com/indiebound; https://www.instagram.com/americanbooksellers/; https://www.usatoday.com/booklist/independent-bookstores; https://www.usatoday.com/booklist/independent-bookstores; https://www.bookweb.org/shopping-local-heres-what-you-did-infographic; https://www.bookweb.org/shopping-local-heres-what-you-did-infographic; https://curator.io

91 link(s) with descriptive text

104 links

3 empty

2 generic text

8 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.facebook.com/IndieBound/	facebook.com/indiebound	new tab	Add '(opens in new tab)' to text
https://twitter.com/indiebound	twitter.com/indiebound	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/americanbookse…	instagram.com/americanbooksell…	new tab	Add '(opens in new tab)' to text
	(empty)	empty	Add link text or aria-label
independent-bookstore-day	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Independent Bookstore Day
/indies-choice-book-awards	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Indies Choice Book Awards
https://www.usatoday.com/booklist/indepe…	USA Today indie bookstores map	new tab	Add '(opens in new tab)' to text
https://www.usatoday.com/booklist/indepe…	The USA Today Independent Book…	new tab	Add '(opens in new tab)' to text
https://www.bookweb.org/shopping-local-h…	What You Did Just Did flyer	new tab	Add '(opens in new tab)' to text
https://www.bookweb.org/shopping-local-h…	Why Shop Indie	new tab	Add '(opens in new tab)' to text
https://curator.io	Powered by Curator.io	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/IndieBound/	(empty)	empty	Add link text or aria-label
https://www.instagram.com/americanbookse…	(empty)	empty	Add link text or aria-label

94 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

a (#145 on page); https://www.facebook.com/IndieBound/; https://www.instagram.com/americanbooksellers/

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Generic link text like 'click here' doesn't describe the destination.

independent-bookstore-day ("Learn more"); /indies-choice-book-awards ("Learn more")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

Add '(opens in new tab)' to link text or aria-label.

https://www.facebook.com/IndieBound/; https://twitter.com/indiebound; https://www.instagram.com/americanbooksellers/; https://www.usatoday.com/booklist/independent-bookstores; https://www.usatoday.com/booklist/independent-bookstores; https://www.bookweb.org/shopping-local-heres-what-you-did-infographic; https://www.bookweb.org/shopping-local-heres-what-you-did-infographic; https://curator.io

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

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 Missing

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Not found

FIX

Not found

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.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Uh oh. This chapter is closed. | IndieBound.org ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Color Contrast (Screenshot)

Action

20 text elements analyzed, 20 fail WCAG AA

REVIEW

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

0 pass 20 fail WCAG AA

h2 Your choices matter.

2.04:1

#000000

#414042

needs 3.0:1 (large text)

24px · bottom of viewport

h2 IndieBound.org uses cookies to enhance y…

2.04:1

#000000

#414042

needs 3.0:1 (large text)

24px · bottom of viewport

title IndieBound.org

1.32:1

#000000

#222222

needs 4.5:1 (normal text)

16px · top of page (header area)

a Skip to main content

1.32:1

#000000

#222222

needs 4.5:1 (normal text)

16px · top of page (header area)

a Questions? Visit our Help Center

4.45:1

#000000

#E31B23

needs 4.5:1 (normal text)

16px · top of page (header area)

span Main navigation

4.45:1

#000000

#E31B23

needs 4.5:1 (normal text)

16px · top of page (header area)

a Indie Bookstore Finder

2.45:1

#000000

#951B1E

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

a Indie Bestsellers

1.11:1

#000000

#111112

needs 4.5:1 (normal text)

16px · above the fold

a Booksellers Recommend

1.12:1

#000000

#121214

needs 4.5:1 (normal text)

16px · above the fold

a Indie Next List

1.19:1

#000000

#15191F

needs 4.5:1 (normal text)

16px · above the fold

a Kids Indie Next List

1.24:1

#000000

#171D23

needs 4.5:1 (normal text)

16px · above the fold

a Indies Introduce

1.24:1

#000000

#171D26

needs 4.5:1 (normal text)

16px · above the fold

a Indies Choice Book Awards

1.46:1

#000000

#252A33

needs 4.5:1 (normal text)

16px · above the fold

a Bookstore Day

1.81:1

#000000

#35393F

needs 4.5:1 (normal text)

16px · above the fold

a Blog

2.92:1

#000000

#61554E

needs 4.5:1 (normal text)

16px · above the fold

a About

1.69:1

#000000

#31343D

needs 4.5:1 (normal text)

16px · mid-page

a Press Contacts

1.66:1

#000000

#2F333B

needs 4.5:1 (normal text)

16px · mid-page

a Help Center

1.67:1

#000000

#2F343A

needs 4.5:1 (normal text)

16px · mid-page

a EBooks & Digital Audiobooks

1.56:1

#000000

#352D27

needs 4.5:1 (normal text)

16px · mid-page

a Become an Affiliate

1.25:1

#000000

#231C16

needs 4.5:1 (normal text)

16px · mid-page

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)

Element	Ratio	Required	FG	BG	Result
h2 Your choices matter.	2.04:1	3.0:1	#000000	#414042	Fail
h2 IndieBound.org uses …	2.04:1	3.0:1	#000000	#414042	Fail
title IndieBound.org	1.32:1	4.5:1	#000000	#222222	Fail
a Skip to main content	1.32:1	4.5:1	#000000	#222222	Fail
a Questions? Visit our…	4.45:1	4.5:1	#000000	#E31B23	Fail
span Main navigation	4.45:1	4.5:1	#000000	#E31B23	Fail
a Indie Bookstore Find…	2.45:1	4.5:1	#000000	#951B1E	Fail
a Indie Bestsellers	1.11:1	4.5:1	#000000	#111112	Fail
a Booksellers Recommen…	1.12:1	4.5:1	#000000	#121214	Fail
a Indie Next List	1.19:1	4.5:1	#000000	#15191F	Fail
a Kids Indie Next List	1.24:1	4.5:1	#000000	#171D23	Fail
a Indies Introduce	1.24:1	4.5:1	#000000	#171D26	Fail
a Indies Choice Book A…	1.46:1	4.5:1	#000000	#252A33	Fail
a Bookstore Day	1.81:1	4.5:1	#000000	#35393F	Fail
a Blog	2.92:1	4.5:1	#000000	#61554E	Fail
a About	1.69:1	4.5:1	#000000	#31343D	Fail
a Press Contacts	1.66:1	4.5:1	#000000	#2F333B	Fail
a Help Center	1.67:1	4.5:1	#000000	#2F343A	Fail
a EBooks & Digital Aud…	1.56:1	4.5:1	#000000	#352D27	Fail
a Become an Affiliate	1.25:1	4.5:1	#000000	#231C16	Fail

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.

Lighthouse Accessibility Audits

Score 88/100 — 4 failing, 24 passed

REVIEW

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.

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
Questions? Visit our Help Center `ul.inline > li > span > a`
View Our Cookie Policy. `div.popup-content > div#popup-text > h2 > a`

These are opportunities to improve the legibility of your content.

Names and labels

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.field > div > div > iframe `div.field > div > div > iframe`

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.socials > ul.footersociallinks > li.ck-list-marker-italic > a`
`div.socials > ul.footersociallinks > li.ck-list-marker-italic > 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.

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
IndieBound Blog `div.column-content-inner > div.gsc-image-content > div.box-content > h4.title`

These are opportunities to improve keyboard navigation in your application.

○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 with `role="dialog"` or `role="alertdialog"` have accessible names.

●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

●Touch targets have sufficient size and spacing.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements 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

○`<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.

○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+

Landmark Structure

11 landmarks

PASS

11 landmarks

<main> landmark present

7 <nav> landmark(s) found

All <nav> elements are properly labeled

Skip navigation link present

Page Structure — as a screen reader sees it

Heading Hierarchy

18 headings, 1 skip(s)

PASS

18 headings, 1 skip(s)

Single H1 present

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H2 Main navigation
H2 Main navigation
H2 Desktop Menu
H3 Why shop Indie?
H2 Your choices matter.
H2 Independent Spirit
H4 IndieBound Blog skipped
H4 Indie Bookstore Day
H4 Indies Choice Book Awards
H1 Independent Bookstores
H2 Independent Bookstores
H2 More on IndieBound
H2 Follow @americanbooksellers on instagram
H2 Links
H2 Booksellers Recommend
H2 Independent Spirit
H2 Campaigns
H2 IndieBound.org uses cookies to enhance your experience on our site, analyze site usage, and assist in our marketing efforts. By clicking Accept, you agree to the storing of cookies on your device. Vie

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 12 images OK

PASS

All 12 images OK

12 image(s) with good alt text

12 images 12 good alt text

All images have appropriate alt text.

Form Accessibility

1 of 1 controls have issues

PASS

1 of 1 controls have issues

1 control(s) rely on placeholder only

Placeholder text disappears on focus and is not a reliable label.

Got: <input type="text" name="q">

1 controls

0 labeled

1 placeholder only

0 unlabeled

Control	Type	Label	Method
q	text	(Zip Code, City, or Address)	placeholder only

Placeholder text disappears on focus and is not a reliable label.

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

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