Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

14 PASS 5 REVIEW 5 FIX

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

Soft 404: server returns HTTP 200 for non-existent pages

The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.

Got: Status: 200 for /beavercheck-404-test-7bcu2p

404 Page Quality ✗ Soft 404 (HTTP 200)

Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://startrekonline.info/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://startrekonline.info/manifest.json

Manifest contains invalid JSON.

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

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

1 navigation landmark(s) detected

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

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

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

Landmark Structure

4 landmarks

REVIEW

4 landmarks

<main> landmark present

1 <nav> landmark(s) found

No banner (header) 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

Link & Button Quality

3 issue(s) across 25 links and 16 buttons

REVIEW

3 issue(s) across 25 links and 16 buttons

3 link(s) with generic text

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

Got: /news/sto-info-version-1-4-release ("Read more"); /news/sto-info-introducing-custom-tracking ("Read more"); /news/sto-info-introducing-storytime ("Read more")

3 link(s) open in new tab without warning

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

Got: https://startrekonline.info/privacy-policy; https://business.safety.google/privacy; https://www.cookieyes.com/product/cookie-consent/?ref=cypbcyb&utm_source=cook…

19 link(s) with descriptive text

25 links

0 empty

3 generic text

3 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://startrekonline.info/privacy-poli…	View Privacy Policy	new tab	Add '(opens in new tab)' to text
https://business.safety.google/privacy	Google Privacy Policy	new tab	Add '(opens in new tab)' to text
https://www.cookieyes.com/product/cookie…	Visit CookieYes website	new tab	Add '(opens in new tab)' to text
/news/sto-info-version-1-4-release	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: Sto Info Version 1 4 Release
/news/sto-info-introducing-custom-tracki…	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: Sto Info Introducing Custom Tracking
/news/sto-info-introducing-storytime	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: Sto Info Introducing Storytime

35 links and buttons have descriptive text

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

/news/sto-info-version-1-4-release ("Read more"); /news/sto-info-introducing-custom-tracking ("Read more"); /news/sto-info-introducing-storytime ("Read 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://startrekonline.info/privacy-policy; https://business.safety.google/privacy; https://www.cookieyes.com/product/cookie-consent/?ref=cypbcyb&utm_source=cook…

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

Mobile-Readable Font Sizes

95% of visible text renders at >= 12 CSS px (2 below threshold)

REVIEW

95% of visible text renders at >= 12 CSS px (2 below threshold)

2 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.9px ("FV-1.4.13"); <div> 11.9px ("BV-1.4.15").

Favicon & Branding

7 icon(s) detected

REVIEW

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

✓ Multiple Sizes Present

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 Welcome to the Star Trek Online Info Por…

1.08:1

#000000

#0D0D0D

needs 3.0:1 (large text)

32px · bottom of viewport

h2 Recent News

1.08:1

#000000

#0D0D0D

needs 3.0:1 (large text)

24px · bottom of viewport

title Home - Star Trek Online Info Portal

1.08:1

#000000

#0D0D0D

needs 4.5:1 (normal text)

16px · top of page (header area)

p Your privacy and cookies

1.08:1

#000000

#0D0D0D

needs 4.5:1 (normal text)

16px · top of page (header area)

p We use cookies to track user behaviour a…

1.08:1

#000000

#0D0D0D

needs 4.5:1 (normal text)

16px · top of page (header area)

a View Privacy Policy

2.31:1

#444A77

#0D0D0D

needs 4.5:1 (normal text)

16px · top of page (header area)

button Customise

1.08:1

#000000

#0D0D0D

needs 4.5:1 (normal text)

16px · above the fold

button Reject All

1.08:1

#000000

#0D0D0D

needs 4.5:1 (normal text)

16px · above the fold

button Accept All

1.08:1

#000000

#0D0D0D

needs 4.5:1 (normal text)

16px · above the fold

span Customise Consent Preferences

1.08:1

#000000

#0D0D0D

needs 4.5:1 (normal text)

16px · above the fold

p We use cookies to help you navigate effi…

1.08:1

#000000

#0D0D0D

needs 4.5:1 (normal text)

16px · above the fold

p The cookies that are categorised as "Nec…

1.08:1

#000000

#0D0D0D

needs 4.5:1 (normal text)

16px · above the fold

button Show more

1.08:1

#000000

#0D0D0D

needs 4.5:1 (normal text)

16px · above the fold

p For more information on how Google's thi…

1.08:1

#000000

#0D0D0D

needs 4.5:1 (normal text)

16px · above the fold

a Google Privacy Policy

1.64:1

#303845

#0D0D0D

needs 4.5:1 (normal text)

16px · above the fold

button Necessary

1.08:1

#000000

#0D0D0D

needs 4.5:1 (normal text)

16px · mid-page

span Always Active

1.08:1

#000000

#0D0D0D

needs 4.5:1 (normal text)

16px · mid-page

p Necessary cookies are required to enable…

1.08:1

#000000

#0D0D0D

needs 4.5:1 (normal text)

16px · mid-page

div Cookie

1.08:1

#000000

#0D0D0D

needs 4.5:1 (normal text)

16px · mid-page

div cookie-yes

1.08:1

#000000

#0D0D0D

needs 4.5:1 (normal text)

16px · mid-page

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Welcome to the Star …	1.08:1	3.0:1	#000000	#0D0D0D	Fail
h2 Recent News	1.08:1	3.0:1	#000000	#0D0D0D	Fail
title Home - Star Trek Onl…	1.08:1	4.5:1	#000000	#0D0D0D	Fail
p Your privacy and coo…	1.08:1	4.5:1	#000000	#0D0D0D	Fail
p We use cookies to tr…	1.08:1	4.5:1	#000000	#0D0D0D	Fail
a View Privacy Policy	2.31:1	4.5:1	#444A77	#0D0D0D	Fail
button Customise	1.08:1	4.5:1	#000000	#0D0D0D	Fail
button Reject All	1.08:1	4.5:1	#000000	#0D0D0D	Fail
button Accept All	1.08:1	4.5:1	#000000	#0D0D0D	Fail
span Customise Consent Pr…	1.08:1	4.5:1	#000000	#0D0D0D	Fail
p We use cookies to he…	1.08:1	4.5:1	#000000	#0D0D0D	Fail
p The cookies that are…	1.08:1	4.5:1	#000000	#0D0D0D	Fail
button Show more	1.08:1	4.5:1	#000000	#0D0D0D	Fail
p For more information…	1.08:1	4.5:1	#000000	#0D0D0D	Fail
a Google Privacy Polic…	1.64:1	4.5:1	#303845	#0D0D0D	Fail
button Necessary	1.08:1	4.5:1	#000000	#0D0D0D	Fail
span Always Active	1.08:1	4.5:1	#000000	#0D0D0D	Fail
p Necessary cookies ar…	1.08:1	4.5:1	#000000	#0D0D0D	Fail
div Cookie	1.08:1	4.5:1	#000000	#0D0D0D	Fail
div cookie-yes	1.08:1	4.5:1	#000000	#0D0D0D	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

5 headings

PASS

5 headings

Single H1 present

H1 Welcome to the Star Trek Online Info Portal!
H2 Recent News
H2 STO Info 1.4 — Storytime, Custom Tracking and More
H2 Introducing Custom Tracking
H2 Introducing STO Storytime

A+

Heading Text Quality

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

PASS

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

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

A+

Alt Text Quality

All 4 images OK

PASS

All 4 images OK

3 decorative image(s) correctly marked

1 image(s) with good alt text

4 images 1 good alt text 3 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
#ckySwitchfunctional	checkbox	Enable Functional	aria-label
#ckySwitchanalytics	checkbox	Enable Analytics	aria-label

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

PASS

Lang attribute set to "en-GB"

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

Got: en-GB

A+

Tabindex Anti-Patterns

3 explicit tabindex attribute(s) checked, no anti-patterns

PASS

3 explicit tabindex attribute(s) checked, no anti-patterns

No tabindex anti-patterns detected

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

2 mobile-depth signal(s) detected

PASS

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

iOS auto-link for phone numbers disabled (`format-detection: telephone=no`)

The page sets `<meta name="format-detection" content="telephone=no">`, which prevents iOS Safari from auto-converting phone-number-shaped strings into clickable `tel:` links. Common reason: the auto-detection rewrites mid-paragraph DOM and breaks CSS selectors / JS that depended on the specific text. If you want clickable phone numbers, declare them with explicit `<a href="tel:+1234567890">` and keep auto-detection disabled.

A+

Lighthouse Accessibility Audits

Score 100/100 — 0 failing, 25 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.

○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 are distinguishable without relying on color.

●Links have a discernible name

●No element has a `[tabindex]` value greater than 0

●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

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

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

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

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

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