Skip to content
https://lrb.co.uk

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
65
GRADE
D
FIX
3
REVIEW
6
PASS
4
INFO
0
Checks
13
4 PASS 6 REVIEW 3 FIX
D
404 Error Page
Action
HTTP 404, custom page
FIX
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
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::
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.
B
Landmark Structure
3 landmarks
REVIEW
3 landmarks
Info::
<main> landmark present
Warning::
No <nav> landmark found
Warning::
Skip navigation link is missing (WCAG 2.4.1)
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
Page Structure — as a screen reader sees it
BANNER header MAIN CONTENTINFO footer

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more ▾

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

B
Form Accessibility
2 of 4 controls have issues
REVIEW
2 of 4 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="button" id="searchSubmit">; <input type="button" id="searchSubmitSecondary">
Info::
2 control(s) properly labeled
4 controls
2 labeled
0 placeholder only
2 unlabeled
ControlTypeLabelMethod
#searchtextSearcharia-label
#searchSecondarytextSearcharia-label
#searchSubmitbutton(none)none
#searchSubmitSecondarybutton(none)none

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

<input type="button" id="searchSubmit">; <input type="button" id="searchSubmitSecondary">

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

B
Favicon & Branding
6 icon(s) detected
REVIEW
6 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
B
Web Manifest
Valid manifest
REVIEW
Valid manifest
Info::
Name present: LRB
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name LRB ✓192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓
Name LRB Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
Dark-specific theme-color detected
A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.
Info::
prefers-color-scheme CSS detected in inline styles
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark Mode✓ Dark Mode Supported
color-scheme meta Not set ✗Dark theme-color #ffffff ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

A
Heading Hierarchy
110 headings, 1 skip(s)
PASS
110 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H4 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 London Review of Books
  • H4 More search Options skipped
  • H4 Browse by Subject
  • H2 Locate Your Subscription Number
  • H2 Back to the Beach Boys
  • H3 Ian Penman
  • H2 Beirut, Now and Then
  • H3 Charles Glass
  • H2 Anglo-American Liaisons
  • H3 Azadeh Moaveni
  • H2 In Court and on the Road
  • H3 James Lasdun
  • H2 Gaza’s Yellow Line
  • H3 Eyal Weizman
  • H2 Ben Lerner’s ‘Transcription’
  • H3 Christian Lorentzen
  • H2 In the latest issue
  • H3 23 April 2026
  • H2 Sounds before Words
  • H3 Francis Gooding
  • H2 Gun Love
  • H3 Paul Theroux
  • H2 Ágota Kristóf’s Secrets
  • H3 Sarah Resnick
  • H2 ‘Rose of Nevada’
  • H3 Gaby Wood
  • H2 Women Paint Women
  • H3 Rosemary Hill
  • H2 ‘Indira is India’
  • H3 Pratinav Anil
  • H2 On James Schuyler
  • H3 Matthew Bevis
  • H2 Holbein and Henry James
  • H3 Elizabeth Goldring
  • H2 Judicial Activism
  • H3 Francis FitzGibbon
  • H2 From the blog
  • H3 ‘Nayatt School Redux’
  • H4 Anna Aslanyan
  • H3 A Kilo of Flour
  • H4 Hassan Ayman Herzallah
  • H3 Twee as Fuck
  • H4 Stephanie Burt
  • H3 City of Peace
  • H4 Rebekah Diski and Khem Rogaly
  • H3 After the Ceasefire
  • H4 Raha Nik-Andish
  • H3 Gamer’s Dilemma
  • H4 Arianne Shahvisi
  • H3 A Hundred Airstrikes in Ten Minutes
  • H4 Loubna El Amine
  • H3 In a League of Their Own
  • H4 Thomas Poole
  • H2 Podcasts & Videos
  • H2 The War in Lebanon
  • H3 Adam Shatz, Mohamad Bazzi and Joëlle Abi-Rached
  • H2 The Philosophy of ‘To the Lighthouse’
  • H3 Jonathan Rée and James Wood
  • H2 Insulin Wars
  • H3 Liam Shaw and Thomas Jones
  • H2 On Politics: Why you can’t change someone’s mind
  • H3 James Butler and Sarah Stein Lubrano
  • H2 Ordinary Abuse
  • H3 Susan Pedersen, Andrew O’Hagan and Thomas Jones
  • H2 On Politics: Keir Starmer’s Mess
  • H3 James Butler, Jeremy Gilbert and Sienna Rodgers
  • H2 What next in Iran?
  • H3 Esfandyar Batmanghelidj, Robert Malley and Adam Shatz
  • H2 Nature in Crisis: ‘Blue Machine’ by Helen Czerski
  • H3 Meehan Crist and Peter Godfrey-Smith
  • H2 Caravaggio’s Bodies
  • H3 Erin Maglaque and Thomas Jones
  • H2 Early Modern News
  • H3 John Gallagher and Thomas Jones
  • H2 From the Archive: ‘The War on Terrorism: Is There an Alternative?’
  • H2 On Politics: Mandelson and the Private Life of Power
  • H3 James Butler, Peter Geoghegan and Ethan Shone
  • H2 Nature in Crisis: ‘The Light Eaters’ by Zoë Schlanger
  • H3 Meehan Crist and Peter Godfrey-Smith
  • H2 Pluralism and the Modern Poet
  • H3 Seamus Perry
  • H2 Jessica Mitford’s Handbag
  • H3 Rosemary Hill and Thomas Jones
  • H2 Another Country
  • H3 Adam Shatz
  • H2 Nature in Crisis: ‘Silent Spring’ by Rachel Carson
  • H3 Meehan Crist and Peter Godfrey-Smith
  • H2 Episode 6: Aftershock ‘Live’
  • H3 Daniel Soar
  • H2 Narrative Poems: ‘Hero and Leander’ by Christopher Marlowe
  • H3 Seamus Perry and Mark Ford
  • H2 The Impossible Patient
  • H3 Amia Srinivasan
  • H2 Nature in Crisis: ‘Silent Spring’ by Rachel Carson
  • H3 Meehan Crist and Peter Godfrey-Smith
  • H2 Will the AI bubble burst?
  • H3 John Lanchester and Thomas Jones
  • H2 Albert Camus: A Short Life
  • H3 Jonathan Rée and James Wood
  • H2 Eric Hobsbawm: The Consolations of History
  • H2 Close Readings 2026
  • H2 LRB 45s: Poetry on vinyl
  • H3 Amy Larocca & Gaby Wood: How to Be Well
  • H3 Brian Dillon & Olivia Laing: Ambivalence
  • H3 Daniel Trilling & William Davies: If We Tolerate This
  • H3 Download the LRB app
  • H3 Sign up to our newsletter
  • H3 About
  • H3 Help
  • H3 Follow Us

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 4 images OK
PASS
All 4 images OK
Info::
3 decorative image(s) correctly marked
Info::
1 image(s) with good alt text
4 images 1 good alt text 3 decorative
All images have appropriate alt text.
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 London Review of Boo…18.84:13.0:1
#000000
#F4F3E9
Pass
h2 Locate Your Subscrip…18.84:13.0:1
#000000
#F4F3E9
Pass
h2 In the latest issue18.84:13.0:1
#000000
#F4F3E9
Pass
h2 Podcasts18.84:13.0:1
#000000
#F4F3E9
Pass
h2 Videos18.84:13.0:1
#000000
#F4F3E9
Pass
h3 23 April 202618.84:13.0:1
#000000
#F4F3E9
Pass
h3 and18.84:13.0:1
#000000
#F4F3E9
Pass
h3 and18.84:13.0:1
#000000
#F4F3E9
Pass
h3 and18.84:13.0:1
#000000
#F4F3E9
Pass
h3 and18.84:13.0:1
#000000
#F4F3E9
Pass
h3 and18.84:13.0:1
#000000
#F4F3E9
Pass
h3 and18.84:13.0:1
#000000
#F4F3E9
Pass
h3 and18.84:13.0:1
#000000
#F4F3E9
Pass
h3 and18.84:13.0:1
#000000
#F4F3E9
Pass
h3 and18.84:13.0:1
#000000
#F4F3E9
Pass
h3 and18.84:13.0:1
#000000
#F4F3E9
Pass
h3 and18.84:13.0:1
#000000
#F4F3E9
Pass
h3 and18.84:13.0:1
#000000
#F4F3E9
Pass
h3 and18.84:13.0:1
#000000
#F4F3E9
Pass
h3 and18.84:13.0:1
#000000
#F4F3E9
Pass

Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.

A+
Lighthouse Accessibility Audits
Score 97/100 — 1 failing, 26 passed
PASS
97

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.

ARIA

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
We use cookies to improve your experience on our website and to show you person… div#cmpbox

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.

○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
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●Links have a discernible name
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
○`[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
○Buttons have an accessible name
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○ARIA IDs are unique
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○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.
○`<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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback