Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

4 PASS 3 REVIEW 6 FIX

Landmark Structure

Action

1 landmarks

FIX

1 landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

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

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

Link & Button Quality

Action

19 issue(s) across 57 links and 38 buttons

FIX

19 issue(s) across 57 links and 38 buttons

16 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: /@gendarmerie_officiel; /@huynhvanthu96; /@emi6218; /@tteenlhair; /@parismatch; /@mum_of_esmee; /@tomjlvt; /@touradd; /@sashasouthside; /@thevalbarrios (+6 more)

1 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: https://www.tiktok.com/legal/update-on-irish-gdpr-decision ("here")

2 button(s) with no accessible text

40 link(s) with descriptive text

57 links

16 empty

1 generic text

0 new tab

2 empty buttons

Element	Text	Issue	Suggested Fix
/@gendarmerie_officiel	(empty)	empty	Add link text or aria-label
/@huynhvanthu96	(empty)	empty	Add link text or aria-label
/@emi6218	(empty)	empty	Add link text or aria-label
/@tteenlhair	(empty)	empty	Add link text or aria-label
/@parismatch	(empty)	empty	Add link text or aria-label
/@mum_of_esmee	(empty)	empty	Add link text or aria-label
/@tomjlvt	(empty)	empty	Add link text or aria-label
/@touradd	(empty)	empty	Add link text or aria-label
/@sashasouthside	(empty)	empty	Add link text or aria-label
/@thevalbarrios	(empty)	empty	Add link text or aria-label
/@lilouruel	(empty)	empty	Add link text or aria-label
/@onlymoviesfr	(empty)	empty	Add link text or aria-label
/@tteenlhair	(empty)	empty	Add link text or aria-label
/@gambi	(empty)	empty	Add link text or aria-label
/@kelskalapos	(empty)	empty	Add link text or aria-label
/@virgil1010	(empty)	empty	Add link text or aria-label
https://www.tiktok.com/legal/update-on-i…	here	generic text	Replace with descriptive text
Before: here Suggested: Update On Irish Gdpr Decision
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

76 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

/@gendarmerie_officiel; /@huynhvanthu96; /@emi6218; /@tteenlhair; /@parismatch; /@mum_of_esmee; /@tomjlvt; /@touradd; /@sashasouthside; /@thevalbarrios (+6 more)

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Generic link text like 'click here' doesn't describe the destination.

https://www.tiktok.com/legal/update-on-irish-gdpr-decision ("here")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

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-31pahd

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

No dark mode signals

FIX

No dark mode signals

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

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 ✗

Heading Hierarchy

9 headings

REVIEW

9 headings

No H1 heading found

Every page should have one H1 that describes the page content.

H2 For You
H2 Explore
H2 Following
H2 LIVE
H2 Profile
H3 Company
H3 Program
H3 Terms & Policies
H4 Remote-access “transfers of EEA User Data to China”: Update on Irish GDPR decision

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

Favicon & Branding

Action

7 icon(s) detected

REVIEW

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

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 16 fail WCAG AA

REVIEW

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

4 pass 16 fail WCAG AA

h3 Company

1.00:1

#000000

needs 3.0:1 (large text)

19px · mid-page

h3 Program

1.00:1

#000000

needs 3.0:1 (large text)

19px · mid-page

h3 Terms & Policies

1.00:1

#000000

needs 3.0:1 (large text)

19px · mid-page

title Explore - Find your favourite videos on …

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

button Skip to content feed

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

strong TikTok

1.00:1

#000000

needs 3.0:1 (large text)

16px · top of page (header area)

button Log in

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

strong TikTok

1.00:1

#000000

needs 3.0:1 (large text)

16px · above the fold

div Search

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

div For You

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

div Explore

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

div Following

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

div LIVE

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

div Upload

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

div Profile

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

div More

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h3 Company	1.00:1	3.0:1	#000000	#000000	Fail
h3 Program	1.00:1	3.0:1	#000000	#000000	Fail
h3 Terms & Policies	1.00:1	3.0:1	#000000	#000000	Fail
title Explore - Find your …	1.00:1	4.5:1	#000000	#000000	Fail
button Skip to content feed	1.00:1	4.5:1	#000000	#000000	Fail
strong TikTok	1.00:1	3.0:1	#000000	#000000	Fail
button Log in	1.00:1	4.5:1	#000000	#000000	Fail
strong TikTok	1.00:1	3.0:1	#000000	#000000	Fail
div Search	1.00:1	4.5:1	#000000	#000000	Fail
div For You	1.00:1	4.5:1	#000000	#000000	Fail
div Explore	1.00:1	4.5:1	#000000	#000000	Fail
div Following	1.00:1	4.5:1	#000000	#000000	Fail
div LIVE	1.00:1	4.5:1	#000000	#000000	Fail
div Upload	1.00:1	4.5:1	#000000	#000000	Fail
div Profile	1.00:1	4.5:1	#000000	#000000	Fail
div More	1.00:1	4.5:1	#000000	#000000	Fail
span © 2026 TikTok	7.00:1	4.5:1	#000000	#10A2C5	Pass
div All	7.00:1	4.5:1	#000000	#10A2C5	Pass
div Singing & Dancing	7.00:1	4.5:1	#000000	#10A2C5	Pass
div Comedy	7.00:1	4.5:1	#000000	#10A2C5	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.

Alt Text Quality

All 32 images OK

PASS

All 32 images OK

8 image(s) with alt text over 125 characters

16 decorative image(s) correctly marked

8 image(s) with good alt text

32 images 8 good alt text 16 decorative

Issue	Count
too long	8 image(s)

A+

Form Accessibility

All 1 controls labeled

PASS

All 1 controls labeled

1 control(s) properly labeled

1 controls

1 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
q	search	Search	aria-label

A+

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: TikTok

192x192 icon present

512x512 icon present

Display mode: minimal-ui

PWA Install Criteria ✓ Installable

Name TikTok ✓192×192 icon ✓512×512 icon ✓Start URL /foryou ✓Display Mode minimal-ui ✓

Name TikTok Display Mode minimal-ui Theme Color #ffffff Background Color #ffffff Icons 5 icon(s)

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.

ARIA

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
Remote-access “transfers of EEA User Data to China”: Update on Irish GDPR decis… `body.hidden > div#:r6: > div.TUXModal-overlay > div#:r4:`

These are opportunities to improve the usage of ARIA in your application which 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
Open TikTok `div.middle > div.css-i270b2-f59ed85f--DivGuideBtnContainer > div.matrix-smart-wrapper > button.css-fnrey4-f59ed85f--ButtonOpenTT`
Allow cookies from TikTok on this browser? `div.tiktok-cookie-banner > div.cookie-content > p.cookie-title`
Cookies Policy `div.tiktok-cookie-banner > div.cookie-content > p.cookie-desc > a`
Got it `div.css-1428ksb-f59ed85f--ButtonItem > button.TUXButton > div.TUXButton-content > div.TUXButton-label`

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

●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

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

●No element has a `[tabindex]` value greater than 0

●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

●Uses ARIA roles only on compatible elements

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

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

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

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