Accessibility

F

Navigation UX

Action

1 navigation pattern(s)

FIX

1 navigation pattern(s)

Skip navigation link detected

3 navigation landmark(s) detected

Breadcrumbs

Search

Skip Link Skip link detected

Labeled Navigation 3 <nav> element(s)

Back to Top

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.

C

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page Not Found — -PTF- ARMADA ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✗

B

Favicon & Branding

8 icon(s) detected

REVIEW

8 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

C

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 Armada

1.06:1

#000000

on

#060B0A

needs 3.0:1 (large text)

32px · above the fold

h2 What PTF is

1.04:1

#000000

on

#030706

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Why join PTF

1.04:1

#000000

on

#030706

needs 3.0:1 (large text)

24px · bottom of viewport

h3 A shared system across PTF.

1.04:1

#000000

on

#030706

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Find people to play with.

1.04:1

#000000

on

#030706

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Learn from experience.

1.04:1

#000000

on

#030706

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Take part without unnecessary barriers.

1.04:1

#000000

on

#030706

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Deep roots in STO PvP.

1.04:1

#000000

on

#030706

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Start with the PTF Discord.

1.04:1

#000000

on

#030706

needs 3.0:1 (large text)

19px · bottom of viewport

title PTF Armada | Star Trek Online Fleets & C…

1.42:1

#000000

on

#102943

needs 4.5:1 (normal text)

16px · top of page (header area)

a Skip to content

1.10:1

#000000

on

#05101B

needs 4.5:1 (normal text)

16px · top of page (header area)

div -PTF- ARMADA // STAR TREK ONLINE

1.07:1

#000000

on

#040D16

needs 4.5:1 (normal text)

16px · top of page (header area)

span -PTF- ARMADA

1.06:1

#000000

on

#030A11

needs 4.5:1 (normal text)

16px · top of page (header area)

small Star Trek Online

1.20:1

#000000

on

#0B1B23

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

a Home

1.12:1

#000000

on

#081416

needs 4.5:1 (normal text)

16px · above the fold

a Structure

1.13:1

#000000

on

#091516

needs 4.5:1 (normal text)

16px · above the fold

a Resources

1.11:1

#000000

on

#091314

needs 4.5:1 (normal text)

16px · above the fold

a Connect

1.11:1

#000000

on

#081213

needs 4.5:1 (normal text)

16px · above the fold

a Join Discord

1.10:1

#000000

on

#081111

needs 4.5:1 (normal text)

16px · above the fold

div Star Trek Online · PC · Federation + K…

1.09:1

#000000

on

#071010

needs 4.5:1 (normal text)

16px · above the fold

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Armada	1.06:1	3.0:1	#000000	#060B0A	Fail
h2 What PTF is	1.04:1	3.0:1	#000000	#030706	Fail
h2 Why join PTF	1.04:1	3.0:1	#000000	#030706	Fail
h3 A shared system acro…	1.04:1	3.0:1	#000000	#030706	Fail
h3 Find people to play …	1.04:1	3.0:1	#000000	#030706	Fail
h3 Learn from experienc…	1.04:1	3.0:1	#000000	#030706	Fail
h3 Take part without un…	1.04:1	3.0:1	#000000	#030706	Fail
h3 Deep roots in STO Pv…	1.04:1	3.0:1	#000000	#030706	Fail
h3 Start with the PTF D…	1.04:1	3.0:1	#000000	#030706	Fail
title PTF Armada \| Star Tr…	1.42:1	4.5:1	#000000	#102943	Fail
a Skip to content	1.10:1	4.5:1	#000000	#05101B	Fail
div -PTF- ARMADA // STAR…	1.07:1	4.5:1	#000000	#040D16	Fail
span -PTF- ARMADA	1.06:1	4.5:1	#000000	#030A11	Fail
small Star Trek Online	1.20:1	4.5:1	#000000	#0B1B23	Fail
a Home	1.12:1	4.5:1	#000000	#081416	Fail
a Structure	1.13:1	4.5:1	#000000	#091516	Fail
a Resources	1.11:1	4.5:1	#000000	#091314	Fail
a Connect	1.11:1	4.5:1	#000000	#081213	Fail
a Join Discord	1.10:1	4.5:1	#000000	#081111	Fail
div Star Trek Online · …	1.09:1	4.5:1	#000000	#071010	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

11 landmarks

PASS

11 landmarks

<main> landmark present

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

9 headings

PASS

9 headings

Single H1 present

H1 -PTF- Armada
H2 What PTF is
H3 A shared system across PTF.
H2 Why join PTF
H3 Find people to play with.
H3 Learn from experience.
H3 Take part without unnecessary barriers.
H3 Deep roots in STO PvP.
H3 Start with the PTF Discord.

A+

Heading Text Quality

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

PASS

All 9 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

1 decorative image(s) correctly marked

1 image(s) with good alt text

2 images 1 good alt text 1 decorative

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

19 links, 0 buttons — all OK

PASS

19 links, 0 buttons — all OK

19 link(s) with descriptive text

19 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

19 links and buttons have descriptive text

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-GB"

PASS

Lang attribute set to "en-GB"

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

Got: en-GB

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 86 visible text node(s) render at >= 12 CSS pixels

PASS

All 86 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: PTF Armada

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name PTF Armada ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode standalone ✓

Name PTF Armada Display Mode standalone Theme Color #071522 Background Color #030706 Icons 3 icon(s)

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Dark Mode Support

Full dark mode support

PASS

Full dark mode support

color-scheme meta tag present

The site declares support for light and dark color schemes via <meta name='color-scheme'>.

Got: strict-origin-when-cross-origin

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 strict-origin-when-cross-origin ✓Dark theme-color #071522 ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

A+

Print Stylesheet

Print styles detected

PASS

Print styles detected

External print stylesheet detected

Got: /assets/print.0d38f95083.css

Print Stylesheet ✓ Print Optimized

Print stylesheet /assets/print.0d38f95083.css ✓Inline @media print Not 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, 21 passed

PASS

100

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
-PTF- ARMADA STAR TREK ONLINE `body#top > header.site-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

●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

●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

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

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

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