Skip to content
https://stelgano.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
62
GRADE
D
FIX
6
REVIEW
2
PASS
5
INFO
0
Checks
13
5 PASS 2 REVIEW 6 FIX
F
404 Error Page
Action
HTTP 404, bare page
FIX
HTTP 404, bare page
Info::
Correct 404 status code returned
Got: HTTP 404
Warning::
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 ✗
D
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
D
Web Manifest
Action
Not found
FIX
Not found
Info::
No web manifest found
No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
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.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
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 ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
2 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 2 <nav> element(s)
Back to Top
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.
B
Landmark Structure
4 landmarks
REVIEW
4 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
No banner (header) landmark
Warning::
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
BANNER (missing!) NAV MAIN CONTENTINFO footer

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

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

C
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
h2 Why sTELgano
1.05:1
#000000
on
#040818
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Feature Comparison
1.05:1
#000000
on
#040818
needs 3.0:1 (large text)
24px · bottom of viewport
h2 How it Works
1.05:1
#000000
on
#040818
needs 3.0:1 (large text)
24px · bottom of viewport
h2 The Core Invariant
1.05:1
#000000
on
#040818
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Security Model
1.05:1
#000000
on
#040818
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Use Cases
1.05:1
#000000
on
#040818
needs 3.0:1 (large text)
24px · bottom of viewport
h2 FAQ
1.05:1
#000000
on
#040818
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Under the Hood
1.05:1
#000000
on
#040818
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Privacy that doesn't advertise itself.
1.05:1
#000000
on
#040818
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Zero-Knowledge Architecture.
1.05:1
#000000
on
#040818
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Ephemeral Identity.
1.05:1
#000000
on
#040818
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Client-Side Cryptography.
1.05:1
#000000
on
#040818
needs 3.0:1 (large text)
19px · bottom of viewport
h3 How we stack up
1.05:1
#000000
on
#040818
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Three steps. Under a minute.
1.05:1
#000000
on
#040818
needs 3.0:1 (large text)
19px · bottom of viewport
h3 N=1 Messaging.
1.05:1
#000000
on
#040818
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Transparent about what we store.
1.05:1
#000000
on
#040818
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Built for people who need real discretio…
1.05:1
#000000
on
#040818
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Frequently Asked Questions.
1.05:1
#000000
on
#040818
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Serious cryptography. Simple interface.
1.05:1
#000000
on
#040818
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Open source. Auditable. Forkable.
1.05:1
#000000
on
#040818
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Why sTELgano1.05:13.0:1
#000000
#040818
Fail
h2 Feature Comparison1.05:13.0:1
#000000
#040818
Fail
h2 How it Works1.05:13.0:1
#000000
#040818
Fail
h2 The Core Invariant1.05:13.0:1
#000000
#040818
Fail
h2 Security Model1.05:13.0:1
#000000
#040818
Fail
h2 Use Cases1.05:13.0:1
#000000
#040818
Fail
h2 FAQ1.05:13.0:1
#000000
#040818
Fail
h2 Under the Hood1.05:13.0:1
#000000
#040818
Fail
h3 Privacy that doesn't…1.05:13.0:1
#000000
#040818
Fail
h3 Zero-Knowledge Archi…1.05:13.0:1
#000000
#040818
Fail
h3 Ephemeral Identity.1.05:13.0:1
#000000
#040818
Fail
h3 Client-Side Cryptogr…1.05:13.0:1
#000000
#040818
Fail
h3 How we stack up1.05:13.0:1
#000000
#040818
Fail
h3 Three steps. Under a…1.05:13.0:1
#000000
#040818
Fail
h3 N=1 Messaging.1.05:13.0:1
#000000
#040818
Fail
h3 Transparent about wh…1.05:13.0:1
#000000
#040818
Fail
h3 Built for people who…1.05:13.0:1
#000000
#040818
Fail
h3 Frequently Asked Que…1.05:13.0:1
#000000
#040818
Fail
h3 Serious cryptography…1.05:13.0:1
#000000
#040818
Fail
h3 Open source. Auditab…1.05:13.0:1
#000000
#040818
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
45 headings
PASS
45 headings
Info::
Single H1 present
  • H1 sTELgano
  • H2 Why sTELgano
  • H3 Privacy that doesn't advertise itself.
  • H3 Zero-Knowledge Architecture.
  • H4 Opaque by Default
  • H4 Untrusted Backend
  • H3 Ephemeral Identity.
  • H4 No Email, No Phone
  • H4 Memory-Only Sessions
  • H3 Client-Side Cryptography.
  • H4 Local Key Derivation
  • H4 End-to-End by Design
  • H2 Feature Comparison
  • H3 How we stack up against the rest.
  • H2 How it Works
  • H3 Three steps. Under a minute.
  • H4 Generate a Steg Number
  • H4 Choose Your PIN
  • H4 Open the Channel
  • H2 The Core Invariant
  • H3 N=1 Messaging.
  • H4 Instant Annihilation
  • H4 No Message History
  • H4 Zero Long-Term Liability
  • H2 Security Model
  • H3 Transparent about what we store.
  • H4 What the server stores
  • H4 What the server never sees
  • H2 Use Cases
  • H3 Built for people who need real discretion.
  • H4 Personal Privacy
  • H4 Confidential Sources
  • H4 Sensitive Coordination
  • H4 Cross-Border Communication
  • H2 FAQ
  • H3 Frequently Asked Questions.
  • H4 How does contact-layer steganography work?
  • H4 What happens to my messages?
  • H4 Can the server read my messages?
  • H4 If there's no account, how do I log in?
  • H4 What happens if I forget my PIN?
  • H2 Under the Hood
  • H3 Serious cryptography. Simple interface.
  • H3 Open source. Auditable. Forkable.
  • H3 Ready to connect privately?
A+
Alt Text Quality
All 8 images OK
PASS
All 8 images OK
Info::
8 image(s) with good alt text
8 images 8 good alt text
All images have appropriate alt text.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A+
Lighthouse Accessibility Audits
Score 96/100 — 1 failing, 22 passed
PASS
96

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
Incognito Mode recommended for maximum discretion. section.relative > div.grid > div.text-left > p.text-[10px]
No plaintext ever touches the backend. Even a full database breach reveals noth… ul.space-y-4 > li.flex > div > p.text-slate-500
The protocol is designed so you don't even have to trust us. The cryptography g… ul.space-y-4 > li.flex > div > p.text-slate-500
We don't want to know who you are. The system is designed to prevent us from ev… ul.space-y-4 > li.flex > div > p.text-slate-500
Session keys are kept strictly in volatile memory. Close the browser, and the e… ul.space-y-4 > li.flex > div > p.text-slate-500
Your encryption keys are derived from your PIN and the Steg Number using 600,00… ul.space-y-4 > li.flex > div > p.text-slate-500
Because the payload is encrypted with AES-256-GCM before it ever hits the netwo… ul.space-y-4 > li.flex > div > p.text-slate-500
The moment a reply is sent, the previous message is atomically wiped from the d… ul.space-y-6 > li.flex > div > p.text-slate-500
Because old messages are actively destroyed to make room for new ones, there is… ul.space-y-6 > li.flex > div > p.text-slate-500
Even if a server is physically seized or fully compromised, there is nothing to… ul.space-y-6 > li.flex > div > p.text-slate-500
Pro Tip: Use Incognito/Private Mode to ensure no local traces remain. div.w-full > section.px-6 > div.relative > p.text-xs
The secure channel platform hidden in your contacts. footer.px-6 > div.max-w-6xl > div.flex > p.text-slate-500
STEL·GAH·NO — STEGANOGRAPHY + TEL footer.px-6 > div.max-w-6xl > div.flex > p.text-slate-600
AGPL-3.0 div.max-w-6xl > div.flex > div.flex > div.px-2
BUILD 2026.04 div.max-w-6xl > div.flex > div.flex > div.px-2
© 2026 sTELgano Contributors footer.px-6 > div.max-w-6xl > div.flex > p.text-[9px]

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>`
●`[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
●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
●Touch targets have sufficient size and spacing.
●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●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.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Deprecated ARIA roles were not used
○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
○`[role]`s have all required `[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
○`[role]` values are valid
○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
○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.
○Skip links are focusable.
○No element has a `[tabindex]` value greater than 0
○`<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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback