Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 2 REVIEW 6 FIX

404 Error Page

Action

HTTP 404, bare page

FIX

HTTP 404, bare page

Correct 404 status code returned

Got: HTTP 404

Bare server default 404 page

The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.

404 Page Quality Default 404 Page

Status Code HTTP 404 ✓Page Title 404 Page not found ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

favicon.ico present at site root

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 Present

✓ 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 ✗

Link & Button Quality

1 issue(s) across 63 links and 2 buttons

REVIEW

1 issue(s) across 63 links and 2 buttons

1 link(s) with no accessible text

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

Got: /

6 link(s) open in new tab without warning

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

Got: https://imagesonline.bl.uk/; https://creativecommons.org/licenses/by/4.0/; https://twitter.com/britishlibrary/; https://www.facebook.com/britishlibrary/; https://www.instagram.com/britishlibrary/; https://www.tiktok.com/@britishlibrary

56 link(s) with descriptive text

63 links

1 empty

0 generic text

6 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/	(empty)	empty	Add link text or aria-label
https://imagesonline.bl.uk/	Collection images	new tab	Add '(opens in new tab)' to text
https://creativecommons.org/licenses/by/…	CC-BY	new tab	Add '(opens in new tab)' to text
https://twitter.com/britishlibrary/	x / Twitter	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/britishlibrary/	facebook / meta	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/britishlibrary…	Instagram	new tab	Add '(opens in new tab)' to text
https://www.tiktok.com/@britishlibrary	TikTok	new tab	Add '(opens in new tab)' to text

58 links and buttons have descriptive text

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

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

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

https://imagesonline.bl.uk/; https://creativecommons.org/licenses/by/4.0/; https://twitter.com/britishlibrary/; https://www.facebook.com/britishlibrary/; https://www.instagram.com/britishlibrary/; https://www.tiktok.com/@britishlibrary

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

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

REVIEW

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

20 pass 11 pass AA only

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Welcome to the Briti…	6.75:1	3.0:1	#000000	#93928F	Pass
h2 What do you want to …	6.75:1	3.0:1	#000000	#93928F	Pass
h2 Everything for	6.75:1	3.0:1	#000000	#93928F	Pass
h2 Events and exhibitio…	6.75:1	3.0:1	#000000	#93928F	Pass
h2 Latest updates	6.75:1	3.0:1	#000000	#93928F	Pass
h3 Updated opening hour…	6.75:1	3.0:1	#000000	#93928F	Pass
h3 Electronic legal dep…	6.75:1	3.0:1	#000000	#93928F	Pass
h3 We're a charity	6.75:1	3.0:1	#000000	#93928F	Pass
h3 Contact us	6.75:1	3.0:1	#000000	#93928F	Pass
a Skip to content	6.75:1	4.5:1	#000000	#93928F	Pass
span Collection	6.75:1	4.5:1	#000000	#93928F	Pass
span What's on	6.75:1	4.5:1	#000000	#93928F	Pass
span Visit	6.75:1	4.5:1	#000000	#93928F	Pass
span Stories	6.75:1	4.5:1	#000000	#93928F	Pass
span About us	6.75:1	4.5:1	#000000	#93928F	Pass
span Contact and help	6.75:1	4.5:1	#000000	#93928F	Pass
span Opening hours	6.75:1	4.5:1	#000000	#93928F	Pass
span Research	6.75:1	4.5:1	#000000	#93928F	Pass
span Business	6.75:1	4.5:1	#000000	#93928F	Pass
span Schools	6.75:1	4.5:1	#000000	#93928F	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.

Landmark Structure

2 landmarks

PASS

2 landmarks

<main> landmark present

No <nav> landmark found

No banner (header) landmark

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Heading Hierarchy

13 headings

PASS

13 headings

Single H1 present

H6 Everything for
H1 Welcome to the British Library
H2 What do you want to do today?
H2 Everything for
H2 Events and exhibitions
H3 Fairy Tales
H3 Treasures of the British Library
H3 All events
H2 Latest updates
H3 Updated opening hours this week due to tube strikes
H3 Electronic legal deposit material available
H3 We're a charity
H3 Contact us

A+

Alt Text Quality

All 7 images OK

PASS

All 7 images OK

7 image(s) with good alt text

7 images 7 good alt text

All images have appropriate alt text.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

A+

Lighthouse Accessibility Audits

Score 100/100 — 0 failing, 28 passed

PASS

100

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.

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

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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

○`[accesskey]` values are unique

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

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

○`[lang]` attributes have a valid value

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