Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

4 PASS 4 REVIEW 5 FIX

Landmark Structure

Action

1 landmarks

FIX

1 landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

No <nav> landmark 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

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

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

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.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

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

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

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

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.

Link & Button Quality

Action

4 issue(s) across 38 links and 13 buttons

REVIEW

4 issue(s) across 38 links and 13 buttons

3 link(s) with generic text

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

Got: /roam ("Learn More"); /residential ("here"); /technology ("Learn More")

4 link(s) open in new tab without warning

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

Got: https://play.google.com/store/apps/details?id=com.starlink.mobile; https://apps.apple.com/app/starlink/id1537177988; https://www.spacex.com/; /legal

1 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.mat-focus-indicator (#158 on page)

31 link(s) with descriptive text

38 links

0 empty

3 generic text

4 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
/roam	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Roam
https://play.google.com/store/apps/detai…	Download for androidchevron_ri…	new tab	Add '(opens in new tab)' to text
https://apps.apple.com/app/starlink/id15…	Download for iOSchevron_right	new tab	Add '(opens in new tab)' to text
/residential	here	generic text	Replace with descriptive text
Before: here Suggested: Residential
/technology	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Technology
https://www.spacex.com/	spacex.com	new tab	Add '(opens in new tab)' to text
/legal	Privacy Policy	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label

43 links and buttons have descriptive text

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

/roam ("Learn More"); /residential ("here"); /technology ("Learn 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://play.google.com/store/apps/details?id=com.starlink.mobile; https://apps.apple.com/app/starlink/id1537177988; https://www.spacex.com/; /legal

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

Icon-only buttons need an aria-label so screen readers can announce them.

button.mat-focus-indicator (#158 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

Favicon & Branding

Action

6 icon(s) detected

REVIEW

6 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

Apple touch icon present

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

Web Manifest

Action

Valid manifest

REVIEW

Valid manifest

No name or short_name

Add a name field to identify the app.

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria Not Installable

Name ✗192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓

Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)

Color Contrast (Screenshot)

Action

20 text elements analyzed, 18 fail WCAG AA

REVIEW

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

2 pass 18 fail WCAG AA

h1 RELIABLE HIGH-SPEED INTERNET FROM SPACE

1.00:1

#000000

needs 3.0:1 (large text)

32px · bottom of viewport

h2 Up to 400+ Mbps in the U.S.

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Get started below or call

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Reliable & resilient

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Internet designed for every need

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Starlink Mini for internet on the go

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 GET ONLINE IN MINUTES

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Flexible Service Plans

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 ENGINEERED BY SPACEX

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

span Personal

2.03:1

#000000

#364150

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

span Business

1.76:1

#000000

#2A3848

needs 4.5:1 (normal text)

16px · top of page (header area)

span Residential

1.99:1

#000000

#314052

needs 4.5:1 (normal text)

16px · above the fold

span Roam

1.99:1

#000000

#334050

needs 4.5:1 (normal text)

16px · above the fold

a Sign In

1.88:1

#000000

#313C4C

needs 4.5:1 (normal text)

16px · above the fold

span Help Center

1.96:1

#000000

#323F4F

needs 4.5:1 (normal text)

16px · above the fold

span Availability Map

1.98:1

#000000

#34404C

needs 4.5:1 (normal text)

16px · above the fold

span Specifications

1.90:1

#000000

#303D4D

needs 4.5:1 (normal text)

16px · above the fold

span Service Plans

2.05:1

#000000

#354252

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 RELIABLE HIGH-SPEED …	1.00:1	3.0:1	#000000	#000000	Fail
h2 Up to 400+ Mbps in t…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Get started below or…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Reliable & resilient	1.00:1	3.0:1	#000000	#000000	Fail
h2 Internet designed fo…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Starlink Mini for in…	1.00:1	3.0:1	#000000	#000000	Fail
h2 GET ONLINE IN MINUTE…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Flexible Service Pla…	1.00:1	3.0:1	#000000	#000000	Fail
h2 ENGINEERED BY SPACEX	1.00:1	3.0:1	#000000	#000000	Fail
title Starlink	21.00:1	4.5:1	#000000	#FFFFFF	Pass
b Residential service …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
span Personal	2.03:1	4.5:1	#000000	#364150	Fail
span Business	1.76:1	4.5:1	#000000	#2A3848	Fail
span Residential	1.99:1	4.5:1	#000000	#314052	Fail
span Roam	1.99:1	4.5:1	#000000	#334050	Fail
a Sign In	1.88:1	4.5:1	#000000	#313C4C	Fail
span Help Center	1.96:1	4.5:1	#000000	#323F4F	Fail
span Availability Map	1.98:1	4.5:1	#000000	#34404C	Fail
span Specifications	1.90:1	4.5:1	#000000	#303D4D	Fail
span Service Plans	2.05:1	4.5:1	#000000	#354252	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

8 headings

PASS

8 headings

Single H1 present

H1 RELIABLE HIGH-SPEED INTERNET FROM SPACE
H2 No upfront Residential hardware cost & professional install in select areas.Up to 400+ Mbps in the U.S.Get started below or call (888) GO-STARLINK.
H2 Reliable & resilient
H2 Internet designed for every need
H2 Starlink Mini for internet on the go
H2 GET ONLINE IN MINUTES
H2 Flexible Service Plans
H2 ENGINEERED BY SPACEX

A+

Alt Text Quality

All 10 images OK

PASS

All 10 images OK

7 decorative image(s) correctly marked

3 image(s) with good alt text

10 images 3 good alt text 7 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 3 controls labeled

PASS

All 3 controls labeled

3 control(s) properly labeled

3 controls

3 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#map-service-input	text	Service Address	aria-label
#footer-service-input	text	Service Address	aria-label
#email-input-footer-63	email	Email	for/id

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

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

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

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

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

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