Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

6 PASS 3 REVIEW 4 FIX

Favicon & Branding

Action

3 icon(s) detected

FIX

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

Apple touch icon present

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✓ Manifest Icons Present

✗ Multiple Sizes Missing

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: #5865f2

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

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

Action

2 landmarks

REVIEW

2 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

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

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page Not Found - SnipRelay ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Web Manifest

Valid manifest

REVIEW

Valid manifest

Name present: SnipRelay

No 192x192 icon

A 192px icon is required for PWA installation.

512x512 icon present

Display mode: standalone

PWA Install Criteria Not Installable

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

Name SnipRelay Display Mode standalone Theme Color #5865F2 Background Color #0f172a Icons 1 icon(s)

A+

Heading Hierarchy

20 headings

PASS

20 headings

Single H1 present

H1 Stop downloading video files manually.
H2 Why use SnipRelay?
H3 Seconds, not Minutes
H3 No "File Too Large" Errors
H3 Tied to your Identity
H2 Versatility
H2 Simple Pricing
H3 Free Starter
H3 Global Personal
H3 Server Premium
H4 Need a quick unlock?
H2 Common Questions
H2 Universal Support
H3 Privacy First
H3 Secure Payments
H3 Platform Compliant
H2 Ready to start clipping?
H3 Product
H3 Community
H3 Legal

A+

Alt Text Quality

All 7 images OK

PASS

All 7 images OK

7 image(s) with good alt text

7 images 7 good alt text

All images have appropriate alt text.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

A+

Link & Button Quality

42 links, 8 buttons — all OK

PASS

42 links, 8 buttons — all OK

42 link(s) with descriptive text

42 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

50 links and buttons have descriptive text

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 Stop downloading	20.07:1	3.0:1	#000000	#F8FAFC	Pass
h2 Why use SnipRelay?	18.49:1	3.0:1	#000000	#F0F0F5	Pass
h2 Versatility	18.49:1	3.0:1	#000000	#F0F0F5	Pass
h2 Simple Pricing	18.49:1	3.0:1	#000000	#F0F0F5	Pass
h2 Common Questions	18.49:1	3.0:1	#000000	#F0F0F5	Pass
h2 Universal Support	18.49:1	3.0:1	#000000	#F0F0F5	Pass
h2 Ready to start clipp…	18.49:1	3.0:1	#000000	#F0F0F5	Pass
h3 Seconds, not Minutes	18.49:1	3.0:1	#000000	#F0F0F5	Pass
h3 No "File Too Large" …	18.49:1	3.0:1	#000000	#F0F0F5	Pass
h3 Tied to your Identit…	18.49:1	3.0:1	#000000	#F0F0F5	Pass
h3 Free Starter	18.49:1	3.0:1	#000000	#F0F0F5	Pass
h3 Global Personal	18.49:1	3.0:1	#000000	#F0F0F5	Pass
h3 Server Premium	18.49:1	3.0:1	#000000	#F0F0F5	Pass
h3 Privacy First	18.49:1	3.0:1	#000000	#F0F0F5	Pass
h3 Secure Payments	18.49:1	3.0:1	#000000	#F0F0F5	Pass
h3 Platform Compliant	18.49:1	3.0:1	#000000	#F0F0F5	Pass
h3 Product	18.49:1	3.0:1	#000000	#F0F0F5	Pass
h3 Community	18.49:1	3.0:1	#000000	#F0F0F5	Pass
h3 Legal	18.49:1	3.0:1	#000000	#F0F0F5	Pass
title SnipRelay – Clip Y…	20.87:1	4.5:1	#000000	#FFFEFF	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 94/100 — 2 failing, 21 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
Telegram `div.flex > div.inline-flex > button#btn-telegram > span.flex`
($0.00 USD) `div.grid > div.flex > div.mb-6 > p.mt-1`
Discord `div.grid > div.flex > div.flex > span.py-1`
Telegram `div.grid > div.flex > div.flex > span.py-1`
CORE LIMITS `div.grid > div.flex > div.flex-grow > p.mb-4`
($5.44 USD) `div.grid > div.flex > div.mb-6 > p#usd-personal`
Telegram `div.grid > div.flex > div.flex > span.flex`
($10.89 USD) `div.grid > div.flex > div.mb-6 > p#usd-server`
per server `div.grid > div.flex > div.mb-6 > p.mt-1`
COMMUNITY BENEFITS `div.grid > div.flex > div.flex-grow > p.mb-4`
($2.17 USD) `div.mx-auto > div.flex > div.flex > span.text-xs`
YouTube `div.px-4 > div.grid > div.flex > span.text-xs`
Twitch `div.px-4 > div.grid > div.flex > span.text-xs`
TikTok `div.px-4 > div.grid > div.flex > span.text-xs`
X (Twitter) `div.px-4 > div.grid > div.flex > span.text-xs`
Instagram `div.px-4 > div.grid > div.flex > span.text-xs`
Reddit `div.px-4 > div.grid > div.flex > span.text-xs`
Facebook `div.px-4 > div.grid > div.flex > span.text-xs`
+10k `div.grid > div.flex > div.flex > span.text-xs`
Others `div.px-4 > div.grid > div.flex > span.text-xs`
Add to Telegram `section.overflow-hidden > div.relative > div.flex > a.inline-flex`
View Commands `section.overflow-hidden > div.relative > div.flex > a.text-indigo-200`
Read FAQ `section.overflow-hidden > div.relative > div.flex > a.text-indigo-200`
Get Support `section.overflow-hidden > div.relative > div.flex > a.text-indigo-200`

These are opportunities to improve the legibility of your content.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

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

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

●Heading elements appear in a sequentially-descending order

●Deprecated ARIA roles were not used

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

○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

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