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

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" id="register-password">, <input type="password" id="register-password-confirm">, <input type="password" id="profile-unlock-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" id="compose-gift-usd">, <input type="number" id="compose-charge-usd">, <input type="number" id="compose-expire-value">

404 Error Page

Action

HTTP 404, bare page

FIX

HTTP 404, bare page

Correct 404 status code returned

Got: HTTP 404

Bare server default 404 page

The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.

404 Page Quality Default 404 Page

Status Code HTTP 404 ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

2 navigation landmark(s) detected

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

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.

Landmark Structure

4 landmarks

REVIEW

4 landmarks

<main> landmark present

2 <nav> landmark(s) found

All <nav> elements are properly labeled

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

Form Input Quality

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

REVIEW

2 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" id="register-password">, <input type="password" id="register-password-confirm">, <input type="password" id="profile-unlock-password">.

2 login form field(s) missing `autocomplete=username` (or `email`)

On a page with a password input, the matching username / email field needs `autocomplete="username"` or `autocomplete="email"` -- otherwise the password manager can't identify which field carries the login identifier and silently skips autofill on the whole form. Sample: <input type="text" id="compose-field-to">, <input type="text" id="register-username">.

Tap Target Adequacy

3 tap target(s) too small or too close together

REVIEW

3 tap target(s) too small or too close together

3 tap target(s) too small or too close to neighbors

WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.

Favicon & Branding

Action

3 icon(s) detected

REVIEW

3 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

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 Missing

✓ 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 · bottom of viewport

h3 Privacy & data notice

1.18:1

#000000

#161628

needs 3.0:1 (large text)

19px · above the fold

h3 Inbox

1.23:1

#000000

#1A1A2E

needs 3.0:1 (large text)

19px · bottom of viewport

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)

a Privacy Policy

1.23:1

#000000

#1A1A2E

needs 4.5:1 (normal text)

16px · top of page (header area)

a Terms of Service

1.23:1

#000000

#1A1A2E

needs 4.5:1 (normal text)

16px · top of page (header area)

a FAQ

1.23:1

#000000

#1A1A2E

needs 4.5:1 (normal text)

16px · top of page (header area)

a Technical documentation

1.23:1

#000000

#1A1A2E

needs 4.5:1 (normal text)

16px · above the fold

a Sitemap

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

p Private Web3 Messenger

1.23:1

#000000

#1A1A2E

needs 4.5:1 (normal text)

16px · above the fold

button Enter Freighter Wallet

1.22:1

#000000

#19192D

needs 4.5:1 (normal text)

16px · above the fold

button Technical documentation

1.20:1

#000000

#18182B

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 Privacy & data notic…	1.18:1	3.0:1	#000000	#161628	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
a Privacy Policy	1.23:1	4.5:1	#000000	#1A1A2E	Fail
a Terms of Service	1.23:1	4.5:1	#000000	#1A1A2E	Fail
a FAQ	1.23:1	4.5:1	#000000	#1A1A2E	Fail
a Technical documentat…	1.23:1	4.5:1	#000000	#1A1A2E	Fail
a Sitemap	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 Enter Freighter Wall…	1.22:1	4.5:1	#000000	#19192D	Fail
button Technical documentat…	1.20:1	4.5:1	#000000	#18182B	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

11 headings, 1 skip(s)

PASS

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

H3 Privacy & data notice
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 11 heading(s) have substantive, well-formed text

PASS

All 11 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 Accessibility

All 13 controls labeled

PASS

All 13 controls labeled

13 control(s) properly labeled

13 controls

13 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#compose-field-to	text	To (username)	for/id
#compose-field-subject	text	Subject	for/id
#compose-field-message	textarea	Message	for/id
#compose-attachment-input	file	Choose file to attach	aria-label
#compose-gift-usd	number	Send money (USD · optional)	for/id
#compose-charge-usd	number	Request payment (USD · optional)	for/id
#compose-expire-value	number	Expires in	for/id
#compose-expire-unit	select	Unit	for/id
#register-username	text	Username	for/id
#register-password	password	Password	for/id
#register-password-confirm	password	Confirm Password	for/id
#profile-unlock-password	password	Password	for/id
#live-chat-profile-unlock-pw	password	Profile password	for/id

Link & Button Quality

8 links, 34 buttons — all OK

PASS

8 links, 34 buttons — all OK

8 link(s) open in new tab without warning

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

Got: https://xpenv.com/privacy-policy-en.html; https://xpenv.com/terms-of-service-en.html; https://xpenv.com/xpenv-faq-en.html; https://xpenv.com/xpenv-technical-documentation-en.html; https://xpenv.com/sitemap.xml; https://xpenv.com/privacy-policy-en.html; https://xpenv.com/terms-of-service-en.html; https://xpenv.com/sitemap.xml

8 links

0 empty

0 generic text

8 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://xpenv.com/privacy-policy-en.html	Privacy Policy	new tab	Add '(opens in new tab)' to text
https://xpenv.com/terms-of-service-en.ht…	Terms of Service	new tab	Add '(opens in new tab)' to text
https://xpenv.com/xpenv-faq-en.html	FAQ	new tab	Add '(opens in new tab)' to text
https://xpenv.com/xpenv-technical-docume…	Technical documentation	new tab	Add '(opens in new tab)' to text
https://xpenv.com/sitemap.xml	Sitemap	new tab	Add '(opens in new tab)' to text
https://xpenv.com/privacy-policy-en.html	Privacy	new tab	Add '(opens in new tab)' to text
https://xpenv.com/terms-of-service-en.ht…	Terms	new tab	Add '(opens in new tab)' to text
https://xpenv.com/sitemap.xml	Sitemap	new tab	Add '(opens in new tab)' to text

34 links and buttons have descriptive text

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

https://xpenv.com/privacy-policy-en.html; https://xpenv.com/terms-of-service-en.html; https://xpenv.com/xpenv-faq-en.html; https://xpenv.com/xpenv-technical-documentation-en.html; https://xpenv.com/sitemap.xml; https://xpenv.com/privacy-policy-en.html; https://xpenv.com/terms-of-service-en.html; https://xpenv.com/sitemap.xml

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

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

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+

Mobile-Readable Font Sizes

All 32 visible text node(s) render at >= 12 CSS pixels

PASS

All 32 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 92/100 — 2 failing, 22 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.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
FAQ `div#root > div.splash-screen > nav.splash-legal-bar > a`
Technical documentation `div#root > div.splash-screen > nav.splash-legal-bar > a`
Sitemap `div#root > div.splash-screen > nav.splash-legal-bar > a`

These items highlight common accessibility best practices.

○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

●`[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 are distinguishable without relying on color.

●Links have a discernible name

●Heading elements appear in a sequentially-descending order

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

●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

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

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