Skip to content
https://english-heritage.org.uk

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
39
GRADE
F
FIX
8
REVIEW
5
PASS
0
INFO
0
Checks
13
5 REVIEW 8 FIX
F
Alt Text Quality
Action
13 of 19 images have issues
FIX
13 of 19 images have issues
Critical::
13 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
6 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
5 decorative image(s) correctly marked
Info::
1 image(s) with good alt text
19 images 1 good alt text 5 decorative 13 missing
IssueCount
missing13 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
Form Accessibility
Action
31 of 35 controls have issues
FIX
31 of 35 controls have issues
Critical::
5 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="text" name="sl" id="goog-gt-votingInputSrcLang">; <input type="text" name="tl" id="goog-gt-votingInputTrgLang">; <input type="text" name="query" id="goog-gt-votingInputSrcText">; <input type="text" name="gtrans" id="goog-gt-votingInputTrgText">; <input type="text" name="vote" id="goog-gt-votingInputVote">
Warning::
26 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text">; <input type="search">; <input type="search">; <input type="search">; <input type="search">; <input type="search">; <input type="search">; <input type="search">; <input type="search">; <input type="search"> (+16 more)
Info::
4 control(s) properly labeled
35 controls
4 labeled
26 placeholder only
5 unlabeled
ControlTypeLabelMethod
#cookiescript_category_strictcheckboxStrictly necessaryfor/id
#cookiescript_category_performancecheckboxPerformancefor/id
#cookiescript_category_targetingcheckboxTargetingfor/id
#cookiescript_category_functionalitycheckboxFunctionalityfor/id
inputsearch(Search the site)placeholder only
inputsearch(Search the site)placeholder only
inputsearch(Search the site)placeholder only
inputsearch(Search the site)placeholder only
inputsearch(Search the site)placeholder only
inputsearch(Search the site)placeholder only
inputsearch(Search the site)placeholder only
inputsearch(Search the site)placeholder only
inputsearch(Search the site)placeholder only
inputsearch(Search the site)placeholder only
inputsearch(Search the site)placeholder only
inputsearch(Search the site)placeholder only
inputsearch(Search the site)placeholder only
inputsearch(Search the site)placeholder only
inputsearch(Search the site)placeholder only
inputsearch(Search the site)placeholder only
inputsearch(Search the site)placeholder only
inputsearch(Search the site)placeholder only
inputsearch(Search the site)placeholder only
inputsearch(Search the site)placeholder only
#mobile-search-inputsearch(Search the site)placeholder only
#searchinputtext(Type place name, postcode or region)placeholder only
inputtext(Search the site)placeholder only
inputsearch(Search the site)placeholder only
inputsearch(Search the site)placeholder only
inputsearch(Search the site)placeholder only
#goog-gt-votingInputVotetext(none)none
#goog-gt-votingInputSrcLangtext(none)none
#goog-gt-votingInputTrgLangtext(none)none
#goog-gt-votingInputSrcTexttext(none)none
#goog-gt-votingInputTrgTexttext(none)none

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

<input type="text" name="sl" id="goog-gt-votingInputSrcLang">; <input type="text" name="tl" id="goog-gt-votingInputTrgLang">; <input type="text" name="query" id="goog-gt-votingInputSrcText">; <input type="text" name="gtrans" id="goog-gt-votingInputTrgText">; <input type="text" name="vote" id="goog-gt-votingInputVote">

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

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

<input type="text">; <input type="search">; <input type="search">; <input type="search">; <input type="search">; <input type="search">; <input type="search">; <input type="search">; <input type="search">; <input type="search"> (+16 more)

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

F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
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-91m5cl
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
Info::
favicon.ico present at site root
Info::
No apple-touch-icon detected
iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.
✓ favicon.ico Present
✗ PNG Icons Missing
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://english-heritage.org.uk/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://english-heritage.org.uk/manifest.json

Manifest contains invalid JSON.

D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #d61130
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark ModePartial Dark Mode
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
No print-specific styles detected
When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.
Print Stylesheet No Print Styles
Print stylesheet Not found ✗Inline @media print Not detected ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
2 navigation landmark(s) detected
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 2 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
8 landmarks
REVIEW
8 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Warning::
Skip navigation link is missing (WCAG 2.4.1)
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
Page Structure — as a screen reader sees it
BANNER header NAV MAIN ASIDE CONTENTINFO footer

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

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

Why this matters

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

Learn more ▾

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

Source: WCAG 2.1 SC 2.4.1

B
Heading Hierarchy
18 headings, 1 skip(s)
REVIEW
18 headings, 1 skip(s)
Warning::
Multiple H1 headings (6 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 English Heritage
  • H1 Spring adventures await duplicate H1
  • H2 Membership
  • H2 May half-term
  • H2 History never looked so good
  • H1 Find a day out near you duplicate H1
  • H2 Learning and schools
  • H1 Give your heritage a future duplicate H1
  • H1 Keep in touch duplicate H1
  • H1 Latest news duplicate H1
  • H3 Ditch the green juice and shakes, have a ‘healthy’ cup of chocolate as Easter approaches skipped
  • H3 Roman rivers and rituals: Treasures in the mud
  • H3 Power and corruption: New display charts the rise and fall of the dynasty behind Audley End, England’s finest Jacobean home
  • H3 Visit
  • H3 Stay
  • H3 Support us
  • H3 Learn
  • H3 About us

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

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

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 17 fail WCAG AA
REVIEW

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

3 pass 17 fail WCAG AA 1 pass AA only
h1 Spring adventures await
2.02:1
#000000
on
#7C1B0C
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Find a day out near you
2.02:1
#000000
on
#7C1B0C
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Give your heritage a future
2.02:1
#000000
on
#7C1B0C
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Keep in touch
2.02:1
#000000
on
#7C1B0C
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Latest news
2.02:1
#000000
on
#7C1B0C
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Membership
2.02:1
#000000
on
#7C1B0C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 May half-term
2.02:1
#000000
on
#7C1B0C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 History never looked so good
2.02:1
#000000
on
#7C1B0C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Learning and schools
2.02:1
#000000
on
#7C1B0C
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Ditch the green juice and shakes, have a…
2.02:1
#000000
on
#7C1B0C
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Roman rivers and rituals: Treasures in t…
2.02:1
#000000
on
#7C1B0C
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Power and corruption: New display charts…
2.02:1
#000000
on
#7C1B0C
needs 3.0:1 (large text)
19px · bottom of viewport
a update Internet Explorer
1.20:1
#000000
on
#181A15
needs 4.5:1 (normal text)
16px · top of page (header area)
a ×
1.21:1
#000000
on
#191B17
needs 4.5:1 (normal text)
16px · above the fold
a English Heritage
1.21:1
#000000
on
#1A1B17
needs 4.5:1 (normal text)
16px · above the fold
a Basket
2.19:1
#000000
on
#4E433D
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
span Seleccionar idioma
3.31:1
#000000
on
#725A56
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)
ElementRatioRequiredFGBGResult
h1 Spring adventures aw…2.02:13.0:1
#000000
#7C1B0C
Fail
h1 Find a day out near …2.02:13.0:1
#000000
#7C1B0C
Fail
h1 Give your heritage a…2.02:13.0:1
#000000
#7C1B0C
Fail
h1 Keep in touch2.02:13.0:1
#000000
#7C1B0C
Fail
h1 Latest news2.02:13.0:1
#000000
#7C1B0C
Fail
h2 Membership2.02:13.0:1
#000000
#7C1B0C
Fail
h2 May half-term2.02:13.0:1
#000000
#7C1B0C
Fail
h2 History never looked…2.02:13.0:1
#000000
#7C1B0C
Fail
h2 Learning and schools2.02:13.0:1
#000000
#7C1B0C
Fail
h3 Ditch the green juic…2.02:13.0:1
#000000
#7C1B0C
Fail
h3 Roman rivers and rit…2.02:13.0:1
#000000
#7C1B0C
Fail
h3 Power and corruption…2.02:13.0:1
#000000
#7C1B0C
Fail
title English Heritage | E…19.09:14.5:1
#000000
#F4F4F4
Pass
div Your browser is out …9.63:14.5:1
#000000
#ACB0B5
Pass
div You are using an old…5.77:14.5:1
#000000
#868686
Pass
a update Internet Expl…1.20:14.5:1
#000000
#181A15
Fail
a ×1.21:14.5:1
#000000
#191B17
Fail
a English Heritage1.21:14.5:1
#000000
#1A1B17
Fail
a Basket2.19:14.5:1
#000000
#4E433D
Fail
span Seleccionar idioma3.31:14.5:1
#000000
#725A56
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.

C
Lighthouse Accessibility Audits
Action
Score 79/100 — 6 failing, 24 passed
REVIEW
79

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

When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.row > ul.column > li.mobnav > a.mobile-mega-menu-toggle div.row > ul.column > li.mobnav > a.mobile-mega-menu-toggle

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.

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
Ditch the green juice and shakes, have a ‘healthy’ cup of chocolate as Easter a… a.news-link > div#news-card1 > div.card-content-container > h3.card-title

These are opportunities to improve keyboard navigation in your application.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.js html.js

These are opportunities to improve the interpretation of your content by users in different locales.

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.block-container > div.slideshow-container > div.slide > img div.block-container > div.slideshow-container > div.slide > img
div.block-container > div.slideshow-container > div.slide > img div.block-container > div.slideshow-container > div.slide > img
div.slideshow-container > div.button-container > a.pause > img div.slideshow-container > div.button-container > a.pause > img
div.slideshow-content > p.primary > a > img div.slideshow-content > p.primary > a > img
div.three-story-cards > div.story-card-block > div.card-image-container > img.card-image div.three-story-cards > div.story-card-block > div.card-image-container > img.card-image
div.three-story-cards > div.story-card-block > div.card-image-container > img.card-image div.three-story-cards > div.story-card-block > div.card-image-container > img.card-image
div.three-story-cards > div.story-card-block > div.card-image-container > img.card-image div.three-story-cards > div.story-card-block > div.card-image-container > img.card-image
a.news-link > div#news-card1 > div.card-image-container > img.card-image a.news-link > div#news-card1 > div.card-image-container > img.card-image
a.news-link > div#news-card2 > div.card-image-container > img.card-image a.news-link > div#news-card2 > div.card-image-container > img.card-image
a.news-link > div#news-card3 > div.card-image-container > img.card-image a.news-link > div#news-card3 > div.card-image-container > img.card-image

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.row > ul.column > li.lng > a div.row > ul.column > li.lng > 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.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Form elements have associated labels
●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
●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.
●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
●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.
○`[accesskey]` values are unique
○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
○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 a valid value for its `[lang]` attribute
○`<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.
○`<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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback