Skip to content
https://manutd.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
64
GRADE
D
FIX
4
REVIEW
6
PASS
3
INFO
0
Checks
13
3 PASS 6 REVIEW 4 FIX
D
Landmark Structure
Action
4 landmarks
FIX
4 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
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 (missing!) CONTENTINFO footer

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

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: #db1d24
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
Alt Text Quality
2 of 31 images have issues
REVIEW
2 of 31 images have issues
Critical::
2 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
11 decorative image(s) correctly marked
Info::
18 image(s) with good alt text
31 images 18 good alt text 11 decorative 2 missing
IssueCount
missing2 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

B
404 Error Page
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 ✓Page Title Error 404 | Page Not Found | Manchester United ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
B
Favicon & Branding
5 icon(s) detected
REVIEW
5 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
PWA-ready
REVIEW
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: Manchester United
Info::
192x192 icon present
Info::
Display mode: standalone
PWA Install Criteria ✓ Installable
Name Manchester United ✓192×192 icon ✓512×512 icon ✗Start URL / ✓Display Mode standalone ✓
Name Manchester United Display Mode standalone Icons 1 icon(s)
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 18 fail WCAG AA
REVIEW

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

2 pass 18 fail WCAG AA
h1 Home Page
1.21:1
#000000
on
#1A1A1A
needs 3.0:1 (large text)
32px · bottom of viewport
h2 TODAY ON MANUTD.COM
1.21:1
#000000
on
#1A1A1A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Fletcher: 'United is all I know'
1.21:1
#000000
on
#1A1A1A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Thwaites thrilled with first-team call
1.21:1
#000000
on
#1A1A1A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 The archive is open
1.21:1
#000000
on
#1A1A1A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Wilcox receives The FA's red legacy cap
1.21:1
#000000
on
#1A1A1A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 What is Fletcher's coaching philosophy?
1.21:1
#000000
on
#1A1A1A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Brentford (H): TV info, team news, form …
1.21:1
#000000
on
#1A1A1A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Men's Videos
1.21:1
#000000
on
#1A1A1A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 The Barbershop: Episode two
1.21:1
#000000
on
#1A1A1A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 You’ll love Fletcher’s United mindse…
1.21:1
#000000
on
#1A1A1A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Robin's reaction to 'unique' hat-trick
1.21:1
#000000
on
#1A1A1A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 adidas and United launch Bringback colle…
1.21:1
#000000
on
#1A1A1A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 IN CASE YOU MISSED IT
1.21:1
#000000
on
#1A1A1A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Why a local hero was at Carrington
1.21:1
#000000
on
#1A1A1A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 'I've still got the original!'
1.21:1
#000000
on
#1A1A1A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Classic shots of the 'snowflake' kit
1.21:1
#000000
on
#1A1A1A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Nostalgia hits different
1.21:1
#000000
on
#1A1A1A
needs 3.0:1 (large text)
24px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Home Page1.21:13.0:1
#000000
#1A1A1A
Fail
h2 COOKIES20.87:13.0:1
#000000
#FFFEFF
Pass
h2 Would you like to su…20.87:13.0:1
#000000
#FFFEFF
Pass
h2 TODAY ON MANUTD.COM1.21:13.0:1
#000000
#1A1A1A
Fail
h2 Fletcher: 'United is…1.21:13.0:1
#000000
#1A1A1A
Fail
h2 Thwaites thrilled wi…1.21:13.0:1
#000000
#1A1A1A
Fail
h2 The archive is open1.21:13.0:1
#000000
#1A1A1A
Fail
h2 Wilcox receives The …1.21:13.0:1
#000000
#1A1A1A
Fail
h2 What is Fletcher's c…1.21:13.0:1
#000000
#1A1A1A
Fail
h2 Brentford (H): TV in…1.21:13.0:1
#000000
#1A1A1A
Fail
h2 Men's Videos1.21:13.0:1
#000000
#1A1A1A
Fail
h2 The Barbershop: Epis…1.21:13.0:1
#000000
#1A1A1A
Fail
h2 You’ll love Fletch…1.21:13.0:1
#000000
#1A1A1A
Fail
h2 Robin's reaction to …1.21:13.0:1
#000000
#1A1A1A
Fail
h2 adidas and United la…1.21:13.0:1
#000000
#1A1A1A
Fail
h2 IN CASE YOU MISSED I…1.21:13.0:1
#000000
#1A1A1A
Fail
h2 Why a local hero was…1.21:13.0:1
#000000
#1A1A1A
Fail
h2 'I've still got the …1.21:13.0:1
#000000
#1A1A1A
Fail
h2 Classic shots of the…1.21:13.0:1
#000000
#1A1A1A
Fail
h2 Nostalgia hits diffe…1.21:13.0:1
#000000
#1A1A1A
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.

A+
Heading Hierarchy
38 headings
PASS
38 headings
Info::
Single H1 present
  • H2 COOKIES
  • H2 Would you like to subscribe to breaking news notifications?
  • H1 Home Page
  • H2 TODAY ON MANUTD.COM
  • H2 Fletcher: 'United is all I know'
  • H2 Thwaites thrilled with first-team call
  • H2 The archive is open
  • H2 Wilcox receives The FA's red legacy cap
  • H2 What is Fletcher's coaching philosophy?
  • H2 Brentford (H): TV info, team news, form guides
  • H2 Men's VideosFind more videosClick to see more content
  • H2 Men's Videos Find more videosClick to see more content
  • H2 The Barbershop: Episode two
  • H2 You’ll love Fletcher’s United mindset!
  • H2 Robin's reaction to 'unique' hat-trick
  • H2 adidas and United launch Bringback collection
  • H2 IN CASE YOU MISSED IT
  • H2 Why a local hero was at Carrington
  • H2 'I've still got the original!'
  • H2 Classic shots of the 'snowflake' kit
  • H2 Nostalgia hits different adcard
  • H2 Inside Carrington adcard
  • H2 Snapdragon RED4LIFE collection adcard
  • H2 The Barbershop: Episode two
  • H2 UNITED WOMEN
  • H2 When are United Women back in action?
  • H2 Last home game of the season adcard
  • H2 Academy VideosFind more videosClick to see more content
  • H2 Academy Videos Find more videosClick to see more content
  • H2 U18s final highlights: Crystal Palace v United
  • H2 Noah Ajayi bags the opener at Palace
  • H2 Young Reds' eyes on the prize
  • H2 UNITED ACADEMY
  • H2 U18s final preview: Palace v United
  • H2 Under-21s' play-off fixture details
  • H2 UNITED STORE
  • H2 MatchesAll MatchesClick to see All Matches
  • H2 Inside Carrington: Da Silva twins
A+
Form Accessibility
All 1 controls labeled
PASS
All 1 controls labeled
Info::
1 control(s) properly labeled
1 controls
1 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#inptextSearch Edit boxaria-label
A
Lighthouse Accessibility Audits
Score 94/100 — 2 failing, 29 passed
PASS
94

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
Would you like to subscribe to breaking news notifications? We’ll send officia… body#siteCorePage > div#root > div.custom-popup

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.

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
SHOP HERE div.mu-item__info > a > span.dfp-ads__cta > span.dfp-ads-link
WATCH EVERY EPISODE div.mu-item__info > a > span.dfp-ads__cta > span.dfp-ads-link
AVAILABLE NOW div.mu-item__info > a > span.dfp-ads__cta > span.dfp-ads-link

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
●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
●`[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
●`[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
●`[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
●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.
●Elements with visible text labels have matching accessible names.
○`[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.
○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