Skip to content
https://www.premierleague.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
58
GRADE
D
FIX
4
REVIEW
7
PASS
2
INFO
0
Checks
13
2 PASS 7 REVIEW 4 FIX
D
Web Manifest
Action
Not found
FIX
Not found
Info::
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.

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::
Hamburger menu detected (responsive design)
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)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
15 landmarks
REVIEW
15 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 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

C
Heading Hierarchy
Action
22 headings, 1 skip(s)
REVIEW
22 headings, 1 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H2 Watch The Archive
  • H2 Iconic Archive Moments
  • H2 From The Clubs
  • H2 Trending - From the Clubs
  • H2 News & Features
  • H2 Games, Quizzes & Polls
  • H2 Who makes your Team of the Season so far? 🌟
  • H2 Unmissable 25/26 Moments 🔥
  • H2 Latest Videos
  • H2 Fantasy Premier League
  • H2 More than a Game
  • H2 Most-viewed video
  • H2 Premier League
  • H4 Premier League Companion, your personalised AI assistant.Premier League Companion your personalised AI assistant. skipped
  • H2 Listen live
  • H2 (empty)
  • H3 Manage Consent Preferences
  • H4 Essential Cookies
  • H4 Performance Cookies
  • H4 Functional Cookies
  • H4 Targeting Cookies
  • H3 Cookie List

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

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

C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
C
Favicon & Branding
Action
14 icon(s) detected
REVIEW
14 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
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 Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

B
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 4 pass AA only
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Watch The Archive4.84:13.0:1
#000000
#7A797A
Pass
h2 Iconic Archive Momen…4.84:13.0:1
#000000
#7A797A
Pass
h2 From The Clubs4.84:13.0:1
#000000
#7A797A
Pass
h2 Trending - From the …4.84:13.0:1
#000000
#7A797A
Pass
h2 News & Features4.84:13.0:1
#000000
#7A797A
Pass
h2 Games, Quizzes & Pol…4.84:13.0:1
#000000
#7A797A
Pass
h2 Who makes your Team …4.84:13.0:1
#000000
#7A797A
Pass
h2 Unmissable 25/26 Mom…4.84:13.0:1
#000000
#7A797A
Pass
h2 Latest Videos4.84:13.0:1
#000000
#7A797A
Pass
h2 Fantasy Premier Leag…4.84:13.0:1
#000000
#7A797A
Pass
h2 More than a Game4.84:13.0:1
#000000
#7A797A
Pass
h2 Most-viewed video4.84:13.0:1
#000000
#7A797A
Pass
h2 Premier League4.84:13.0:1
#000000
#7A797A
Pass
h2 Listen live4.84:13.0:1
#000000
#7A797A
Pass
h3 Manage Consent Prefe…4.84:13.0:1
#000000
#7A797A
Pass
h3 Cookie List4.84:13.0:1
#000000
#7A797A
Pass
title Premier League Footb…5.05:14.5:1
#000000
#7D7C7D
Pass
button Skip to main content5.05:14.5:1
#000000
#7D7C7D
Pass
a Premier League5.05:14.5:1
#000000
#7D7C7D
Pass
a Shop5.05:14.5:1
#000000
#7D7C7D
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.

C
Lighthouse Accessibility Audits
Action
Score 76/100 — 8 failing, 22 passed
REVIEW
76

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

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Modern Slavery Statement Equality, Diversity and Inclusion Standard Terms of Us… body.js-lazy-load-images > footer.main-footer > div.footer-corporate > ul.footer-corporate__menu

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Modern Slavery Statement div.footer-corporate > ul.footer-corporate__menu > li.footer-corporate__item > a.footer-corporate__link
Equality, Diversity and Inclusion Standard div.footer-corporate > ul.footer-corporate__menu > li.footer-corporate__item > a.footer-corporate__link
Terms of Use div.footer-corporate > ul.footer-corporate__menu > li.footer-corporate__item > a.footer-corporate__link
Policies div.footer-corporate > ul.footer-corporate__menu > li.footer-corporate__item > a.footer-corporate__link
Cookie Policy div.footer-corporate > ul.footer-corporate__menu > li.footer-corporate__item > a.footer-corporate__link
Contact Us div.footer-corporate > ul.footer-corporate__menu > li.footer-corporate__item > a.footer-corporate__link
Appearance div.footer-corporate > ul.footer-corporate__menu > li.footer-corporate__item > a.footer-corporate__link
Back To Top div.footer-corporate > ul.footer-corporate__menu > li.footer-corporate__item > a.footer-corporate__link

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Previous slide div.content-rail__container > header.content-rail-header > div.content-rail-header__navigation > button.content-rail-header__nav-button
Next slide div.content-rail__container > header.content-rail-header > div.content-rail-header__navigation > button.content-rail-header__nav-button
Previous slide div.content-rail__container > header.content-rail-header > div.content-rail-header__navigation > button.content-rail-header__nav-button
Next slide div.content-rail__container > header.content-rail-header > div.content-rail-header__navigation > button.content-rail-header__nav-button
Previous slide div.content-rail__container > header.content-rail-header > div.content-rail-header__navigation > button.content-rail-header__nav-button
Next slide div.content-rail__container > header.content-rail-header > div.content-rail-header__navigation > button.content-rail-header__nav-button

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
Premier League Companion your personalised AI assistant. div.copilot__wrapper > div.copilot__container > div.copilot__header-container > h4.copilot__title

These are opportunities to improve keyboard navigation in your application.

Names and labels

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.page-wrapper > div.default-template > div.image-promo > a.image-promo__link div.page-wrapper > div.default-template > div.image-promo > a.image-promo__link
div.page-wrapper > div.default-template > div.image-promo > a.image-promo__link div.page-wrapper > div.default-template > div.image-promo > a.image-promo__link
div.page-wrapper > div.default-template > div.image-promo > a.image-promo__link div.page-wrapper > div.default-template > div.image-promo > a.image-promo__link

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
Modern Slavery Statement footer.main-footer > div.footer-corporate > ul.footer-corporate__menu > li.footer-corporate__item
Equality, Diversity and Inclusion Standard footer.main-footer > div.footer-corporate > ul.footer-corporate__menu > li.footer-corporate__item
Terms of Use footer.main-footer > div.footer-corporate > ul.footer-corporate__menu > li.footer-corporate__item
Policies footer.main-footer > div.footer-corporate > ul.footer-corporate__menu > li.footer-corporate__item
Cookie Policy footer.main-footer > div.footer-corporate > ul.footer-corporate__menu > li.footer-corporate__item
Manage Cookies footer.main-footer > div.footer-corporate > ul.footer-corporate__menu > li.footer-corporate__item
Contact Us footer.main-footer > div.footer-corporate > ul.footer-corporate__menu > li.footer-corporate__item
Appearance footer.main-footer > div.footer-corporate > ul.footer-corporate__menu > li.footer-corporate__item
Back To Top footer.main-footer > div.footer-corporate > ul.footer-corporate__menu > li.footer-corporate__item

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
Modern Slavery Statement div.footer-corporate > ul.footer-corporate__menu > li.footer-corporate__item > a.footer-corporate__link
Equality, Diversity and Inclusion Standard div.footer-corporate > ul.footer-corporate__menu > li.footer-corporate__item > a.footer-corporate__link
Terms of Use div.footer-corporate > ul.footer-corporate__menu > li.footer-corporate__item > a.footer-corporate__link
Policies div.footer-corporate > ul.footer-corporate__menu > li.footer-corporate__item > a.footer-corporate__link
Cookie Policy div.footer-corporate > ul.footer-corporate__menu > li.footer-corporate__item > a.footer-corporate__link
Contact Us div.footer-corporate > ul.footer-corporate__menu > li.footer-corporate__item > a.footer-corporate__link
Appearance div.footer-corporate > ul.footer-corporate__menu > li.footer-corporate__item > a.footer-corporate__link

These items highlight common accessibility best practices.

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
Type your question here div.copilot > div.copilot__wrapper > div.copilot__container > button.copilot__open-prompt-button
○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 are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●`button`, `link`, and `menuitem` elements have accessible names
●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.
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●No element has a `[tabindex]` value greater than 0
●Document has a main landmark.
●Deprecated ARIA roles were not used
○`[accesskey]` values are unique
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○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
○Form elements have associated labels
○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.
○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.
A
Alt Text Quality
All 219 images OK
PASS
All 219 images OK
Info::
5 image(s) with alt text over 125 characters
Info::
214 image(s) with good alt text
219 images 214 good alt text
IssueCount
too long5 image(s)
A+
Form Accessibility
All 8 controls labeled
PASS
All 8 controls labeled
Info::
8 control(s) properly labeled
8 controls
8 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#ot-group-id-C0002checkboxPerformance Cookiesfor/id
#ot-group-id-C0003checkboxFunctional Cookiesfor/id
#ot-group-id-C0004checkboxTargeting Cookiesfor/id
#vendor-search-handlertextCookie list searcharia-label
#chkbox-idcheckboxcheckbox labelfor/id
#select-all-hosts-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-leg-handlercheckboxcheckbox labelfor/id
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback