Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

19 PASS 3 REVIEW 2 FIX

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

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)

1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 404: This page could not be found. ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

Dark-specific theme-color detected

A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.

prefers-color-scheme CSS detected in inline styles

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark Mode✓ Dark Mode Supported

color-scheme meta Not set ✗Dark theme-color #0d1117 ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

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 TikTok Story Viewer

1.08:1

#000000

#0A0D0C

needs 3.0:1 (large text)

32px · above the fold

h2 Why Choose Story Viewer?

1.13:1

#000000

#0A1513

needs 3.0:1 (large text)

24px · mid-page

h2 Powering Anonymous TikTok Viewing at Sca…

1.11:1

#000000

#111111

needs 3.0:1 (large text)

24px · bottom of viewport

h2 How It Works

1.11:1

#000000

#111111

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Built for Everyone Who Values Privacy

1.11:1

#000000

#111111

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Story Viewer vs. Other Tools

1.11:1

#000000

#111111

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Trusted by Thousands of Users Worldwide

1.11:1

#000000

#111111

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Frequently Asked Questions

1.11:1

#000000

#111111

needs 3.0:1 (large text)

24px · bottom of viewport

h3 100% Anonymous Viewing

1.10:1

#000000

#0A1110

needs 3.0:1 (large text)

19px · mid-page

h3 HD Downloads Without Watermark

1.07:1

#000000

#0A0B0B

needs 3.0:1 (large text)

19px · mid-page

h3 Lightning Fast

1.06:1

#000000

#0A0A0A

needs 3.0:1 (large text)

19px · mid-page

h3 No Login Required

1.06:1

#000000

#0A0A0A

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Stories & Videos

1.11:1

#000000

#111111

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Profile Pictures

1.11:1

#000000

#111111

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Works Worldwide

1.11:1

#000000

#111111

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Mobile Friendly

1.11:1

#000000

#111111

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Always Up-to-Date

1.11:1

#000000

#111111

needs 3.0:1 (large text)

19px · bottom of viewport

h3 View History

1.11:1

#000000

#111111

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Unlimited Usage

1.11:1

#000000

#111111

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Active Users

1.11:1

#000000

#111111

needs 3.0:1 (large text)

19px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 TikTok Story Viewer	1.08:1	3.0:1	#000000	#0A0D0C	Fail
h2 Why Choose Story Vie…	1.13:1	3.0:1	#000000	#0A1513	Fail
h2 Powering Anonymous T…	1.11:1	3.0:1	#000000	#111111	Fail
h2 How It Works	1.11:1	3.0:1	#000000	#111111	Fail
h2 Built for Everyone W…	1.11:1	3.0:1	#000000	#111111	Fail
h2 Story Viewer vs. Oth…	1.11:1	3.0:1	#000000	#111111	Fail
h2 Trusted by Thousands…	1.11:1	3.0:1	#000000	#111111	Fail
h2 Frequently Asked Que…	1.11:1	3.0:1	#000000	#111111	Fail
h3 100% Anonymous Viewi…	1.10:1	3.0:1	#000000	#0A1110	Fail
h3 HD Downloads Without…	1.07:1	3.0:1	#000000	#0A0B0B	Fail
h3 Lightning Fast	1.06:1	3.0:1	#000000	#0A0A0A	Fail
h3 No Login Required	1.06:1	3.0:1	#000000	#0A0A0A	Fail
h3 Stories & Videos	1.11:1	3.0:1	#000000	#111111	Fail
h3 Profile Pictures	1.11:1	3.0:1	#000000	#111111	Fail
h3 Works Worldwide	1.11:1	3.0:1	#000000	#111111	Fail
h3 Mobile Friendly	1.11:1	3.0:1	#000000	#111111	Fail
h3 Always Up-to-Date	1.11:1	3.0:1	#000000	#111111	Fail
h3 View History	1.11:1	3.0:1	#000000	#111111	Fail
h3 Unlimited Usage	1.11:1	3.0:1	#000000	#111111	Fail
h3 Active Users	1.11:1	3.0:1	#000000	#111111	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.

Landmark Structure

4 landmarks

PASS

4 landmarks

<main> landmark present

1 <nav> landmark(s) found

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

A+

Heading Hierarchy

33 headings

PASS

33 headings

Single H1 present

H1 TikTok Story Viewer View Anonymously
H2 Why Choose Story Viewer?
H3 100% Anonymous Viewing
H3 HD Downloads Without Watermark
H3 Lightning Fast
H3 No Login Required
H3 Stories & Videos
H3 Profile Pictures
H3 Works Worldwide
H3 Mobile Friendly
H3 Always Up-to-Date
H3 View History
H3 Unlimited Usage
H2 Powering Anonymous TikTok Viewing at Scale
H3 Active Users
H3 Videos Downloaded
H3 Stories Viewed
H3 Countries Served
H2 How It Works
H3 Find the Username
H3 Enter & Search
H3 View & Download
H2 Built for Everyone Who Values Privacy
H3 Content Creators & Influencers
H3 Marketing Professionals
H3 Researchers & Journalists
H3 Parents & Guardians
H3 Privacy-Conscious Users
H3 Business Analysts
H2 Story Viewer vs. Other Tools
H2 Trusted by Thousands of Users Worldwide
H2 Frequently Asked Questions
H3 Important Notice

A+

Heading Text Quality

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

PASS

All 33 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.

Form Accessibility

1 of 1 controls have issues

PASS

1 of 1 controls have issues

1 control(s) rely on placeholder only

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

Got: <input type="text">

1 controls

0 labeled

1 placeholder only

0 unlabeled

Control	Type	Label	Method
input	text	(Enter TikTok username or profile URL...)	placeholder only

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

Link & Button Quality

1 issue(s) across 4 links and 14 buttons

PASS

1 issue(s) across 4 links and 14 buttons

1 button(s) with no accessible text

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

Got: button.md:hidden (#56 on page)

4 link(s) with descriptive text

4 links

0 empty

0 generic text

0 new tab

1 empty buttons

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

17 links and buttons have descriptive text

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

button.md:hidden (#56 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

A+

Form Input Types

1 form control(s) checked, no type mismatches

PASS

1 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

1 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

No explicit tabindex attributes found

PASS

No explicit tabindex attributes found

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+

Mobile-Readable Font Sizes

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

PASS

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

All text uses legible mobile font sizes (>= 12 CSS px)

Favicon & Branding

7 icon(s) detected

PASS

7 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

SVG favicon detected — scales perfectly to any size

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✓ SVG Favicon Present

✓ Manifest Icons Present

✓ Multiple Sizes Present

A+

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: XTFetch - Social Media Downloader

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name XTFetch - Social Media Downloader ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode standalone ✓

Name XTFetch - Social Media Downloader Display Mode standalone Theme Color #58a6ff Background Color #0d1117 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 90/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.

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
header.fixed > div.max-w-7xl > div.flex > button.md:hidden `header.fixed > div.max-w-7xl > div.flex > button.md:hidden`
div.w-full > form > div.glow-input > button.bg-[#00f5d4] `div.w-full > form > div.glow-input > button.bg-[#00f5d4]`

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
View TikTok stories and profiles anonymously. Free, fast, and private. `div.max-w-7xl > div.flex > div.flex > p.text-gray-500`
© 2026 Story Viewer. All rights reserved. `footer.py-12 > div.max-w-7xl > div.mt-8 > p.text-gray-500`
Not affiliated with TikTok or ByteDance `footer.py-12 > div.max-w-7xl > div.mt-8 > p.text-gray-600`

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

●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

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

●Document has a main landmark.

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

○Image elements have `[alt]` attributes

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

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