Skip to main content

TikTok tiktok.com

Screenshot of the TikTok home page

Accessibility score

0 out of 100, poorPoor±0 vs September

League position

9thof 10

Issues found

3

Audits passed

19

Accessibility score over time

weekly scans · last 6 months
  • Good · 90+
  • Needs improvement · 70–89
  • Poor · Below 70

This month's scan

Issues found

3Moderate
Document should have one main landmark

Every page should have exactly one main landmark that identifies the primary content. Without a main landmark, screen reader users must navigate through all content linearly to find what they're looking for, making page navigation difficult and time-consuming.

Learn more

Failing Elements

html
<html dir="ltr" lang="en">

Fix all of the following:

  • Document does not have a main landmark
Zooming and scaling must not be disabled

Setting user-scalable="no" or maximum-scale less than 2 prevents people with low vision from zooming to read content. Users who enlarge text in their browsers are blocked from making content readable, violating accessibility guidelines that require supporting at least 200% zoom.

Learn more

Failing Elements

meta[name="viewport"]
<meta name="viewport" content="width=device-width, initial-scale=1.0,
                                 maximum-scale=1.0, user-scalable=no">

Fix any of the following:

  • user-scalable=no on <meta> tag disables zooming on mobile devices
All page content should be contained by landmarks

Content should be organized within high-level landmark regions like <header>, <navigation>, <main>, and <footer>. Content outside these sections is difficult to find and its purpose may be unclear, making navigation inefficient for screen reader users who rely on landmarks to understand page structure.

Learn more

Failing Elements

#main-content
<div id="main-content">

Fix any of the following:

  • Some page content is not contained by landmarks
Passed audits19 across 1 page
<html> element must have a lang attribute

Screen readers need language information to switch between pronunciation libraries. Without a specified language, screen readers default to the user's preferred language, resulting in incorrect pronunciation that sounds like a strange accent and makes content difficult or impossible to understand.

Learn more

Audit Elements

html
<html dir="ltr" lang="en">
<html> element must have a valid value for the lang attribute

Screen readers use language-specific sound libraries for proper pronunciation. Invalid language attributes cause screen readers to use the wrong library, making text sound like a confusing accent or completely unintelligible, especially for multilingual users who access content in multiple languages.

Learn more

Audit Elements

html
<html dir="ltr" lang="en">
All page content should be contained by landmarks

Content should be organized within high-level landmark regions like <header>, <navigation>, <main>, and <footer>. Content outside these sections is difficult to find and its purpose may be unclear, making navigation inefficient for screen reader users who rely on landmarks to understand page structure.

Learn more

Audit Elements

#content
<div id="content">
#main-frame-error
<div id="main-frame-error" class="interstitial-wrapper ">
.icon-generic
<div class="icon icon-generic"></div>
#main-message
<div id="main-message">
h1
<h1>
            <span>Access to <span>www.tiktok.com</span> was denied</span>
          </h1>

Showing first 5 of 12 audited elements.

All touch targets must be 24px large, or leave sufficient space

Touch targets must be large enough or spaced far enough apart to be activated without accidentally hitting adjacent controls. This helps users on mobile devices, people with hand tremors or mobility impairments, users in shaking environments like public transit, and anyone using one hand or large fingers to interact with the interface.

Learn more

Audit Elements

#reload-button
<button id="reload-button" class="blue-button text-button" data-url="https://www.tiktok.com/">
              <!--?lit$580824833$-->Reload
            </button>
aria-hidden="true" must not be present on the document body

Setting <body aria-hidden="true" hides all page content from assistive technologies while leaving it visible on screen. This creates a confusing experience where keyboard users can still tab to elements, but screen readers remain completely silent, providing no information about what's focused.

Learn more

Audit Elements

body
<body class="neterror" style="font-family: "sans", Arial, sans-serif; font-size: 75%">
Buttons must have discernible text

Screen reader users cannot determine the purpose of buttons without an accessible name. Without a name, users don't know what action the button will perform when activated.

Learn more

Audit Elements

#reload-button
<button id="reload-button" class="blue-button text-button" data-url="https://www.tiktok.com/">
              <!--?lit$580824833$-->Reload
            </button>
Content must reflow without two-dimensional scrolling

People who zoom to 400% or use a narrow viewport must be able to scroll in one direction only. A layout that still requires horizontal scrolling at 320 CSS pixels forces magnified readers to pan left and right line by line, which makes the page close to unusable.

Learn more

Documents must have <title> element to aid in navigation

The page title is the first thing screen reader users hear when loading a page. Without a descriptive, unique title, users must read through the entire page to understand its contents and purpose, wasting valuable time on every page visit.

Learn more

Audit Elements

html
<html dir="ltr" lang="en">
Elements must meet minimum color contrast ratio thresholds

People with low vision or color blindness cannot read text that lacks sufficient contrast with its background. With nearly three times more people having low vision than total blindness, and 8% of men and 0.4% of women having color deficiencies, adequate contrast is essential for making text readable to millions of users.

Learn more

Audit Elements

h1 > span
<span>Access to <span>www.tiktok.com</span> was denied</span>
span > span
<span>www.tiktok.com</span>
p
<p>You don't have authorization to view this page.</p>
.error-code
<div class="error-code"><!--?lit$580824833$-->HTTP ERROR 403</div>
#reload-button
<button id="reload-button" class="blue-button text-button" data-url="https://www.tiktok.com/">
              <!--?lit$580824833$-->Reload
            </button>
Focused elements must not be entirely hidden by author-created content

Keyboard users have no pointer to show where they are. The focus indicator is their only cue, and a sticky header, footer, cookie banner, or other author-created overlay that completely hides the focused control strands them with no idea what will activate next.

Learn more

Audit Elements

#reload-button
<button id="reload-button" class="blue-button text-button" data-url="https://www.tiktok.com/">
Heading levels should only increase by one

Headings convey page structure for screen reader users the same way text size does for sighted users. Properly ordered headings (h1 through h6) allow screen reader users to quickly navigate and understand content structure, saving significant time and frustration while also improving search engine optimization.

Learn more

Audit Elements

h1
<h1>
            <span>Access to <span>www.tiktok.com</span> was denied</span>
          </h1>
Headings should not be empty

Screen readers announce headings to help users navigate page structure. Empty headings confuse users and prevent them from understanding the page's organization. Headings should only be used to convey structure, not for visual styling, and must contain accessible text that screen readers can announce.

Learn more

Audit Elements

h1
<h1>
            <span>Access to <span>www.tiktok.com</span> was denied</span>
          </h1>
Inline text spacing must be adjustable with custom stylesheets

Single-spaced text makes it difficult for people with cognitive disabilities to track lines while reading. Providing line spacing between 1.5 to 2 helps these users start a new line more easily after finishing the previous one.

Learn more

Audit Elements

body
<body class="neterror" style="font-family: "sans", Arial, sans-serif; font-size: 75%">
Interactive controls must not be nested

Nested interactive elements create empty tab stops where screen readers remain silent. When users tab to a focusable element inside another interactive control, they receive no information about its name, role, or state, creating a confusing and broken navigation experience.

Learn more

Audit Elements

#reload-button
<button id="reload-button" class="blue-button text-button" data-url="https://www.tiktok.com/">
              <!--?lit$580824833$-->Reload
            </button>
Interactive elements must have a visible focus indicator

Sighted keyboard users rely on a visible focus indicator to know where they are on the page. When focus styles are missing, too subtle, or have insufficient contrast against the surrounding colors, users cannot tell which element will respond when they press Enter or Space, making keyboard navigation slow and error-prone. This especially affects people with motor impairments who cannot use a mouse and people with low vision who need clear, high-contrast indicators.

Learn more

Audit Elements

#reload-button
<button id="reload-button" class="blue-button text-button" data-url="https://www.tiktok.com/">
Keyboard focus must be able to leave every component it can enter

Keyboard users move through a page with Tab, Shift+Tab, arrow keys and Escape. When focus enters a component and none of those keys lets it leave, the rest of the page becomes unreachable and the only way out is to reload or abandon it.

Learn more

Page should contain a level-one heading

Screen reader users use keyboard shortcuts to jump directly to the first h1, expecting to land at the main content. Without an h1 or with a misplaced one, users must listen to more of the page to understand its structure, wasting valuable time on every page visit.

Learn more

Audit Elements

html
<html dir="ltr" lang="en">
Text must remain readable when spacing is increased

People with low vision and dyslexia increase line height, letter spacing, word spacing, and paragraph spacing so they can read. Fixed-height boxes and overflow: hidden containers clip or overlap that text, which is a loss of content under WCAG 1.4.12.

Learn more

Users should be able to zoom and scale the text up to 500%

The user-scalable="no" and restrictive maximum-scale parameters prevent people with low vision from zooming to read content. Users who rely on browser zoom to enlarge text are blocked from accessing content at a readable size, violating their need to scale pages up to 5x zoom.

Learn more

Audit Elements

meta[name="viewport"]
<meta name="viewport" content="width=device-width, initial-scale=1.0,
                                 maximum-scale=1.0, user-scalable=no">

How does your site stack up against TikTok?

Run the same automated WCAG 2.2 checks we run on the scoreboard.

Free scan. No signup. See where you'd rank.

More in Social Media