Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

15 PASS 4 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-woex1k

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://Wealth-os.online/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://Wealth-os.online/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: #c9a227

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 ✗

Landmark Structure

Action

4 landmarks

REVIEW

4 landmarks

No <main> landmark found

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

1 <nav> landmark(s) found

Skip navigation link present

Skip link target(s) don't exist on page: #main-content, #main-content

The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.

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

Why this matters

Skip link points at an ID that doesn't exist on the page. The link looks fine visually but does nothing when activated -- silent WCAG 2.4.1 failure.

Learn more ▾

Find the target landmark (typically <main> or the first <h1>) and add `id="..."` matching the skip link's href fragment. Test by tabbing to the skip link and pressing Enter -- focus should jump to the target.

Source: WCAG 2.1 SC 2.4.1

Link & Button Quality

5 issue(s) across 25 links and 20 buttons

REVIEW

5 issue(s) across 25 links and 20 buttons

5 button(s) with no accessible text

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

Got: button.w-8 (#991 on page); button.w-2 (#992 on page); button.w-2 (#993 on page); button.w-2 (#994 on page); button.w-8 (#997 on page)

25 link(s) with descriptive text

25 links

0 empty

0 generic text

0 new tab

5 empty buttons

Element	Text	Issue	Suggested Fix
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

40 links and buttons have descriptive text

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

button.w-8 (#991 on page); button.w-2 (#992 on page); button.w-2 (#993 on page); button.w-2 (#994 on page); button.w-8 (#997 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

Mobile-Readable Font Sizes

Action

76% of visible text renders at >= 12 CSS px (78 below threshold)

REVIEW

76% of visible text renders at >= 12 CSS px (78 below threshold)

78 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: <p> 9.0px ("Total Net Worth"); <p> 9.0px ("↑ +6.42%"); <p> 9.0px ("Income"); <p> 10.0px ("WealthOS"); <p> 10.0px ("Total Net Worth").

Favicon & Branding

5 icon(s) detected

REVIEW

5 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

A+

Heading Hierarchy

23 headings

PASS

23 headings

Single H1 present

H1 Your Money. Your Plan. Your Future.Your Money. Your Plan. Your Future.
H2 Money shouldn't feel this complicated.
H3 Too many accounts
H3 No clear picture
H3 Goals without a plan
H2 Meet WealthOS.
H2 Built around your life, not just your numbers.
H3 Know where you stand.
H3 Save without thinking about it.
H3 Turn numbers into decisions.
H3 See your progress.
H2 Build the life you're saving for.
H2 Stop managing your money everywhere.
H2 Up and running in minutes.
H3 Connect
H3 Understand
H3 Grow
H2 What could your savings become?
H2 Trusted by people building their financial future.
H2 Your financial data deserves serious protection.
H2 Invest in your financial future
H2 Questions answered.
H2 Your future won't build itself.

A+

Heading Text Quality

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

PASS

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

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

Alt Text Quality

4 of 10 images have issues

PASS

4 of 10 images have issues

4 image(s) with generic alt text

1 decorative image(s) correctly marked

5 image(s) with good alt text

10 images 5 good alt text 1 decorative 4 generic

Issue	Count
generic	4 image(s)

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
input	range	Monthly savings ($)	aria-label
input	range	Years	aria-label
input	range	Expected annual growth (%)	aria-label

A+

Form Input Types

3 form control(s) checked, no type mismatches

PASS

3 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

3 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

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

PASS

1 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

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+

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

PASS

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

20 pass

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Your Money. Your Pla…	12.51:1	3.0:1	#000000	#C5C8CC	Pass
h2 Money shouldn't feel…	12.51:1	3.0:1	#000000	#C5C8CC	Pass
h2 Meet WealthOS.	12.51:1	3.0:1	#000000	#C5C8CC	Pass
h2 Built around your li…	12.51:1	3.0:1	#000000	#C5C8CC	Pass
h2 Build the life you'r…	12.51:1	3.0:1	#000000	#C5C8CC	Pass
h2 Stop managing your m…	12.51:1	3.0:1	#000000	#C5C8CC	Pass
h2 Up and running in mi…	12.51:1	3.0:1	#000000	#C5C8CC	Pass
h2 What could your savi…	12.51:1	3.0:1	#000000	#C5C8CC	Pass
h2 Trusted by people bu…	12.51:1	3.0:1	#000000	#C5C8CC	Pass
h2 Your financial data …	12.51:1	3.0:1	#000000	#C5C8CC	Pass
h2 Invest in your finan…	12.51:1	3.0:1	#000000	#C5C8CC	Pass
h2 Questions answered.	12.51:1	3.0:1	#000000	#C5C8CC	Pass
h2 Your future won't bu…	12.51:1	3.0:1	#000000	#C5C8CC	Pass
h3 Too many accounts	12.51:1	3.0:1	#000000	#C5C8CC	Pass
h3 No clear picture	12.51:1	3.0:1	#000000	#C5C8CC	Pass
h3 Goals without a plan	12.51:1	3.0:1	#000000	#C5C8CC	Pass
h3 Know where you stand…	12.51:1	3.0:1	#000000	#C5C8CC	Pass
h3 Save without thinkin…	12.51:1	3.0:1	#000000	#C5C8CC	Pass
h3 Turn numbers into de…	12.51:1	3.0:1	#000000	#C5C8CC	Pass
h3 See your progress.	12.51:1	3.0:1	#000000	#C5C8CC	Pass

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.

Lighthouse Accessibility Audits

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

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.relative > div.lg:hidden > div.flex > button.w-8 `div.relative > div.lg:hidden > div.flex > button.w-8`
div.relative > div.lg:hidden > div.flex > button.w-2 `div.relative > div.lg:hidden > div.flex > button.w-2`
div.relative > div.lg:hidden > div.flex > button.w-2 `div.relative > div.lg:hidden > div.flex > button.w-2`
div.relative > div.lg:hidden > div.flex > button.w-2 `div.relative > div.lg:hidden > div.flex > button.w-2`
div.relative > div.lg:hidden > div.flex > button.w-8 `div.relative > div.lg:hidden > div.flex > button.w-8`

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

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
Net Worth `div.relative > div.absolute > div > p.text-[9px]`
Savings Rate `div.hero-dashboard-wrapper > div.relative > div.absolute > p.text-[9px]`
28% / month `div.hero-dashboard-wrapper > div.relative > div.absolute > p.text-xs`

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

●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

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

●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

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

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

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

●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

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements 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

○Links are distinguishable without relying on color.

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

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