Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 3 REVIEW 5 FIX

404 Error Page

Action

HTTP 403, custom page

FIX

HTTP 403, custom page

Unexpected status code: HTTP 403

Expected HTTP 404 but received 403. This may confuse search engine crawlers.

Got: HTTP 403

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 403 ✗Page Title Just a moment... ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Favicon & Branding

Action

3 icon(s) detected

FIX

3 icon(s) detected

favicon.ico present at site root

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

Multiple icon sizes detected

✓ favicon.ico Present

✗ PNG Icons Missing

✗ Apple Touch Missing

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

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 ✗

Landmark Structure

Action

1 landmarks

REVIEW

1 landmarks

<main> landmark present

No <nav> landmark found

No banner (header) landmark

No contentinfo (footer) 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

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

Web Manifest

Valid manifest

REVIEW

Valid manifest

Name present: Epic Games

192x192 icon present

Display mode: standalone

PWA Install Criteria Not Installable

Name Epic Games ✓192×192 icon ✓512×512 icon ✗Start URL ✗Display Mode standalone ✓

Name Epic Games Display Mode standalone Theme Color #2a2a2a Background Color #2a2a2a Icons 2 icon(s)

Color Contrast (Screenshot)

Action

8 text elements analyzed, 8 fail WCAG AA

REVIEW

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

0 pass 8 fail WCAG AA

h1 One more step

1.11:1

#000000

#101014

needs 3.0:1 (large text)

32px · top of page (header area)

title Just a moment...

1.11:1

#000000

#101014

needs 4.5:1 (normal text)

16px · top of page (header area)

p Please complete a security check to cont…

1.11:1

#000000

#101014

needs 4.5:1 (normal text)

16px · top of page (header area)

div Verification successful. Waiting for www…

1.11:1

#000000

#101014

needs 4.5:1 (normal text)

16px · top of page (header area)

strong Session ID

1.11:1

#000000

#101014

needs 3.0:1 (large text)

16px · above the fold

p : 9ed4c83d3c4d0eaa

1.11:1

#000000

#101014

needs 4.5:1 (normal text)

16px · above the fold

strong IP Address

1.11:1

#000000

#101014

needs 3.0:1 (large text)

16px · above the fold

p : 5.8.34.200

1.10:1

#000000

#0F0F13

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (8)

Element	Ratio	Required	FG	BG	Result
h1 One more step	1.11:1	3.0:1	#000000	#101014	Fail
title Just a moment...	1.11:1	4.5:1	#000000	#101014	Fail
p Please complete a se…	1.11:1	4.5:1	#000000	#101014	Fail
div Verification success…	1.11:1	4.5:1	#000000	#101014	Fail
strong Session ID	1.11:1	3.0:1	#000000	#101014	Fail
p : 9ed4c83d3c4d0eaa	1.11:1	4.5:1	#000000	#101014	Fail
strong IP Address	1.11:1	3.0:1	#000000	#101014	Fail
p : 5.8.34.200	1.10:1	4.5:1	#000000	#0F0F13	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

2 headings

PASS

2 headings

Single H1 present

1 empty heading(s)

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

H1 One more step
H2 (empty)

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

A+

Alt Text Quality

All 1 images OK

PASS

All 1 images OK

1 image(s) with good alt text

1 images 1 good alt text

All images have appropriate alt text.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

A+

Link & Button Quality

No links or buttons

PASS

No links or buttons

No links or buttons on this page

0 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

A+

Lighthouse Accessibility Audits

Score 95/100 — 3 failing, 24 passed

PASS

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.

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
New Featured Carousel `div > div.css-1wwyop4 > div > h5.eds_1ypbntd0`

These are opportunities to improve keyboard navigation in your application.

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
Slide 1 of 6 `div.css-cdzsa1 > div > div.css-mzrlh2 > button.css-f18ets`
Slide 2 of 6 `div.css-cdzsa1 > div > div.css-mzrlh2 > button.css-f18ets`
Slide 3 of 6 `div.css-cdzsa1 > div > div.css-mzrlh2 > button.css-f18ets`
Slide 4 of 6 `div.css-cdzsa1 > div > div.css-mzrlh2 > button.css-f18ets`
Slide 5 of 6 `div.css-cdzsa1 > div > div.css-mzrlh2 > button.css-f18ets`
Slide 6 of 6 `div.css-cdzsa1 > div > div.css-mzrlh2 > button.css-f18ets`
Slide 1 of 3 `div > div.css-ikhelv > div.css-mzrlh2 > button.css-f18ets`
Slide 2 of 3 `div > div.css-ikhelv > div.css-mzrlh2 > button.css-f18ets`
Slide 3 of 3 `div > div.css-ikhelv > div.css-mzrlh2 > button.css-f18ets`
Slide 1 of 3 `div > div.css-ikhelv > div.css-mzrlh2 > button.css-f18ets`
Slide 2 of 3 `div > div.css-ikhelv > div.css-mzrlh2 > button.css-f18ets`
Slide 3 of 3 `div > div.css-ikhelv > div.css-mzrlh2 > button.css-f18ets`

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
Base Game I Hate This Place €29.99 `div.swiper-slide > div > div.css-2mlzob > a.css-1k3j1r9`
Base Game 1348 Ex Voto €24.99 `div.swiper-slide > div > div.css-2mlzob > a.css-1k3j1r9`
See In Shop (Opens in new tab) `div.css-1sadfz1 > div.css-asovn8 > div.css-u4p24i > a.eds_wy6w1n0`
Base Game Metro 2033 Redux -90% €19.99* €1.99 `div.swiper-slide > div > div.css-2mlzob > a.css-1k3j1r9`
Edition Metro Exodus - Gold Edition -85% €39.99* €5.99 `div.swiper-slide > div > div.css-2mlzob > a.css-1k3j1r9`
FREE NOW The Stone of Madness Free Now - Apr 23 at 05:00 PM `div.css-aere9z > div > div.css-2mlzob > a.css-1k3j1r9`
COMING SOON DOOMBLADE Free Apr 23 - Apr 30 `div.css-aere9z > div > div.css-2mlzob > a.css-1k3j1r9`

○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

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

●`[lang]` attributes have a valid value

●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

○Form elements have associated labels

○Links are distinguishable without relying on color.

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