Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

4 PASS 5 REVIEW 4 FIX

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 ✗

Heading Hierarchy

36 headings, 1 skip(s)

REVIEW

36 headings, 1 skip(s)

Multiple H1 headings (3 found)

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

Heading level skipped: H2 → H5 (missing H3)

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

1 empty heading(s)

Empty headings appear in the document outline but provide no information.

H2 Main menu
H5 Stories skipped
H5 Tate Kids
H3 Try searching for...
H3 DON'T MISS
H2 Hurvin Anderson
H2 Tracey Emin: A Second Life
H1 Nigerian Modernism
H2 Exhibitions
H2 Hurvin Anderson
H2 Tracey Emin: A Second Life
H2 James McNeill Whistler
H2 Aleksandra Kasuba: Shelters for the Senses
H2 Galleries
H2 Tate Britain
H2 Tate Modern
H2 Tate Liverpool + RIBA North
H2 Tate St Ives
H2 Support us
H2 Buy books, prints and more
H2 Donate to Tate
H1 TATE MEMBERS duplicate H1
H2 Read, watch, listen
H2 Stories
H2 Tate Etc.
H2 Play games, make art and explore artists
H1 Delve into Centuries of art duplicate H1
H2 Shop
H2 Books
H2 Gifts
H2 Prints
H3 (empty)
H2 Join in
H2 Sign up to emails
H2 About
H2 Support

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

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

Alt Text Quality

Action

3 of 31 images have issues

REVIEW

3 of 31 images have issues

3 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

1 image(s) with alt text over 125 characters

9 decorative image(s) correctly marked

18 image(s) with good alt text

31 images 18 good alt text 9 decorative 3 missing

Issue	Count
missing	3 image(s)
too long	1 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

Link & Button Quality

101 links, 11 buttons — all OK

REVIEW

101 links, 11 buttons — all OK

6 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="/whats-on/tate-britain/hurvin-anderson"]; a[href="/whats-on/tate-modern/tracey-emin"]; a[href="https://www.tate.org.uk/whats-on/tate-britain/hurvin-anderson"]; a[href="https://www.tate.org.uk/whats-on/tate-britain/whistler"]; a[href="https://www.tate.org.uk/whats-on/tate-st-ives/aleksandra-kasuba"]; a[href="/tate-etc"]

95 link(s) with descriptive text

101 links

0 empty

0 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/whats-on/tate-britain/hurvin-anderson	Hurvin Anderson	img no alt	Add alt attribute to the image
/whats-on/tate-modern/tracey-emin	Tracey Emin: A Second Life	img no alt	Add alt attribute to the image
https://www.tate.org.uk/whats-on/tate-br…	Hurvin Anderson	img no alt	Add alt attribute to the image
https://www.tate.org.uk/whats-on/tate-br…	James McNeill Whistler	img no alt	Add alt attribute to the image
https://www.tate.org.uk/whats-on/tate-st…	Aleksandra Kasuba	img no alt	Add alt attribute to the image
/tate-etc	Tate Etc.	img no alt	Add alt attribute to the image

106 links and buttons have descriptive text

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

a[href="/whats-on/tate-britain/hurvin-anderson"]; a[href="/whats-on/tate-modern/tracey-emin"]; a[href="https://www.tate.org.uk/whats-on/tate-britain/hurvin-anderson"]; a[href="https://www.tate.org.uk/whats-on/tate-britain/whistler"]; a[href="https://www.tate.org.uk/whats-on/tate-st-ives/aleksandra-kasuba"]; a[href="/tate-etc"]

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

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

404 Page Quality ✓ Custom 404 Page

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

Navigation UX

Action

3 navigation pattern(s)

REVIEW

3 navigation pattern(s)

Search functionality detected

Got: role-search

Skip navigation link detected

Back-to-top link detected

1 navigation landmark(s) detected

Hamburger menu detected (responsive design)

Breadcrumbs

Search role='search' landmark

Skip Link Skip link detected

Labeled Navigation 1 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

5 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.

A+

Landmark Structure

8 landmarks

PASS

8 landmarks

<main> landmark present

1 <nav> landmark(s) found

Skip navigation link present

Search landmark present

Page Structure — as a screen reader sees it

Form Accessibility

1 of 2 controls have issues

PASS

1 of 2 controls have issues

1 control(s) without accessible label

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

Got: <textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">

1 control(s) properly labeled

2 controls

1 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#email	email	Subscribe to email newsletter	aria-label
#g-recaptcha-response-100000	textarea	(none)	none

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

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

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)

Element	Ratio	Required	FG	BG	Result
h1 Nigerian Modernism	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 TATE MEMBERS	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 Delve into Centuries…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Main menu	8.29:1	3.0:1	#000000	#D8953D	Pass
h2 Exhibitions	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Galleries	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Support us	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Read, watch, listen	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Shop	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Join in	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Sign up to emails	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 About	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Support	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Try searching for...	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 DON'T MISS	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Tate	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Skip navigation	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Back to menu	8.18:1	4.5:1	#000000	#D79439	Pass
a What's On	8.04:1	4.5:1	#000000	#D6923C	Pass
a Visit	8.19:1	4.5:1	#000000	#D7943C	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 100/100 — 1 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.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
EXHIBITION Hurvin Anderson Experience the intensely colourful work of British … `div.slick-slide > div > div.card > a`
Tate Britain Free admission Open today 10.00–18.00 `div > div.card-list > div.card > a`
Tate Modern Free admission Open today 10.00–18.00 `div > div.card-list > div.card > a`
Tate Liverpool + RIBA North Free admission Open today 10.00–17.50 `div > div.card-list > div.card > a`
Tate St Ives Ticket or membership card required Open today 10.00–17.20 `div > div.card-list > div.card > a`
Buy books, prints and more Shopping with Tate helps supports our galleries `div > div.card-list > div.card > a`
Donate to Tate Your donation could provide art materials for young people or h… `div > div.card-list > div.card > a`
Stories Watch videos, listen to audio and read articles about art and artists `div.slick-slide > div > div.card > a`
Books Discover our titles on art history, artists, and our award-winning child… `div > div.card-list > div.card > a`
Gifts Shop art-inspired gifts for all ages and tastes `div > div.card-list > div.card > a`
Prints Browse from over 1,000 artworks from Tate's collection, to enjoy your f… `div > div.card-list > div.card > a`

○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

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

●Identical links have the same purpose.

○`[accesskey]` values are unique

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

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

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