Accessibility

D

Landmark Structure

Action

No landmarks

FIX

No landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

No <nav> landmark found

No banner (header) landmark

No contentinfo (footer) landmark

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.

No landmarks detected

Screen reader users have no way to navigate by region.

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

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

F

Heading Hierarchy

Action

89 headings, 24 skip(s)

FIX

89 headings, 24 skip(s)

No H1 heading found

Every page should have one H1 that describes the page content.

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

H2 “Clitter” is a Real World: And Other Discoveries Reading the First Draft of Stephen King’s Pet Sematary
H3 Caroline Bicks Explores the Literary Legacy of an Undisputed Master of the Genre
H2 And the Best Literary Film Adaptation of the Last 50 Years is...
H3 Not Exactly Inconceivable
H2 What is the Best Literary Film Adaptation of the Last 50 Years? The Final Matchup
H3 Either Way, We’re in Fantasy Land
H2 What is the Best Literary Film Adaptation of the Last 50 Years? Day Five
H3 Out of the Park and Clueless-less
H2 Are Shakespeare’s Commas Really That Important?
H4 By Daniel Hahn skipped
H2 The Power of Prophecy, from Apollo to AI
H4 By Carissa Véliz skipped
H2 Jayne Anne Phillips Wonders What Happens to Writers If They Don’t Write?
H4 By Jayne Anne Phillips skipped
H2 The Hub
H3 News, Notes, Talk
H4 BPL Chief Librarian Edwin B. Maxwell on his favorite books about libraries.
H4 One great poem to read today: Carson Jordan’s “Permiso”
H4 Meet the shortlisted writers for the 2026 Women’s Prize for Fiction.
H4 Why a group of writers and artists is boycotting the 92nd Street Y.
H4 Here’s the shortlist for the 2026 Carol Shields Prize for Fiction.
H4 One great poem to read today: Allen Ginsberg’s “A Supermarket in California”
H4 Jayne Anne Phillips, Xochitl Gonzalez, T. C. Boyle, and more: 20 new books out today!
H4 $2M worth of stolen rare books have been returned to the Whitney family.
H4 One great poem to read today: Ada Limón’s “The Noisiness of Sleep”
H4 These were the 11 most challenged books in 2025.
H4 Here’s what’s making us happy this week.
H4 This week’s news in Venn diagrams.
H2 Have We Entertained Ourselves Into a State of Emergency?
H4 By Megan Garber skipped
H2 A Poem by Christopher Kondrich
H4 By Christopher Kondrich skipped
H2 Pollinating Our Stories: What Honeybees Taught Me About Writing
H4 By Eileen Garvin skipped
H2 Becca Rothfeld (with Herman Melville and John Updike)
H4 By The Writers Institute skipped
H2 On the Crazy 1963 Tour That Established the Rolling Stones’ Bad Boy Image
H4 By Bob Spitz skipped
H2 Why We All Hate the Word “Moist” So Much
H4 By Valerie Fridland skipped
H2 Best ReviewedBooks of the Week
H2 YourDaily Fiction
H2 Jayne Anne Phillips on Chronicling Her West Virginia Upbringing and Writer’s Journey
H4 By Jane Ciabattari skipped
H2 How Lewis and Clark Invented the Western
H4 By Craig Fehrman skipped
H2 Eight Books About Women With Secret Lives
H4 By Bonnie Friedman skipped
H2 When (and Why) Exactly Did Elon Musk Make His Hard Turn to the Right?
H4 By Quinn Slobodian and Ben Tarnoff skipped
H2 On the Unique and Ongoing Relationship Between Bob Dylan and the Beatles
H4 By Jim Windolf skipped
H2 How Writing Helped Me Heal After a Trauma
H4 By Grace Spulak skipped
H4 Crime Reads
H5 April 20, 2026
H4 10 New Books Coming Out This Week
H5 By CrimeReads
H4 The Best International Fiction of April 2026
H5 By Molly Odintz
H4 10 New Books Coming Out This Week
H5 By CrimeReads
H4 The Best Psychological Thrillers of April 2026
H5 By Molly Odintz
H4 Book Marks
H4 The Best Reviewed Books of the Week
H4 5 Reviews You Need to Read This Week
H2 On the Dark Arts of Writing Dangerously (and Marriage, and Life in L.A.)
H4 By Luke Goebel skipped
H2 The Annotated Nightstand: What Rachel Khong is Reading Now, And Next
H4 By Diana Arterian skipped
H2 Polly Barton on Ryunosuke Akutagawa’s Hell of Solitude
H4 By Polly Barton skipped
H2 This Week in Literary History: Mae West is Sentenced to Ten Days in Jail for Obscenity
H4 By Literary Hub skipped
H2 On the Systematic Annihilation of Gaza’s Educational Future
H4 By Taqwa Ahmed Alwawi skipped
H2 Of the Many Types of Roman Gladiator, Some Were Definitely Women
H4 By Harry Sidebottom skipped
H2 Rasputin: Fraud, Mystic, Womanizer, Prophet... Or All of the Above?
H4 By Antony Beevor skipped
H2 God Bless the Pill: Meet the Devout Catholic Who Invented Oral Contraception
H4 By Samira K. Mehta skipped
H2 Of the Many Types of Roman Gladiator, Some Were Definitely Women
H4 By Harry Sidebottom skipped
H2 April 22, 2026
H2 Follow Us
H2 Support Lit Hub.
H2 Literary Hub

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

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

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

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

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

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

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

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

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

F

Alt Text Quality

Action

69 of 82 images have issues

FIX

69 of 82 images have issues

69 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

67 image-in-link without alt text

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

2 decorative image(s) correctly marked

11 image(s) with good alt text

82 images 11 good alt text 2 decorative 69 missing

Issue	Count
missing	69 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

F

Link & Button Quality

Action

27 issue(s) across 267 links and 8 buttons

FIX

27 issue(s) across 267 links and 8 buttons

26 link(s) with no accessible text

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

Got: https://www.threads.com/@literaryhub; https://www.tiktok.com/@lit.hub; https://www.instagram.com/literaryhub/; https://www.facebook.com/lithub; https://www.youtube.com/@Literary_Hub; https://bsky.app/profile/literaryhub.bsky.social; https://mastodon.social/@literaryhub; https://www.tumblr.com/lithub; a.icons (#190 on page); https://www.threads.com/@literaryhub (+16 more)

43 image-only link(s) without alt text

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

Got: a[href="https://lithub.com/chief-librarian-edwin-b-maxwell-on-his-favorite-books-abou…"]; a[href="https://lithub.com/one-great-poem-to-read-today-carson-jordans-permiso/"]; a[href="https://lithub.com/meet-the-shortlisted-writers-for-the-2026-womens-prize-for…"]; a[href="https://lithub.com/why-a-group-of-writers-and-artists-is-boycotting-the-92nd-…"]; a[href="https://lithub.com/heres-the-shortlist-for-the-2026-carol-shields-prize-for-f…"]; a[href="https://lithub.com/one-great-poem-to-read-today-allen-ginsbergs-a-supermarket…"]; a[href="https://lithub.com/jayne-anne-phillips-xochitl-gonzalez-t-c-boyle-and-more-20…"]; a[href="https://lithub.com/2m-worth-of-stolen-rare-books-have-been-returned-to-the-wh…"]; a[href="https://lithub.com/one-great-poem-to-read-today-ada-limons-the-noisiness-of-s…"]; a[href="https://lithub.com/these-were-the-11-most-challenged-books-in-2025/"] (+33 more)

6 link(s) open in new tab without warning

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

Got: https://literaryhub.myshopify.com/products/lit-hub-hat; https://daily.jstor.org/how-america-racialized-the-robot/; https://www.theatlantic.com/magazine/2026/05/billionaire-consequence-free-rea…; https://www.publicbooks.org/the-hypochondriacs-complaint/; https://lithub.memberful.com/join; https://bookshop.org

1 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button (#307 on page)

192 link(s) with descriptive text

267 links

26 empty

0 generic text

6 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
https://www.threads.com/@literaryhub	(empty)	empty	Add link text or aria-label
https://www.tiktok.com/@lit.hub	(empty)	empty	Add link text or aria-label
https://www.instagram.com/literaryhub/	(empty)	empty	Add link text or aria-label
https://www.facebook.com/lithub	(empty)	empty	Add link text or aria-label
https://www.youtube.com/@Literary_Hub	(empty)	empty	Add link text or aria-label
https://bsky.app/profile/literaryhub.bsk…	(empty)	empty	Add link text or aria-label
https://mastodon.social/@literaryhub	(empty)	empty	Add link text or aria-label
https://www.tumblr.com/lithub	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
https://literaryhub.myshopify.com/produc…	BUY A HAT	new tab	Add '(opens in new tab)' to text
https://lithub.com/chief-librarian-edwin…	BPL Chief Librarian Edwin B. M…	img no alt	Add alt attribute to the image
https://lithub.com/one-great-poem-to-rea…	One great poem to read today: …	img no alt	Add alt attribute to the image
https://lithub.com/meet-the-shortlisted-…	Meet the shortlisted writers f…	img no alt	Add alt attribute to the image
https://lithub.com/why-a-group-of-writer…	Why a group of writers and art…	img no alt	Add alt attribute to the image
https://lithub.com/heres-the-shortlist-f…	Here’s the shortlist for the…	img no alt	Add alt attribute to the image
https://lithub.com/one-great-poem-to-rea…	One great poem to read today: …	img no alt	Add alt attribute to the image
https://lithub.com/jayne-anne-phillips-x…	Jayne Anne Phillips, Xochitl G…	img no alt	Add alt attribute to the image
https://lithub.com/2m-worth-of-stolen-ra…	$2M worth of stolen rare books…	img no alt	Add alt attribute to the image
https://lithub.com/one-great-poem-to-rea…	One great poem to read today: …	img no alt	Add alt attribute to the image
https://lithub.com/these-were-the-11-mos…	These were the 11 most challen…	img no alt	Add alt attribute to the image
https://lithub.com/heres-whats-making-us…	Here’s what’s making us ha…	img no alt	Add alt attribute to the image
https://lithub.com/this-weeks-news-in-ve…	This week’s news in Venn dia…	img no alt	Add alt attribute to the image
https://lithub.com/have-we-entertained-o…	Have We Entertained Ourselves …	img no alt	Add alt attribute to the image
https://lithub.com/a-poem-by-christopher…	A Poem by Christopher Kondrich	img no alt	Add alt attribute to the image
https://lithub.com/pollinating-our-stori…	Pollinating Our Stories: What …	img no alt	Add alt attribute to the image
https://lithub.com/becca-rothfeld-with-h…	Becca Rothfeld (with Herman Me…	img no alt	Add alt attribute to the image
https://lithub.com/on-the-crazy-1963-tou…	On the Crazy 1963 Tour That Es…	img no alt	Add alt attribute to the image
https://lithub.com/why-we-all-hate-the-w…	Why We All Hate the Word “Mo…	img no alt	Add alt attribute to the image
https://lithub.com/the-abyss-jeyamohan/	The Abyss	img no alt	Add alt attribute to the image
https://lithub.com/permanence/	Permanence	img no alt	Add alt attribute to the image
https://lithub.com/lidie/	Lidie	img no alt	Add alt attribute to the image
https://lithub.com/small-boat/	Small Boat	img no alt	Add alt attribute to the image
https://lithub.com/delivery/	Delivery	img no alt	Add alt attribute to the image
https://lithub.com/the-abyss-jeyamohan/	The Abyss	img no alt	Add alt attribute to the image
https://lithub.com/permanence/	Permanence	img no alt	Add alt attribute to the image
https://lithub.com/jayne-anne-phillips-o…	Jayne Anne Phillips on Chronic…	img no alt	Add alt attribute to the image
https://lithub.com/how-lewis-and-clark-i…	How Lewis and Clark Invented t…	img no alt	Add alt attribute to the image
https://lithub.com/eight-books-about-wom…	Eight Books About Women With S…	img no alt	Add alt attribute to the image
https://lithub.com/when-and-why-exactly-…	When (and Why) Exactly Did Elo…	img no alt	Add alt attribute to the image
https://lithub.com/on-the-unique-and-ong…	On the Unique and Ongoing Rela…	img no alt	Add alt attribute to the image
https://lithub.com/how-writing-helped-me…	How Writing Helped Me Heal Aft…	img no alt	Add alt attribute to the image
https://crimereads.com/10-new-books-comi…	10 New Books Coming Out This W…	img no alt	Add alt attribute to the image
https://bookmarks.reviews/the-best-revie…	The Best Reviewed Books of the…	img no alt	Add alt attribute to the image
https://bookmarks.reviews/5-reviews-you-…	5 Reviews You Need to Read Thi…	img no alt	Add alt attribute to the image
https://lithub.com/on-the-dark-arts-of-w…	On the Dark Arts of Writing Da…	img no alt	Add alt attribute to the image
https://lithub.com/the-annotated-nightst…	The Annotated Nightstand: What…	img no alt	Add alt attribute to the image
https://lithub.com/polly-barton-on-ryuno…	Polly Barton on Ryunosuke Akut…	img no alt	Add alt attribute to the image
https://lithub.com/this-week-in-literary…	This Week in Literary History:…	img no alt	Add alt attribute to the image
https://lithub.com/on-the-systematic-ann…	On the Systematic Annihilation…	img no alt	Add alt attribute to the image
https://lithub.com/of-the-many-types-of-…	Of the Many Types of Roman Gla…	img no alt	Add alt attribute to the image
https://lithub.com/rasputin-fraud-mystic…	Rasputin: Fraud, Mystic, Woman…	img no alt	Add alt attribute to the image
https://lithub.com/god-bless-the-pill-me…	God Bless the Pill: Meet the D…	img no alt	Add alt attribute to the image
https://lithub.com/of-the-many-types-of-…	Of the Many Types of Roman Gla…	img no alt	Add alt attribute to the image
https://daily.jstor.org/how-america-raci…	On labor and the racializaton …	new tab	Add '(opens in new tab)' to text
https://www.theatlantic.com/magazine/202…	Attending Jeff Bezos’ “Cam…	new tab	Add '(opens in new tab)' to text
https://www.publicbooks.org/the-hypochon…	Some recent books about hypoch…	new tab	Add '(opens in new tab)' to text
https://www.threads.com/@literaryhub	(empty)	empty	Add link text or aria-label
https://www.tiktok.com/@lit.hub	(empty)	empty	Add link text or aria-label
https://www.instagram.com/literaryhub/	(empty)	empty	Add link text or aria-label
https://www.facebook.com/lithub	(empty)	empty	Add link text or aria-label
https://www.youtube.com/@Literary_Hub	(empty)	empty	Add link text or aria-label
https://bsky.app/profile/literaryhub.bsk…	(empty)	empty	Add link text or aria-label
https://mastodon.social/@literaryhub	(empty)	empty	Add link text or aria-label
https://www.tumblr.com/lithub	(empty)	empty	Add link text or aria-label
https://lithub.memberful.com/join	(empty)	empty	Add link text or aria-label
https://lithub.memberful.com/join	Support Lit Hub - Become A Mem…	new tab	Add '(opens in new tab)' to text
https://bookshop.org	Bookshop.org	new tab	Add '(opens in new tab)' to text
https://www.threads.com/@literaryhub	(empty)	empty	Add link text or aria-label
https://www.tiktok.com/@lit.hub	(empty)	empty	Add link text or aria-label
https://www.instagram.com/literaryhub/	(empty)	empty	Add link text or aria-label
https://www.facebook.com/lithub	(empty)	empty	Add link text or aria-label
https://www.youtube.com/@Literary_Hub	(empty)	empty	Add link text or aria-label
https://bsky.app/profile/literaryhub.bsk…	(empty)	empty	Add link text or aria-label
https://mastodon.social/@literaryhub	(empty)	empty	Add link text or aria-label
https://www.tumblr.com/lithub	(empty)	empty	Add link text or aria-label
<button>	(empty)	empty	Add button text or aria-label

199 links and buttons have descriptive text

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

https://www.threads.com/@literaryhub; https://www.tiktok.com/@lit.hub; https://www.instagram.com/literaryhub/; https://www.facebook.com/lithub; https://www.youtube.com/@Literary_Hub; https://bsky.app/profile/literaryhub.bsky.social; https://mastodon.social/@literaryhub; https://www.tumblr.com/lithub; a.icons (#190 on page); https://www.threads.com/@literaryhub (+16 more)

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

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

a[href="https://lithub.com/chief-librarian-edwin-b-maxwell-on-his-favorite-books-abou…"]; a[href="https://lithub.com/one-great-poem-to-read-today-carson-jordans-permiso/"]; a[href="https://lithub.com/meet-the-shortlisted-writers-for-the-2026-womens-prize-for…"]; a[href="https://lithub.com/why-a-group-of-writers-and-artists-is-boycotting-the-92nd-…"]; a[href="https://lithub.com/heres-the-shortlist-for-the-2026-carol-shields-prize-for-f…"]; a[href="https://lithub.com/one-great-poem-to-read-today-allen-ginsbergs-a-supermarket…"]; a[href="https://lithub.com/jayne-anne-phillips-xochitl-gonzalez-t-c-boyle-and-more-20…"]; a[href="https://lithub.com/2m-worth-of-stolen-rare-books-have-been-returned-to-the-wh…"]; a[href="https://lithub.com/one-great-poem-to-read-today-ada-limons-the-noisiness-of-s…"]; a[href="https://lithub.com/these-were-the-11-most-challenged-books-in-2025/"] (+33 more)

Why this matters

Image-only links with no alt are unidentifiable to screen-reader users — link's destination is invisible.

Source: WCAG 2.1 SC 2.4.4

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

https://literaryhub.myshopify.com/products/lit-hub-hat; https://daily.jstor.org/how-america-racialized-the-robot/; https://www.theatlantic.com/magazine/2026/05/billionaire-consequence-free-rea…; https://www.publicbooks.org/the-hypochondriacs-complaint/; https://lithub.memberful.com/join; https://bookshop.org

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

Icon-only buttons need an aria-label so screen readers can announce them.

button (#307 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

F

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

Soft 404: server returns HTTP 200 for non-existent pages

The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.

Got: Status: 200 for /beavercheck-404-test-d793pe

404 Page Quality ✗ Soft 404 (HTTP 200)

Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

F

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

F

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://lithub.com/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://lithub.com/manifest.json

Manifest contains invalid JSON.

D

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.

D

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 ✗

F

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

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

Back to Top

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

D

Lighthouse Accessibility Audits

Action

Score 67/100 — 9 failing, 16 passed

FIX

67

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

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.title-bar > div.title-bar-wrapper > div.title-bar-third > a.icons `div.title-bar > div.title-bar-wrapper > div.title-bar-third > a.icons`

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
Where the Music Had to Go: How Bob Dylan and the Beatles Changed Each Other--An… `div.flexslider > div.flex-viewport > ul.slides > li.clone`
Go Gentle `div.flexslider > div.flex-viewport > ul.slides > li.clone`
div.flexslider > div.flex-viewport > ul.slides > li.clone `div.flexslider > div.flex-viewport > ul.slides > li.clone`
div.flexslider > div.flex-viewport > ul.slides > li.clone `div.flexslider > div.flex-viewport > ul.slides > li.clone`

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.

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
You are outside the CCPA jurisdiction. `div.grid-container > div.cell > li#custom_ads-31 > div`

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
BY DANIEL HAHN `div.cell > div.featured-item > div.featured-item-story > h4`
BY CARISSA VÉLIZ `div.cell > div.featured-item > div.featured-item-story > h4`
BY JAYNE ANNE PHILLIPS `div.cell > div.featured-item > div.featured-item-story > h4`
BY MEGAN GARBER `div.grid-x > div.cell > div.story-content > h4`
BY CHRISTOPHER KONDRICH `div.grid-x > div.cell > div.story-content > h4`
BY EILEEN GARVIN `div.grid-x > div.cell > div.story-content > h4`
BY THE WRITERS INSTITUTE `div.grid-x > div.cell > div.story-content > h4`
BY BOB SPITZ `div.grid-x > div.cell > div.story-content > h4`
BY VALERIE FRIDLAND `div.grid-x > div.cell > div.story-content > h4`
BY JANE CIABATTARI `div.grid-x > div.cell > div.story-content > h4`
BY CRAIG FEHRMAN `div.grid-x > div.cell > div.story-content > h4`
BY BONNIE FRIEDMAN `div.grid-x > div.cell > div.story-content > h4`
BY QUINN SLOBODIAN AND BEN TARNOFF `div.grid-x > div.cell > div.story-content > h4`
BY JIM WINDOLF `div.grid-x > div.cell > div.story-content > h4`
BY GRACE SPULAK `div.grid-x > div.cell > div.story-content > h4`
BY LUKE GOEBEL `div.grid-x > div.cell > div.story-content > h4`
BY DIANA ARTERIAN `div.grid-x > div.cell > div.story-content > h4`
BY POLLY BARTON `div.grid-x > div.cell > div.story-content > h4`
BY LITERARY HUB `div.grid-x > div.cell > div.story-content > h4`
BY TAQWA AHMED ALWAWI `div.grid-x > div.cell > div.story-content > h4`
BY HARRY SIDEBOTTOM `div.grid-x > div.cell > div.story-content > h4`
BY ANTONY BEEVOR `div.grid-x > div.cell > div.story-content > h4`
BY SAMIRA K. MEHTA `div.grid-x > div.cell > div.story-content > h4`
BY HARRY SIDEBOTTOM `div.grid-x > div.cell > div.story-content > h4`

These are opportunities to improve keyboard navigation in your application.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.hub-home-container > div.hub-home-wrapper > div.hub-header-container > img `div.hub-home-container > div.hub-home-wrapper > div.hub-header-container > img`
ul.slides > li > a > img `ul.slides > li > a > img`
ul.slides > li > a > img `ul.slides > li > a > img`
ul.slides > li > a > img `ul.slides > li > a > img`
ul.slides > li > a > img `ul.slides > li > a > img`
ul.slides > li > a > img `ul.slides > li > a > img`
ul.slides > li > a > img `ul.slides > li > a > img`
ul.slides > li > a > img `ul.slides > li > a > img`
ul.slides > li > a > img `ul.slides > li > a > img`
ul.slides > li > a > img `ul.slides > li > a > img`
ul.slides > li > a > img `ul.slides > li > a > img`
ul.slides > li > a > img `ul.slides > li > a > img`
ul.slides > li > a > img `ul.slides > li > a > img`
div.story-content > div.story-img-container > a > img `div.story-content > div.story-img-container > a > img`
div.story-content > div.story-img-container > a > img `div.story-content > div.story-img-container > a > img`
div.story-content > div.story-img-container > a > img `div.story-content > div.story-img-container > a > img`
div.story-content > div.story-img-container > a > img `div.story-content > div.story-img-container > a > img`
div.story-content > div.story-img-container > a > img `div.story-content > div.story-img-container > a > img`
div.story-content > div.story-img-container > a > img `div.story-content > div.story-img-container > a > img`
ul.slides > li > a > img `ul.slides > li > a > img`
ul.slides > li > a > img `ul.slides > li > a > img`
ul.slides > li > a > img `ul.slides > li > a > img`
ul.slides > li.flex-active-slide > a > img `ul.slides > li.flex-active-slide > a > img`
ul.slides > li > a > img `ul.slides > li > a > img`
div.story-content > div.story-img-container > a > img `div.story-content > div.story-img-container > a > img`
div.story-content > div.story-img-container > a > img `div.story-content > div.story-img-container > a > img`
div.story-content > div.story-img-container > a > img `div.story-content > div.story-img-container > a > img`
div.story-content > div.story-img-container > a > img `div.story-content > div.story-img-container > a > img`
div.story-content > div.story-img-container > a > img `div.story-content > div.story-img-container > a > img`
div.story-content > div.story-img-container > a > img `div.story-content > div.story-img-container > a > img`
div.cell > div.sister-content > a > img.featured-image `div.cell > div.sister-content > a > img.featured-image`
div.cell > div.sister-content > a > img.featured-image `div.cell > div.sister-content > a > img.featured-image`
div.cell > div.sister-content > a > img.featured-image `div.cell > div.sister-content > a > img.featured-image`
div.story-content > div.story-img-container > a > img `div.story-content > div.story-img-container > a > img`
div.story-content > div.story-img-container > a > img `div.story-content > div.story-img-container > a > img`
div.story-content > div.story-img-container > a > img `div.story-content > div.story-img-container > a > img`
div.story-content > div.story-img-container > a > img `div.story-content > div.story-img-container > a > img`
div.story-content > div.story-img-container > a > img `div.story-content > div.story-img-container > a > img`
div.story-content > div.story-img-container > a > img `div.story-content > div.story-img-container > a > img`
div.story-content > div.story-img-container > a > img `div.story-content > div.story-img-container > a > img`
div.story-content > div.story-img-container > a > img `div.story-content > div.story-img-container > a > img`
div.story-content > div.story-img-container > a > img `div.story-content > div.story-img-container > a > img`
div.cell > div.sidebar_widget > li#lithub_daily_widget-7 > img `div.cell > div.sidebar_widget > li#lithub_daily_widget-7 > img`
ul.social_wrapper > li > a.external > img `ul.social_wrapper > li > a.external > img`
ul.social_wrapper > li > a.external > img `ul.social_wrapper > li > a.external > img`
ul.social_wrapper > li > a.external > img `ul.social_wrapper > li > a.external > img`
ul.social_wrapper > li > a.external > img `ul.social_wrapper > li > a.external > img`
ul.social_wrapper > li > a.external > img `ul.social_wrapper > li > a.external > img`
ul.social_wrapper > li > a.external > img `ul.social_wrapper > li > a.external > img`
ul.social_wrapper > li > a.external > img `ul.social_wrapper > li > a.external > img`
ul.social_wrapper > li > a.external > img `ul.social_wrapper > li > a.external > img`
ul.social_wrapper > li > a.external > img `ul.social_wrapper > li > a.external > img`
ul.social_wrapper > li > a.external > img `ul.social_wrapper > li > a.external > img`
ul.social_wrapper > li > a.external > img `ul.social_wrapper > li > a.external > img`
ul.social_wrapper > li > a.external > img `ul.social_wrapper > li > a.external > img`
ul.social_wrapper > li > a.external > img `ul.social_wrapper > li > a.external > img`
ul.social_wrapper > li > a.external > img `ul.social_wrapper > li > a.external > img`
ul.social_wrapper > li > a.external > img `ul.social_wrapper > li > a.external > img`
ul.social_wrapper > li > a.external > img `ul.social_wrapper > li > a.external > img`

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
li#lhp_social_widget-2 > ul.social_wrapper > li > a.external `li#lhp_social_widget-2 > ul.social_wrapper > li > a.external`
li#lhp_social_widget-2 > ul.social_wrapper > li > a.external `li#lhp_social_widget-2 > ul.social_wrapper > li > a.external`
li#lhp_social_widget-2 > ul.social_wrapper > li > a.external `li#lhp_social_widget-2 > ul.social_wrapper > li > a.external`
li#lhp_social_widget-2 > ul.social_wrapper > li > a.external `li#lhp_social_widget-2 > ul.social_wrapper > li > a.external`
li#lhp_social_widget-2 > ul.social_wrapper > li > a.external `li#lhp_social_widget-2 > ul.social_wrapper > li > a.external`
li#lhp_social_widget-2 > ul.social_wrapper > li > a.external `li#lhp_social_widget-2 > ul.social_wrapper > li > a.external`
li#lhp_social_widget-2 > ul.social_wrapper > li > a.external `li#lhp_social_widget-2 > ul.social_wrapper > li > a.external`
li#lhp_social_widget-2 > ul.social_wrapper > li > a.external `li#lhp_social_widget-2 > ul.social_wrapper > li > a.external`
div.cell > div.sidebar_widget > li#media_image-30 > a.external `div.cell > div.sidebar_widget > li#media_image-30 > a.external`
div.cell > ul.social_wrapper > li > a.external `div.cell > ul.social_wrapper > li > a.external`
div.cell > ul.social_wrapper > li > a.external `div.cell > ul.social_wrapper > li > a.external`
div.cell > ul.social_wrapper > li > a.external `div.cell > ul.social_wrapper > li > a.external`
div.cell > ul.social_wrapper > li > a.external `div.cell > ul.social_wrapper > li > a.external`
div.cell > ul.social_wrapper > li > a.external `div.cell > ul.social_wrapper > li > a.external`
div.cell > ul.social_wrapper > li > a.external `div.cell > ul.social_wrapper > li > a.external`
div.cell > ul.social_wrapper > li > a.external `div.cell > ul.social_wrapper > li > a.external`
div.cell > ul.social_wrapper > li > a.external `div.cell > ul.social_wrapper > li > a.external`

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.

Tables and lists

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
LIT HUB DAILY APRIL 22, 2026 On labor and the racializaton of robots Attending … `div.grid-container > div.cell > div.sidebar_widget > li#lithub_daily_widget-7`
Advertisement `div.grid-container > div.cell > div.sidebar_widget > li#custom_ads-32`
SUBSCRIBE TO THE LIT HUB DAILY For our latest stories, updates, and more. … `div.grid-container > div.cell > div.sidebar_widget > li#custom_ads-33`
FOLLOW US `div.grid-container > div.cell > div.sidebar_widget > li#lhp_social_widget-2`
Advertisement `div.grid-container > div.cell > div.sidebar_widget > li#custom_ads-34`
SUPPORT LIT HUB. `div.grid-container > div.cell > div.sidebar_widget > li#media_image-30`
Advertisement `div.grid-container > div.cell > div.sidebar_widget > li#custom_ads-35`
div.grid-container > div.cell > div.sidebar_widget > li#custom_ads-36 `div.grid-container > div.cell > div.sidebar_widget > li#custom_ads-36`
div.footer > div.grid-container > div.cell > li#text-2 `div.footer > div.grid-container > div.cell > li#text-2`
Literary Hub Created by Grove Atlantic and Electric Literature Masthead A… `div.footer > div.grid-container > div.cell > li#custom_html-2`
You are outside the CCPA jurisdiction. `div.footer > div.grid-container > div.cell > li#custom_ads-31`

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

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
1 `div.flexslider > ol.flex-control-nav > li > a`
2 `div.flexslider > ol.flex-control-nav > li > a`
3 `div.flexslider > ol.flex-control-nav > li > a`
4 `div.flexslider > ol.flex-control-nav > li > a.flex-active`
5 `div.flexslider > ol.flex-control-nav > li > a`
6 `div.flexslider > ol.flex-control-nav > li > a`
7 `div.flexslider > ol.flex-control-nav > li > a`
8 `div.flexslider > ol.flex-control-nav > li > a`
9 `div.flexslider > ol.flex-control-nav > li > a`
10 `div.flexslider > ol.flex-control-nav > li > a`
11 `div.flexslider > ol.flex-control-nav > li > a`
12 `div.flexslider > ol.flex-control-nav > li > a`
div.cell > ul.social_wrapper > li > a.external `div.cell > ul.social_wrapper > li > a.external`
div.cell > ul.social_wrapper > li > a.external `div.cell > ul.social_wrapper > li > a.external`
div.cell > ul.social_wrapper > li > a.external `div.cell > ul.social_wrapper > li > a.external`
div.cell > ul.social_wrapper > li > a.external `div.cell > ul.social_wrapper > li > a.external`
div.cell > ul.social_wrapper > li > a.external `div.cell > ul.social_wrapper > li > a.external`
div.cell > ul.social_wrapper > li > a.external `div.cell > ul.social_wrapper > li > a.external`
div.cell > ul.social_wrapper > li > a.external `div.cell > ul.social_wrapper > li > a.external`
div.cell > ul.social_wrapper > li > a.external `div.cell > ul.social_wrapper > li > a.external`

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

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-hidden="true"]` is not present on the document `<body>`

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●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

●Document has a `<title>` element

●`<frame>` or `<iframe>` elements have a title

●`<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>`).

●No element has a `[tabindex]` value greater than 0

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Deprecated ARIA roles were not used

○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

○`[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]`s are contained by their required parent element

○`[role]` values are valid

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

B

Form Accessibility

2 of 3 controls have issues

REVIEW

2 of 3 controls have issues

2 control(s) rely on placeholder only

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

Got: <input type="text" name="s" id="s">; <input type="text" name="s" id="s">

1 control(s) properly labeled

3 controls

1 labeled

2 placeholder only

0 unlabeled

Control	Type	Label	Method
#email_01K6WRN9H4PYY694E2KQYFHHDQ	email	Email	for/id
#s	text	(Search)	placeholder only
#s	text	(Search)	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

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

title Literary Hub

1.58:1

#000000

on

#2B3036

needs 4.5:1 (normal text)

16px · top of page (header area)

a Literary Hub

1.56:1

#000000

on

#2B2F34

needs 4.5:1 (normal text)

16px · top of page (header area)

a Craft and Criticism

4.47:1

#000000

on

#258448

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

a Literary Criticism

1.52:1

#000000

on

#292D32

needs 4.5:1 (normal text)

16px · top of page (header area)

a Craft and Advice

1.49:1

#000000

on

#282C30

needs 4.5:1 (normal text)

16px · above the fold

a In Conversation

1.46:1

#000000

on

#282A30

needs 4.5:1 (normal text)

16px · above the fold

a On Translation

1.43:1

#000000

on

#27282E

needs 4.5:1 (normal text)

16px · above the fold

a Fiction and Poetry

1.44:1

#000000

on

#26292D

needs 4.5:1 (normal text)

16px · above the fold

a Short Story

3.73:1

#000000

on

#67676B

needs 4.5:1 (normal text)

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

2 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	18.26:1	3.0:1	#000000	#EFEFEF	Pass
h2 Daily Fiction	18.26:1	3.0:1	#000000	#EFEFEF	Pass
h2 April 22, 2026	18.26:1	3.0:1	#000000	#EFEFEF	Pass
h2 Follow Us	18.26:1	3.0:1	#000000	#EFEFEF	Pass
h2 Support Lit Hub.	18.26:1	3.0:1	#000000	#EFEFEF	Pass
h2 Literary Hub	18.26:1	3.0:1	#000000	#EFEFEF	Pass
h3 News, Notes, Talk	18.26:1	3.0:1	#000000	#EFEFEF	Pass
title Literary Hub	1.58:1	4.5:1	#000000	#2B3036	Fail
a Literary Hub	1.56:1	4.5:1	#000000	#2B2F34	Fail
a Craft and Criticism	4.47:1	4.5:1	#000000	#258448	Fail
a Literary Criticism	1.52:1	4.5:1	#000000	#292D32	Fail
a Craft and Advice	1.49:1	4.5:1	#000000	#282C30	Fail
a In Conversation	1.46:1	4.5:1	#000000	#282A30	Fail
a On Translation	1.43:1	4.5:1	#000000	#27282E	Fail
a Fiction and Poetry	1.44:1	4.5:1	#000000	#26292D	Fail
a Short Story	3.73:1	4.5:1	#000000	#67676B	Fail
a From the Novel	11.83:1	4.5:1	#000000	#C3C2C3	Pass
a Poem	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a News and Culture	20.03:1	4.5:1	#000000	#FFF9ED	Pass
a History	20.03:1	4.5:1	#000000	#FFF9ED	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.