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

Form Accessibility

Action

11 of 13 controls have issues

FIX

11 of 13 controls have issues

2 control(s) without accessible label

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Got: <input type="number">; <select>

9 control(s) rely on placeholder only

Placeholder text disappears on focus and is not a reliable label.

Got: <input type="text">; <input type="text">; <textarea>; <input type="number">; <input type="number">; <input type="text">; <input type="password">; <input type="password">; <input type="password">

2 control(s) properly labeled

13 controls

2 labeled

9 placeholder only

2 unlabeled

Control	Type	Label	Method
#compose-attachment-input	file	Choose file to attach	aria-label
#live-chat-profile-unlock-pw	password	Profile password	for/id
textarea	textarea	(Enter your message (press Enter for new line))	placeholder only
input	text	(e.g. andre luiz — stored as andreluiz like signup)	placeholder only
input	number	(0)	placeholder only
input	number	(0)	placeholder only
input	text	(e.g. mia3, Mia 3, or Mia123)	placeholder only
input	password	(Enter password)	placeholder only
input	password	(Confirm password)	placeholder only
input	password	(Profile password)	placeholder only
input	text	(Enter subject)	placeholder only
select	select	(none)	none
input	number	(none)	none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

Placeholder text disappears on focus and is not a reliable label.

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

Mobile Keyboard & Autofill

Action

6/7 eligible field(s) missing autocomplete or inputmode

FIX

6/7 eligible field(s) missing autocomplete or inputmode

3 field(s) missing recommended autocomplete attribute

WCAG 1.3.5 (Level AA): inputs whose purpose maps to a Common Input Purpose value should declare it via `autocomplete=`. Required for password managers, browser autofill, and assistive tech that customizes inputs (e.g., simplified keyboards). Mobile autofill in particular cuts form-completion time by 30-50% when these are present. Affected purposes: current-password.

Got: <input type="password">, <input type="password">, <input type="password">

3 field(s) would benefit from inputmode attribute

Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: numeric.

Got: <input type="number">, <input type="number">, <input type="number">

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

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

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: #1a1a2e

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

2 landmarks

REVIEW

2 landmarks

<main> landmark present

No <nav> landmark found

No banner (header) landmark

No contentinfo (footer) 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

8 issue(s) across 0 links and 30 buttons

REVIEW

8 issue(s) across 0 links and 30 buttons

8 button(s) with no accessible text

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

Got: button.menu-toggle (#69 on page); button.modal-close (#122 on page); button.modal-close (#175 on page); button.modal-close (#190 on page); button.modal-close (#213 on page); button.modal-close (#234 on page); button.modal-close (#257 on page); button.modal-close (#276 on page)

0 links

0 empty

0 generic text

0 new tab

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

22 links and buttons have descriptive text

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

button.menu-toggle (#69 on page); button.modal-close (#122 on page); button.modal-close (#175 on page); button.modal-close (#190 on page); button.modal-close (#213 on page); button.modal-close (#234 on page); button.modal-close (#257 on page); button.modal-close (#276 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

4 icon(s) detected

REVIEW

4 icon(s) detected

favicon.ico present at site root

HTML icon links detected

No apple-touch-icon detected

iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.

SVG favicon detected — scales perfectly to any size

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✗ Apple Touch Missing

✓ SVG Favicon Present

✓ Manifest Icons Present

✓ 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 Inbox

1.23:1

#000000

#1A1A2E

needs 3.0:1 (large text)

32px · mid-page

h3 Inbox

1.23:1

#000000

#1A1A2E

needs 3.0:1 (large text)

19px · mid-page

h3 Send new email

1.23:1

#000000

#1A1A2E

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Confirm send / fee

1.23:1

#000000

#1A1A2E

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Log in / Register profile

1.23:1

#000000

#1A1A2E

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Read message

1.23:1

#000000

#1A1A2E

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Enter Profile Password

1.23:1

#000000

#1A1A2E

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Confirm live chat / fee

1.23:1

#000000

#1A1A2E

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Unlock live chat

1.23:1

#000000

#1A1A2E

needs 3.0:1 (large text)

19px · bottom of viewport

title XPENV — Private Web3 Messenger (offici…

1.23:1

#000000

#1A1A2E

needs 4.5:1 (normal text)

16px · top of page (header area)

div XPENV

1.23:1

#000000

#1A1A2E

needs 4.5:1 (normal text)

16px · top of page (header area)

p Private Web3 Messenger

1.23:1

#000000

#1A1A2E

needs 4.5:1 (normal text)

16px · top of page (header area)

button Add site in desktop

1.23:1

#000000

#1A1A2E

needs 4.5:1 (normal text)

16px · top of page (header area)

button Enter Freighter Wallet

1.23:1

#000000

#1A1A2E

needs 4.5:1 (normal text)

16px · above the fold

button Technical documentation

1.23:1

#000000

#1A1A2E

needs 4.5:1 (normal text)

16px · above the fold

button Questions FAQ

1.23:1

#000000

#1A1A2E

needs 4.5:1 (normal text)

16px · above the fold

button Warrant Canary

1.23:1

#000000

#1A1A2E

needs 4.5:1 (normal text)

16px · above the fold

span XPENV

1.23:1

#000000

#1A1A2E

needs 4.5:1 (normal text)

16px · above the fold

div XPENV

1.23:1

#000000

#1A1A2E

needs 4.5:1 (normal text)

16px · above the fold

button Send new email

1.23:1

#000000

#1A1A2E

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Inbox	1.23:1	3.0:1	#000000	#1A1A2E	Fail
h3 Inbox	1.23:1	3.0:1	#000000	#1A1A2E	Fail
h3 Send new email	1.23:1	3.0:1	#000000	#1A1A2E	Fail
h3 Confirm send / fee	1.23:1	3.0:1	#000000	#1A1A2E	Fail
h3 Log in / Register pr…	1.23:1	3.0:1	#000000	#1A1A2E	Fail
h3 Read message	1.23:1	3.0:1	#000000	#1A1A2E	Fail
h3 Enter Profile Passwo…	1.23:1	3.0:1	#000000	#1A1A2E	Fail
h3 Confirm live chat / …	1.23:1	3.0:1	#000000	#1A1A2E	Fail
h3 Unlock live chat	1.23:1	3.0:1	#000000	#1A1A2E	Fail
title XPENV — Private We…	1.23:1	4.5:1	#000000	#1A1A2E	Fail
div XPENV	1.23:1	4.5:1	#000000	#1A1A2E	Fail
p Private Web3 Messeng…	1.23:1	4.5:1	#000000	#1A1A2E	Fail
button Add site in desktop	1.23:1	4.5:1	#000000	#1A1A2E	Fail
button Enter Freighter Wall…	1.23:1	4.5:1	#000000	#1A1A2E	Fail
button Technical documentat…	1.23:1	4.5:1	#000000	#1A1A2E	Fail
button Questions FAQ	1.23:1	4.5:1	#000000	#1A1A2E	Fail
button Warrant Canary	1.23:1	4.5:1	#000000	#1A1A2E	Fail
span XPENV	1.23:1	4.5:1	#000000	#1A1A2E	Fail
div XPENV	1.23:1	4.5:1	#000000	#1A1A2E	Fail
button Send new email	1.23:1	4.5:1	#000000	#1A1A2E	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.

Heading Hierarchy

10 headings, 1 skip(s)

PASS

10 headings, 1 skip(s)

Single H1 present

Heading level skipped: H1 → H3 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H1 Inbox
H3 Inbox skipped
H3 Send new email
H3 Confirm send / fee
H3 Log in / Register profile
H3 Read message
H3 Enter Profile Password
H4 Received memos
H3 Confirm live chat / fee
H3 Unlock live chat

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

A+

Heading Text Quality

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

PASS

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

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

A+

Alt Text Quality

No images

PASS

No images

No images on this page

No images on this page.

A+

Form Input Types

13 form control(s) checked, no type mismatches

PASS

13 form control(s) checked, no type mismatches

No input-type mismatches detected

Form Input Quality

1 input-semantic issue(s) across 13 form control(s)

PASS

1 input-semantic issue(s) across 13 form control(s)

3 password field(s) missing or with invalid `autocomplete`

Password managers fill / save passwords only when `autocomplete` is exactly `current-password` (login) or `new-password` (registration / change). Empty, `off`, `password`, or other values silently disable the manager UX. Sample: <input type="password">, <input type="password">, <input type="password">.

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

Iframe Accessibility

1/1 iframe(s) missing title; 0 placeholder(s)

PASS

1/1 iframe(s) missing title; 0 placeholder(s)

WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.

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

PASS

All 7 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: XPENV - Private Web3 Messenger

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name XPENV - Private Web3 Messenger ✓192×192 icon ✓512×512 icon ✓Start URL ./index.html ✓Display Mode standalone ✓

Name XPENV - Private Web3 Messenger Display Mode standalone Theme Color #8ab4f8 Background Color #1a1a2e Icons 2 icon(s)

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.

Lighthouse Accessibility Audits

Score 94/100 — 1 failing, 15 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
Note: on some devices it may work only if you open this site inside the Freight… `div#root > div.splash-screen > div.splash-mobile-desktop-notice > p.splash-mobile-desktop-notice__muted`
Freighter app's built-in browser `div.splash-screen > div.splash-mobile-desktop-notice > p.splash-mobile-desktop-notice__muted > em`

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-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

●Buttons have an accessible name

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

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

●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

●Touch targets have sufficient size and spacing.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●The page contains a heading, skip link, or landmark region

○`[accesskey]` values are unique

○`[aria-*]` attributes match their roles

○`button`, `link`, and `menuitem` elements have accessible names

○ARIA attributes are used as specified for the element's role

○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 use only permitted ARIA attributes

○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

○`[aria-*]` attributes have valid values

○`[aria-*]` attributes are valid and not misspelled

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

○Heading elements appear in a sequentially-descending order

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Image elements have `[alt]` attributes

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