Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

16 PASS 2 REVIEW 6 FIX

Mobile-Readable Font Sizes

Action

57% of visible text renders at >= 12 CSS px (125 below threshold)

FIX

57% of visible text renders at >= 12 CSS px (125 below threshold)

125 text node(s) render below 12 CSS pixels on mobile

Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <div> 11.0px ("The game mashup collection"); <div> 11.0px ("23 sourced projects · 16 author download..."); <span> 10.0px ("IN THE SPOTLIGHT"); <div> 11.0px ("Skyrim meets Minecraft"); <span> 10.0px ("Author download").

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

SVG favicon detected — scales perfectly to any size

✗ favicon.ico Missing

✓ PNG Icons Present

✗ Apple Touch Missing

✓ SVG Favicon Present

✗ 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

Theme color only

FIX

Theme color only

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: #111510

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

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 ✗

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 Mashup Not Found | Merging Games ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Color Contrast (Screenshot)

Action

20 text elements analyzed, 20 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 20 fail WCAG AA

h1 GAME MASHUPS

1.14:1

#000000

#111510

needs 3.0:1 (large text)

32px · above the fold

h2 Welcome to SkyCraft

1.14:1

#000000

#111510

needs 3.0:1 (large text)

24px · mid-page

h2 Find your next crossover

1.14:1

#000000

#111510

needs 3.0:1 (large text)

24px · bottom of viewport

h2 So, how do games get merged?

1.14:1

#000000

#111510

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Choose game mashups that fit your setup

1.14:1

#000000

#111510

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Optional analytics

1.14:1

#000000

#111510

needs 3.0:1 (large text)

24px · bottom of viewport

h3 No mashups match just yet.

1.14:1

#000000

#111510

needs 3.0:1 (large text)

19px · bottom of viewport

h3 What are game mashups?

1.14:1

#000000

#111510

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Where can I download game mashups?

1.14:1

#000000

#111510

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Find game mashups for your platform

1.14:1

#000000

#111510

needs 3.0:1 (large text)

19px · bottom of viewport

h3 What should I check before installing?

1.14:1

#000000

#111510

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Can I play these game mashups in my brow…

1.14:1

#000000

#111510

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Do game mashups need AI?

1.14:1

#000000

#111510

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Are game mashups the same as merge games…

1.14:1

#000000

#111510

needs 3.0:1 (large text)

19px · bottom of viewport

title Merging Games: Game Mashups & Crossover …

1.14:1

#000000

#111510

needs 4.5:1 (normal text)

16px · top of page (header area)

a Skip to content

1.14:1

#000000

#111510

needs 4.5:1 (normal text)

16px · top of page (header area)

span merging

1.14:1

#000000

#111510

needs 4.5:1 (normal text)

16px · top of page (header area)

small .games

1.14:1

#000000

#111510

needs 4.5:1 (normal text)

16px · top of page (header area)

a The collection

1.14:1

#000000

#111510

needs 4.5:1 (normal text)

16px · above the fold

a Merging games with AI

1.14:1

#000000

#111510

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 GAME MASHUPS	1.14:1	3.0:1	#000000	#111510	Fail
h2 Welcome to SkyCraft	1.14:1	3.0:1	#000000	#111510	Fail
h2 Find your next cross…	1.14:1	3.0:1	#000000	#111510	Fail
h2 So, how do games get…	1.14:1	3.0:1	#000000	#111510	Fail
h2 Choose game mashups …	1.14:1	3.0:1	#000000	#111510	Fail
h2 Optional analytics	1.14:1	3.0:1	#000000	#111510	Fail
h3 No mashups match jus…	1.14:1	3.0:1	#000000	#111510	Fail
h3 What are game mashup…	1.14:1	3.0:1	#000000	#111510	Fail
h3 Where can I download…	1.14:1	3.0:1	#000000	#111510	Fail
h3 Find game mashups fo…	1.14:1	3.0:1	#000000	#111510	Fail
h3 What should I check …	1.14:1	3.0:1	#000000	#111510	Fail
h3 Can I play these gam…	1.14:1	3.0:1	#000000	#111510	Fail
h3 Do game mashups need…	1.14:1	3.0:1	#000000	#111510	Fail
h3 Are game mashups the…	1.14:1	3.0:1	#000000	#111510	Fail
title Merging Games: Game …	1.14:1	4.5:1	#000000	#111510	Fail
a Skip to content	1.14:1	4.5:1	#000000	#111510	Fail
span merging	1.14:1	4.5:1	#000000	#111510	Fail
small .games	1.14:1	4.5:1	#000000	#111510	Fail
a The collection	1.14:1	4.5:1	#000000	#111510	Fail
a Merging games with A…	1.14:1	4.5:1	#000000	#111510	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+

Landmark Structure

9 landmarks

PASS

9 landmarks

<main> landmark present

2 <nav> landmark(s) found

All <nav> elements are properly labeled

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Heading Hierarchy

37 headings

PASS

37 headings

Single H1 present

H1 GAME MASHUPSTWO GAMESONE TWIST
H2 Welcome to SkyCraft
H2 Find your next crossover
H3 Minecraft X Half-Life
H3 HalfCraft
H3 ValCraft
H3 SilentDOOM
H3 FalloutCraft
H3 SkateGM
H3 Ultracraft
H3 Killcraft
H3 SkyCraft
H3 SkyDoom
H3 SekiroCraft
H3 OWCraft
H3 Skyring
H3 Super Mario Ring
H3 Skate Warfare
H3 SUPER IS HOT
H3 Mari0
H3 NucleDoom
H3 Balatro in Minecraft
H3 2010 Rust Rewrite Mashup
H3 Minecraft Crossover Bridge
H3 Skywind
H3 Minecraft Zombies
H3 No mashups match just yet.
H2 So, how do games get merged?
H2 Choose game mashups that fit your setup
H3 What are game mashups?
H3 Where can I download game mashups?
H3 Find game mashups for your platform
H3 What should I check before installing?
H3 Can I play these game mashups in my browser?
H3 Do game mashups need AI?
H3 Are game mashups the same as merge games?
H2 Optional analytics

A+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

2 heading(s) are all-uppercase (excluding short acronyms)

Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.

Got: 2 all-caps heading(s)

A+

Alt Text Quality

All 25 images OK

PASS

All 25 images OK

1 decorative image(s) correctly marked

24 image(s) with good alt text

25 images 24 good alt text 1 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 2 controls labeled

PASS

All 2 controls labeled

2 control(s) properly labeled

2 controls

2 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#search	search	⌕Search mashups	none
#platform	select	Platform	for/id

A+

Link & Button Quality

91 links, 9 buttons — all OK

PASS

91 links, 9 buttons — all OK

91 link(s) with descriptive text

91 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

100 links and buttons have descriptive text

A+

Form Input Types

2 form control(s) checked, no type mismatches

PASS

2 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

2 form control(s) checked, no input-semantic issues

PASS

2 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

No autofill-eligible form controls (no name/email/tel/address fields)

A+

Document Language

Lang attribute set to "en"

PASS

Lang attribute set to "en"

<html lang="en"> is set and valid

Got: en

A+

Tabindex Anti-Patterns

No explicit tabindex attributes found

PASS

No explicit tabindex attributes found

A+

Iframe Accessibility

No iframes on this page

PASS

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

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

Browser-chrome `theme-color` meta tag present

The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.

A+

Lighthouse Accessibility Audits

Score 100/100 — 1 failing, 29 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.

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
merging.games `body > header > div.wrap > a.brand`

○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

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

●Select elements have associated label elements.

●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

●`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

●Definition list items are wrapped in `<dl>` elements

●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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

○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

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

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

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