Skip to content
https://evilempire.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
77
GRADE
C
FIX
5
REVIEW
7
PASS
12
INFO
0
Checks
24
12 PASS 7 REVIEW 5 FIX
F
404 Error Page
Action
HTTP 404, bare page
FIX
HTTP 404, bare page
Info::
Correct 404 status code returned
Got: HTTP 404
Warning::
Bare server default 404 page
The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.
404 Page Quality Default 404 Page
Status Code HTTP 404 ✓Page Title 404 Not Found ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
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
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
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 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.

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::
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
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
3 landmarks
REVIEW
3 landmarks
Info::
<main> landmark present
Warning::
No <nav> landmark found
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 MAIN CONTENTINFO footer

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

B
Heading Hierarchy
7 headings
REVIEW
7 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H2 We make games.
  • H2 The Rogue Prince of Persia
  • H2 Brotato
  • H2 Dead Cells: Return to Castlevania
  • H2 Dead Cells: The Queen and the Sea
  • H2 Dead Cells: Fatal Falls
  • H2 Dead Cells: The Bad Seed

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

C
Document Language
Action
Lang attribute "en_US" is malformed
REVIEW
Lang attribute "en_US" is malformed
Warning::
<html lang="en_US"> is not a valid BCP-47 tag
Language attribute is present but doesn't parse as a valid BCP-47 tag (e.g., 'english' instead of 'en', or 'us' which is a region not a language). Screen readers may ignore invalid values and fall back to the system locale.
B
Favicon & Branding
6 icon(s) detected
REVIEW
6 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 Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
14 text elements analyzed, 3 fail WCAG AA
REVIEW

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

11 pass 3 fail WCAG AA
h2 Dead Cells: The Bad Seed
1.11:1
#000000
on
#150F0C
needs 3.0:1 (large text)
24px · mid-page
p Try not to fall as you wind your way alo…
1.05:1
#000000
on
#0D0807
needs 4.5:1 (normal text)
16px · mid-page
p Explore a relaxing Arboretum, wade throu…
1.45:1
#000000
on
#302915
needs 4.5:1 (normal text)
16px · mid-page
Show all checked elements (14)
ElementRatioRequiredFGBGResult
h2 We make games.12.91:13.0:1
#000000
#F6C447
Pass
h2 The Rogue Prince of …12.91:13.0:1
#000000
#F6C447
Pass
h2 Brotato12.91:13.0:1
#000000
#F6C447
Pass
h2 Dead Cells: Return t…12.91:13.0:1
#000000
#F6C447
Pass
h2 Dead Cells: The Quee…12.91:13.0:1
#000000
#F6C447
Pass
h2 Dead Cells: Fatal Fa…12.91:13.0:1
#000000
#F6C447
Pass
h2 Dead Cells: The Bad …1.11:13.0:1
#000000
#150F0C
Fail
title EVIL EMPIRE12.91:14.5:1
#000000
#F6C447
Pass
p The new action rogue…12.91:14.5:1
#000000
#F6C447
Pass
p A spaceship from Pot…12.91:14.5:1
#000000
#F6C447
Pass
p The inspiration behi…12.91:14.5:1
#000000
#F6C447
Pass
p Battle your way thro…12.91:14.5:1
#000000
#F6C447
Pass
p Try not to fall as y…1.05:14.5:1
#000000
#0D0807
Fail
p Explore a relaxing A…1.45:14.5:1
#000000
#302915
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.

B
Lighthouse Accessibility Audits
Score 85/100 — 2 failing, 11 passed
REVIEW
85

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.

Internationalization and localization

Specifying a valid BCP 47 language helps screen readers announce text properly. Learn how to use the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These are opportunities to improve the interpretation of your content by users in different locales.

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
section#hero > ul.hero-links > li > a section#hero > ul.hero-links > li > a
section#hero > ul.hero-links > li > a section#hero > ul.hero-links > li > a
section#hero > ul.hero-links > li > a section#hero > ul.hero-links > li > a
section#hero > ul.hero-links > li > a section#hero > ul.hero-links > li > a
section#hero > ul.hero-links > li > a section#hero > ul.hero-links > li > a
section#hero > ul.hero-links > li > a section#hero > ul.hero-links > li > a
section#hero > ul.hero-links > li > a section#hero > ul.hero-links > li > a
Steam div.game-infos > ul.game-links > li > a
Xbox div.game-infos > ul.game-links > li > a
Playstation div.game-infos > ul.game-links > li > a
div.game-infos > ul.game-links > li > a div.game-infos > ul.game-links > li > a
Steam div.game-infos > ul.game-links > li > a
Xbox div.game-infos > ul.game-links > li > a
Playstation div.game-infos > ul.game-links > li > a
div.game-infos > ul.game-links > li > a div.game-infos > ul.game-links > li > a
Steam div.game-infos > ul.game-links > li > a
Xbox div.game-infos > ul.game-links > li > a
Playstation div.game-infos > ul.game-links > li > a
div.game-infos > ul.game-links > li > a div.game-infos > ul.game-links > li > a
Steam div.game-infos > ul.game-links > li > a
Xbox div.game-infos > ul.game-links > li > a
Playstation div.game-infos > ul.game-links > li > a
div.game-infos > ul.game-links > li > a div.game-infos > ul.game-links > li > a
Steam div.game-infos > ul.game-links > li > a
Xbox div.game-infos > ul.game-links > li > a
Playstation div.game-infos > ul.game-links > li > a
div.game-infos > ul.game-links > li > a div.game-infos > ul.game-links > li > a
Steam div.game-infos > ul.game-links > li > a
Xbox div.game-infos > ul.game-links > li > a
Playstation div.game-infos > ul.game-links > li > a
div.game-infos > ul.game-links > li > a div.game-infos > ul.game-links > li > a
Discord div.content > ul#footer-links > li > a
YouTube div.content > ul#footer-links > li > a
X div.content > ul#footer-links > li > a
Instagram div.content > ul#footer-links > li > a
Twitch div.content > ul#footer-links > li > a
BlueSky div.content > ul#footer-links > li > a
Facebook div.content > ul#footer-links > li > a

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.

○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-hidden="true"]` is not present on the document `<body>`
●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.
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●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.
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA attributes are used as specified for the element's role
○Deprecated ARIA roles were not used
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○`[aria-hidden="true"]` elements do not contain focusable descendents
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements use only permitted ARIA attributes
○`[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
○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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○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
○`<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.
○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.
○Identical links have the same purpose.
○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.
A+
Heading Text Quality
All 7 heading(s) have substantive, well-formed text
PASS
All 7 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 8 images OK
PASS
All 8 images OK
Info::
6 decorative image(s) correctly marked
Info::
2 image(s) with good alt text
8 images 2 good alt text 6 decorative
All images have appropriate alt text.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A+
Form Input Types
No form controls on this page
PASS
No form controls on this page
Info::
No form controls on this page
A+
Form Input Quality
No form controls on this page
PASS
No form controls on this page
Info::
No form controls on this page
A+
Mobile Keyboard & Autofill
No form controls -- mobile keyboard check is N/A
PASS
No form controls -- mobile keyboard check is N/A
Info::
No form controls on this page
A+
Tabindex Anti-Patterns
No explicit tabindex attributes found
PASS
No explicit tabindex attributes found
Info::
No explicit tabindex attributes found
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
No iframes on this page
A+
Tap Target Adequacy
All tap targets meet WCAG 2.5.5/2.5.8 sizing
PASS
All tap targets meet WCAG 2.5.5/2.5.8 sizing
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
Mobile-Readable Font Sizes
All 13 visible text node(s) render at >= 12 CSS pixels
PASS
All 13 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
No `<meta name="theme-color">` -- browser chrome falls back to default
Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback