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 6 REVIEW 2 FIX

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

3 navigation landmark(s) detected

Hamburger menu detected (responsive design)

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 3 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

Landmark Structure

12 landmarks

REVIEW

12 landmarks

<main> landmark present

3 <nav> landmark(s) found

2 of 3 <nav> elements are unlabeled

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

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

Link & Button Quality

2 issue(s) across 55 links and 1 buttons

REVIEW

2 issue(s) across 55 links and 1 buttons

2 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: /trello/ ("More"); /trello/ ("More")

3 link(s) open in new tab without warning

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

Got: https://www.roblox.com/games/95409544559668/Military-Army-Tycoon; https://www.roblox.com/games/95409544559668/Military-Army-Tycoon; https://www.roblox.com/communities/683115741/Battle-Action

50 link(s) with descriptive text

55 links

0 empty

2 generic text

3 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/trello/	More	generic text	Replace with descriptive text
Before: More Suggested: Trello
https://www.roblox.com/games/95409544559…	Play on Roblox	new tab	Add '(opens in new tab)' to text
/trello/	More	generic text	Replace with descriptive text
Before: More Suggested: Trello
https://www.roblox.com/games/95409544559…	Official Roblox game	new tab	Add '(opens in new tab)' to text
https://www.roblox.com/communities/68311…	Battle Action Roblox group	new tab	Add '(opens in new tab)' to text

51 links and buttons have descriptive text

Generic link text like 'click here' doesn't describe the destination.

/trello/ ("More"); /trello/ ("More")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

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

https://www.roblox.com/games/95409544559668/Military-Army-Tycoon; https://www.roblox.com/games/95409544559668/Military-Army-Tycoon; https://www.roblox.com/communities/683115741/Battle-Action

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

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: This page could not be found. ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Favicon & Branding

9 icon(s) detected

REVIEW

9 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

Dark-specific theme-color detected

A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.

prefers-color-scheme CSS detected in inline styles

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark Mode✓ Dark Mode Supported

color-scheme meta Not set ✗Dark theme-color #061116 ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

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 Military Army Tycoon Wiki

1.16:1

#000000

#07181F

needs 3.0:1 (large text)

32px · bottom of viewport

h2 Field Hub: the checked answer

1.16:1

#000000

#07181F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Task Entry

1.16:1

#000000

#07181F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Core systems

1.16:1

#000000

#07181F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Latest status

1.16:1

#000000

#07181F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Sources and verification

1.16:1

#000000

#07181F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Discovery

1.16:1

#000000

#07181F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Frequently asked questions

1.16:1

#000000

#07181F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Checked detail 1

1.16:1

#000000

#07181F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Checked detail 2

1.16:1

#000000

#07181F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Checked detail 3

1.16:1

#000000

#07181F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Checked detail 4

1.16:1

#000000

#07181F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Apply the evidence in the live game

1.16:1

#000000

#07181F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 If your screen looks different

1.16:1

#000000

#07181F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 What does the Field Hub evidence confirm…

1.16:1

#000000

#07181F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Where this answer comes from

1.16:1

#000000

#07181F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Military Army Tycoon Wiki

1.16:1

#000000

#07181F

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Base economy

1.16:1

#000000

#07181F

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Squad command

1.16:1

#000000

#07181F

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Strategic capture

1.16:1

#000000

#07181F

needs 3.0:1 (large text)

19px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Military Army Tycoon…	1.16:1	3.0:1	#000000	#07181F	Fail
h2 Field Hub: the check…	1.16:1	3.0:1	#000000	#07181F	Fail
h2 Task Entry	1.16:1	3.0:1	#000000	#07181F	Fail
h2 Core systems	1.16:1	3.0:1	#000000	#07181F	Fail
h2 Latest status	1.16:1	3.0:1	#000000	#07181F	Fail
h2 Sources and verifica…	1.16:1	3.0:1	#000000	#07181F	Fail
h2 Discovery	1.16:1	3.0:1	#000000	#07181F	Fail
h2 Frequently asked que…	1.16:1	3.0:1	#000000	#07181F	Fail
h2 Checked detail 1	1.16:1	3.0:1	#000000	#07181F	Fail
h2 Checked detail 2	1.16:1	3.0:1	#000000	#07181F	Fail
h2 Checked detail 3	1.16:1	3.0:1	#000000	#07181F	Fail
h2 Checked detail 4	1.16:1	3.0:1	#000000	#07181F	Fail
h2 Apply the evidence i…	1.16:1	3.0:1	#000000	#07181F	Fail
h2 If your screen looks…	1.16:1	3.0:1	#000000	#07181F	Fail
h2 What does the Field …	1.16:1	3.0:1	#000000	#07181F	Fail
h2 Where this answer co…	1.16:1	3.0:1	#000000	#07181F	Fail
h2 Military Army Tycoon…	1.16:1	3.0:1	#000000	#07181F	Fail
h3 Base economy	1.16:1	3.0:1	#000000	#07181F	Fail
h3 Squad command	1.16:1	3.0:1	#000000	#07181F	Fail
h3 Strategic capture	1.16:1	3.0:1	#000000	#07181F	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

25 headings

PASS

25 headings

Single H1 present

H1 Military Army Tycoon Wiki
H2 Field Hub: the checked answer
H2 Task Entry
H2 Core systems
H3 Base economy
H3 Squad command
H3 Strategic capture
H2 Latest status
H2 Sources and verification
H2 Discovery
H2 Frequently asked questions
H3 Which Roblox game does this site cover?
H3 Is this an official website?
H2 Checked detail 1
H2 Checked detail 2
H2 Checked detail 3
H2 Checked detail 4
H2 Apply the evidence in the live game
H2 If your screen looks different
H2 What does the Field Hub evidence confirm?
H2 Where this answer comes from
H2 Military Army Tycoon Wiki
H3 Core pages
H3 Sources
H3 Site info

A+

Heading Text Quality

All 25 heading(s) have substantive, well-formed text

PASS

All 25 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A+

Alt Text Quality

All 2 images OK

PASS

All 2 images OK

2 image(s) with good alt text

2 images 2 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+

Form Input Types

No form controls on this page

PASS

No form controls on this page

A+

Form Input Quality

No form controls on this page

PASS

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

No form controls on this page

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+

Mobile-Readable Font Sizes

All 112 visible text node(s) render at >= 12 CSS pixels

PASS

All 112 visible text node(s) render at >= 12 CSS pixels

All text uses legible mobile font sizes (>= 12 CSS px)

A+

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: Military Army Tycoon Calculator

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name Military Army Tycoon Calculator ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode standalone ✓

Name Military Army Tycoon Calculator Display Mode standalone Theme Color #11160a Background Color #0d1108 Icons 3 icon(s)

A+

PWA Depth

1 PWA signal(s) surfaced

PASS

1 PWA signal(s) surfaced

Manifest has no maskable icon

Android 12+ Adaptive Icons crop non-maskable icons to a circle or squircle -- frequently hiding important parts of the logo. Add at least one icon entry with `"purpose": "maskable"` (or `"any maskable"`) and a maskable-aware design (16% safe-zone padding around the inner mark).

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.

Lighthouse Accessibility Audits

Score 92/100 — 2 failing, 22 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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
military-armytycoon.wiki is an unofficial fan-made Roblox resource. `body.inter_5901b7c6-module__ec5Qua__variable > footer.border-t > div.mx-auto > div.mt-8`

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Continue to /codes `section > nav > p > a`
Continue to /tier-list `section > nav > p > a`
Continue to /guides `section > nav > p > a`
Continue to /wiki `section > nav > p > a`
Continue to /trello `section > nav > p > a`
Continue to /updates `section > nav > p > a`
Continue to /sources `section > nav > p > a`

These are opportunities to improve the legibility of your content.

○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

●`<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 have a discernible name

●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

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

○Form elements have associated labels

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

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

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.