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 4 REVIEW 5 FIX

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

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 Missing

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

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

4 navigation landmark(s) detected

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 4 <nav> element(s)

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.

Landmark Structure

6 landmarks

REVIEW

6 landmarks

<main> landmark present

4 <nav> landmark(s) found

4 of 4 <nav> elements are unlabeled

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

No banner (header) landmark

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

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

Heading Hierarchy

7 headings

REVIEW

7 headings

No H1 heading found

Every page should have one H1 that describes the page content.

H2 Latest on Empire
H2 Latest Movies
H2 Latest reviews
H2 Latest features
H2 Latest TV Series
H2 Latest Games
H2 Latest hardware

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

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

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

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

Color Contrast (Screenshot)

Action

20 text elements analyzed, 10 fail WCAG AA

REVIEW

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

10 pass 10 fail WCAG AA

h2 Latest on Empire

1.01:1

#000000

#020100

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Latest Movies

1.01:1

#000000

#020100

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Latest reviews

1.01:1

#000000

#020100

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Latest features

1.01:1

#000000

#020100

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Latest TV Series

1.01:1

#000000

#020100

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Latest Games

1.01:1

#000000

#020100

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Latest hardware

1.01:1

#000000

#020100

needs 3.0:1 (large text)

24px · bottom of viewport

title Empire - Movies, TV Shows & Gaming | Fil…

3.00:1

#000000

#595959

needs 4.5:1 (normal text)

16px · top of page (header area)

a Movies

3.00:1

#000000

#595959

needs 4.5:1 (normal text)

16px · top of page (header area)

a Reviews

3.00:1

#000000

#595959

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Latest on Empire	1.01:1	3.0:1	#000000	#020100	Fail
h2 Latest Movies	1.01:1	3.0:1	#000000	#020100	Fail
h2 Latest reviews	1.01:1	3.0:1	#000000	#020100	Fail
h2 Latest features	1.01:1	3.0:1	#000000	#020100	Fail
h2 Latest TV Series	1.01:1	3.0:1	#000000	#020100	Fail
h2 Latest Games	1.01:1	3.0:1	#000000	#020100	Fail
h2 Latest hardware	1.01:1	3.0:1	#000000	#020100	Fail
title Empire - Movies, TV …	3.00:1	4.5:1	#000000	#595959	Fail
a Movies	3.00:1	4.5:1	#000000	#595959	Fail
a Reviews	3.00:1	4.5:1	#000000	#595959	Fail
a News	7.01:1	4.5:1	#000000	#959595	Pass
a Features	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Gaming	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Podcasts	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Empire VIP	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Empire Magazine	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Subscribe	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Manage My Subscripti…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Newsletter	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Michael (2026)	21.00:1	4.5:1	#000000	#FFFFFF	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+

Alt Text Quality

All 61 images OK

PASS

All 61 images OK

2 image(s) with alt text over 125 characters

59 image(s) with good alt text

61 images 59 good alt text

Issue	Count
too long	2 image(s)

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

Link & Button Quality

221 links, 0 buttons — all OK

PASS

221 links, 0 buttons — all OK

4 link(s) open in new tab without warning

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

Got: https://account.greatmagazines.co.uk?utm_source=empireonline.com&utm_medium=r…; //www.facebook.com/empiremagazine; //twitter.com/empiremagazine; //www.pinterest.com/empiremagazine/

217 link(s) with descriptive text

221 links

0 empty

0 generic text

4 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://account.greatmagazines.co.uk?utm…	Manage My Subscription	new tab	Add '(opens in new tab)' to text
//www.facebook.com/empiremagazine	Facebook	new tab	Add '(opens in new tab)' to text
//twitter.com/empiremagazine	Twitter	new tab	Add '(opens in new tab)' to text
//www.pinterest.com/empiremagazine/	Pinterest	new tab	Add '(opens in new tab)' to text

217 links and buttons have descriptive text

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

https://account.greatmagazines.co.uk?utm_source=empireonline.com&utm_medium=r…; //www.facebook.com/empiremagazine; //twitter.com/empiremagazine; //www.pinterest.com/empiremagazine/

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

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

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

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

●`<frame>` or `<iframe>` elements have a title

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

●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

●Identical links have the same purpose.

○`[accesskey]` values are unique

○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

○Buttons have an accessible name

○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

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

○No element has a `[tabindex]` value greater than 0

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

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