TikTok tiktok.com
Accessibility score
League position
9thof 10
Issues found
11
Audits passed
36
Accessibility score over time
weekly scans · last 6 months- Good · 90+
- Needs improvement · 70–89
- Poor · Below 70
This month's scan
Issues found
CriticalElements must only use supported ARIA attributes6 elements
Using ARIA attributes in roles where they're not allowed can disable accessibility for entire sections of your application. Invalid attribute-role combinations create conflicts that cause assistive technologies to report incorrect or nonsensical information about your interface.
Failing Elements
<div aria-expanded="false" aria-haspopup="dialog" class="css-1464rs-7937d88b--DivTriggerButtonWrapper e8wzh870">
Fix all of the following:
- ARIA attribute is not allowed: aria-expanded="false"
<div aria-expanded="false" aria-haspopup="dialog" style="width: 100%;">
Fix all of the following:
- ARIA attribute is not allowed: aria-expanded="false"
<button class="TUXButton TUXButton--default TUXButton--medium TUXButton--secondary css-1t1gyuu-7937d88b--StyledTUXNavButton eqhuzff0" aria-disabled="false" type="button" data-e2e="nav-more-menu" aria-label="More" role="listitem" aria-pressed="false">
Fix all of the following:
- ARIA attribute is not allowed: aria-pressed="false"
<div aria-expanded="false" aria-haspopup="dialog">
Fix all of the following:
- ARIA attribute is not allowed: aria-expanded="false"
<div aria-expanded="false" aria-haspopup="dialog">
Fix all of the following:
- ARIA attribute is not allowed: aria-expanded="false"
<div aria-expanded="false" aria-haspopup="dialog" style="position: fixed; left: 0px; top: 0px;"></div>
Fix all of the following:
- ARIA attribute is not allowed: aria-expanded="false"
CriticalCertain ARIA roles must be contained by particular parents9 elements
ARIA roles with missing required parent elements cannot function as intended for assistive technology users. Parent-child relationships convey essential hierarchy and context, like showing where an item sits within a tree structure. Without proper parents, this critical relationship information is lost.
Failing Elements
<button class="TUXButton TUXButton--default TUXButton--medium TUXButton--secondary css-1nj9u0d-7937d88b--StyledTUXNavButton eqhuzff0" aria-disabled="false" type="button" aria-label="For You" role="listitem">
Fix any of the following:
- Required ARIA parent role not present: list
<button class="TUXButton TUXButton--default TUXButton--medium TUXButton--secondary css-1t1gyuu-7937d88b--StyledTUXNavButton eqhuzff0" aria-disabled="false" type="button" aria-label="Shop" role="listitem">
Fix any of the following:
- Required ARIA parent role not present: list
<button class="TUXButton TUXButton--default TUXButton--medium TUXButton--secondary css-1t1gyuu-7937d88b--StyledTUXNavButton eqhuzff0" aria-disabled="false" type="button" aria-label="Explore" role="listitem">
Fix any of the following:
- Required ARIA parent role not present: list
<button class="TUXButton TUXButton--default TUXButton--medium TUXButton--secondary css-1t1gyuu-7937d88b--StyledTUXNavButton eqhuzff0" aria-disabled="false" type="button" aria-label="Following" role="listitem">
Fix any of the following:
- Required ARIA parent role not present: list
<button class="TUXButton TUXButton--default TUXButton--medium TUXButton--secondary css-1t1gyuu-7937d88b--StyledTUXNavButton eqhuzff0" aria-disabled="false" type="button" aria-label="Short dramas" role="listitem">
Fix any of the following:
- Required ARIA parent role not present: list
<button class="TUXButton TUXButton--default TUXButton--medium TUXButton--secondary css-1t1gyuu-7937d88b--StyledTUXNavButton eqhuzff0" aria-disabled="false" type="button" aria-label="LIVE" role="listitem">
Fix any of the following:
- Required ARIA parent role not present: list
<button class="TUXButton TUXButton--default TUXButton--medium TUXButton--secondary css-1t1gyuu-7937d88b--StyledTUXNavButton eqhuzff0" aria-disabled="false" type="button" aria-label="Upload" role="listitem">
Fix any of the following:
- Required ARIA parent role not present: list
<button class="TUXButton TUXButton--default TUXButton--medium TUXButton--secondary css-1t1gyuu-7937d88b--StyledTUXNavButton eqhuzff0" aria-disabled="false" type="button" aria-label="Profile" role="listitem">
Fix any of the following:
- Required ARIA parent role not present: list
<button class="TUXButton TUXButton--default TUXButton--medium TUXButton--secondary css-1t1gyuu-7937d88b--StyledTUXNavButton eqhuzff0" aria-disabled="false" type="button" data-e2e="nav-more-menu" aria-label="More" role="listitem" aria-pressed="false">
Fix any of the following:
- Required ARIA parent role not present: list
CriticalButtons must have discernible text14 elements
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.
Failing Elements
<button class="TUXButton TUXButton--capsule TUXButton--medium TUXButton--secondary eco3q8z0 action-item css-n6as00-7937d88b--StyledMoreMenuActionItem" aria-disabled="false" type="button" data-e2e="more-menu-icon" aria-expanded="false" data-tux-color-scheme="dark" aria-haspopup="dialog">
Fix any of the following:
- Element does not have inner text that is visible to screen readers
- aria-label attribute does not exist or is empty
- aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
- Element has no title attribute
- Element does not have an implicit (wrapped) <label>
- Element does not have an explicit <label>
- Element's default semantics were not overridden with role="none" or role="presentation"
<button class="elfe6iu1 css-co7ut0-7937d88b--Button-7937d88b--StyledAvatarFollowButton e11yjflg0" shape="capsule" data-e2e="feed-follow">
Fix any of the following:
- Element does not have inner text that is visible to screen readers
- aria-label attribute does not exist or is empty
- aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
- Element has no title attribute
- Element does not have an implicit (wrapped) <label>
- Element does not have an explicit <label>
- Element's default semantics were not overridden with role="none" or role="presentation"
<button type="button" class="tux-button__element__ZBq38f_v1_8_0" data-testid="tux-web-icon-button" style="padding-left: 0px; padding-right: 0px;">
Fix any of the following:
- Element does not have inner text that is visible to screen readers
- aria-label attribute does not exist or is empty
- aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
- Element has no title attribute
- Element does not have an implicit (wrapped) <label>
- Element does not have an explicit <label>
- Element's default semantics were not overridden with role="none" or role="presentation"
<button type="button" class="tux-button__element__ZBq38f_v1_8_0" data-testid="tux-web-icon-button" style="padding-left: 0px; padding-right: 0px;">
Fix any of the following:
- Element does not have inner text that is visible to screen readers
- aria-label attribute does not exist or is empty
- aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
- Element has no title attribute
- Element does not have an implicit (wrapped) <label>
- Element does not have an explicit <label>
- Element's default semantics were not overridden with role="none" or role="presentation"
<button type="button" class="tux-button__element__ZBq38f_v1_8_0" data-testid="tux-web-icon-button" style="padding-left: 0px; padding-right: 0px;">
Fix any of the following:
- Element does not have inner text that is visible to screen readers
- aria-label attribute does not exist or is empty
- aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
- Element has no title attribute
- Element does not have an implicit (wrapped) <label>
- Element does not have an explicit <label>
- Element's default semantics were not overridden with role="none" or role="presentation"
<button type="button" class="tux-button__element__ZBq38f_v1_8_0" data-testid="tux-web-icon-button" style="padding-left: 0px; padding-right: 0px;">
Fix any of the following:
- Element does not have inner text that is visible to screen readers
- aria-label attribute does not exist or is empty
- aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
- Element has no title attribute
- Element does not have an implicit (wrapped) <label>
- Element does not have an explicit <label>
- Element's default semantics were not overridden with role="none" or role="presentation"
<button class="TUXButton TUXButton--capsule TUXButton--medium TUXButton--secondary eco3q8z0 action-item css-n6as00-7937d88b--StyledMoreMenuActionItem" aria-disabled="false" type="button" data-e2e="more-menu-icon" aria-expanded="false" data-tux-color-scheme="dark" aria-haspopup="dialog">
Fix any of the following:
- Element does not have inner text that is visible to screen readers
- aria-label attribute does not exist or is empty
- aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
- Element has no title attribute
- Element does not have an implicit (wrapped) <label>
- Element does not have an explicit <label>
- Element's default semantics were not overridden with role="none" or role="presentation"
<button class="elfe6iu1 css-co7ut0-7937d88b--Button-7937d88b--StyledAvatarFollowButton e11yjflg0" shape="capsule" data-e2e="feed-follow">
Fix any of the following:
- Element does not have inner text that is visible to screen readers
- aria-label attribute does not exist or is empty
- aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
- Element has no title attribute
- Element does not have an implicit (wrapped) <label>
- Element does not have an explicit <label>
- Element's default semantics were not overridden with role="none" or role="presentation"
<button type="button" class="tux-button__element__ZBq38f_v1_8_0" data-testid="tux-web-icon-button" style="padding-left: 0px; padding-right: 0px;">
Fix any of the following:
- Element does not have inner text that is visible to screen readers
- aria-label attribute does not exist or is empty
- aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
- Element has no title attribute
- Element does not have an implicit (wrapped) <label>
- Element does not have an explicit <label>
- Element's default semantics were not overridden with role="none" or role="presentation"
<button type="button" class="tux-button__element__ZBq38f_v1_8_0" data-testid="tux-web-icon-button" style="padding-left: 0px; padding-right: 0px;">
Fix any of the following:
- Element does not have inner text that is visible to screen readers
- aria-label attribute does not exist or is empty
- aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
- Element has no title attribute
- Element does not have an implicit (wrapped) <label>
- Element does not have an explicit <label>
- Element's default semantics were not overridden with role="none" or role="presentation"
Showing first 10 of 14 failing elements.
SeriousElements must meet minimum color contrast ratio thresholds8 elements
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.
Failing Elements
<div class="TUXButton-label">Search</div>
Fix any of the following:
- Element has insufficient color contrast of 2.33 (foreground color: #a0a0a0, background color: #f2f2f2, font size: 10.5pt (14px), font weight: normal). Expected contrast ratio of 4.5:1
<div class="TUXButton-label">For You</div>
Fix any of the following:
- Element has insufficient color contrast of 3.68 (foreground color: #fe2c55, background color: #ffffff, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1
<div class="TUXButton-label">Log in</div>
Fix any of the following:
- Element has insufficient color contrast of 3.68 (foreground color: #ffffff, background color: #fe2c55, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1
<h3 class="css-107c00v-7937d88b--H4LinkListHeader ekchpq58">Company</h3>
Fix any of the following:
- Element has insufficient color contrast of 3.35 (foreground color: #8b8c91, background color: #ffffff, font size: 11.3pt (15px), font weight: bold). Expected contrast ratio of 4.5:1
<h3 class="css-s3tddi-7937d88b--H4LinkListHeader ekchpq58">Program</h3>
Fix any of the following:
- Element has insufficient color contrast of 3.35 (foreground color: #8b8c91, background color: #ffffff, font size: 11.3pt (15px), font weight: bold). Expected contrast ratio of 4.5:1
<h3 class="css-s3tddi-7937d88b--H4LinkListHeader ekchpq58">Terms & Policies</h3>
Fix any of the following:
- Element has insufficient color contrast of 3.35 (foreground color: #8b8c91, background color: #ffffff, font size: 11.3pt (15px), font weight: bold). Expected contrast ratio of 4.5:1
<span data-e2e="copyright" class="css-1l13mxl-7937d88b--SpanCopyright ekchpq51">© 2026 TikTok</span>
Fix any of the following:
- Element has insufficient color contrast of 3.35 (foreground color: #8b8c91, background color: #ffffff, font size: 9.0pt (12px), font weight: normal). Expected contrast ratio of 4.5:1
<div class="TUXButton-label">Log in</div>
Fix any of the following:
- Element has insufficient color contrast of 3.68 (foreground color: #ffffff, background color: #fe2c55, font size: 11.3pt (15px), font weight: normal). Expected contrast ratio of 4.5:1
SeriousInteractive controls must not be nested8 elements
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.
Failing Elements
<div role="button" tabindex="0" aria-label="Like video 25.6M likes" aria-pressed="false" data-e2e="like-icon" class="css-11wvys0-7937d88b--ButtonActionItemV1 e12fjiyr3">
Fix any of the following:
- Element has focusable descendants
<div role="button" tabindex="0" aria-label="Read or add comments 248.1K comments" data-e2e="comment-icon" class="css-11wvys0-7937d88b--ButtonActionItemV1 e12fjiyr3">
Fix any of the following:
- Element has focusable descendants
<div role="button" tabindex="0" aria-label="Add to Favorites. 2M added to Favorites" data-e2e="favorite-icon" class="css-11wvys0-7937d88b--ButtonActionItemV1 e12fjiyr3">
Fix any of the following:
- Element has focusable descendants
<div role="button" tabindex="0" aria-label="Share video 3.3M shares" aria-expanded="false" data-e2e="share-icon" class="css-11wvys0-7937d88b--ButtonActionItemV1 e12fjiyr3">
Fix any of the following:
- Element has focusable descendants
<div role="button" tabindex="0" aria-label="Like video 1.6M likes" aria-pressed="false" data-e2e="like-icon" class="css-11wvys0-7937d88b--ButtonActionItemV1 e12fjiyr3">
Fix any of the following:
- Element has focusable descendants
<div role="button" tabindex="0" aria-label="Read or add comments 9374 comments" data-e2e="comment-icon" class="css-11wvys0-7937d88b--ButtonActionItemV1 e12fjiyr3">
Fix any of the following:
- Element has focusable descendants
<div role="button" tabindex="0" aria-label="Add to Favorites. 118K added to Favorites" data-e2e="favorite-icon" class="css-11wvys0-7937d88b--ButtonActionItemV1 e12fjiyr3">
Fix any of the following:
- Element has focusable descendants
<div role="button" tabindex="0" aria-label="Share video 39.7K shares" aria-expanded="false" data-e2e="share-icon" class="css-11wvys0-7937d88b--ButtonActionItemV1 e12fjiyr3">
Fix any of the following:
- Element has focusable descendants
SeriousContent must reflow without two-dimensional scrolling58 elements
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.
Failing Elements
<button aria-label="Close toast" data-disabled="false" data-close-button="true" class="inapp-notif__close">
<main id="main-content-homepage_hot" class="css-qelder-7937d88b--DivMainContainer er8k1k70">
<div id="column-list-container" class="css-acgxju-7937d88b--DivColumnListContainer e3bfsj...">
<article id="one-column-item-0" data-scroll-index="0" shape="vertical" data-e2e="recommend-list-item-container" class="css-6wvhtq-7937d88b--ArticleItemContainer ehcbpkw0" style="">
<div class="css-1gp40pd-7937d88b--DivContentFlexLayout ehcbpkw...">
<section id="media-card-0" shape="vertical" tabindex="0" aria-label="Watch in full screen" data-e2e="feed-video" class="css-dv33hf-7937d88b--SectionMediaCardContainer ezf...">
<div class="css-bfblgq-7937d88b--BasePlayerContainer-7937d88b-...">
<div mode="0" class="css-1umd7qg-7937d88b--DivContainer e1sq7r4z0" style="border-radius: 16px;">
<div class="css-16s6atg-7937d88b--Box etuqjjj0">
<div class="css-10wzcli-7937d88b--DivBasicPlayerWrapper e1sq7r...">
Showing first 10 of 58 failing elements.
SeriousText must remain readable when spacing is increased3 elements
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.
Failing Elements
<span class="TUXText TUXText--tiktok-sans css-u0d6t3-7937d88b--..." letter-spacing="0.09380000000000001" data-e2e="desc-span-0" style="color: inherit; font-size: 14px; display: inline-b...">
<p class="TUXText TUXText--tiktok-sans ew21clu2 css-143w6dm-..." letter-spacing="0.09380000000000001" style="color: var(--ui-text-1); font-size: 14px; directio...">
<button type="button" height="18" class="css-1v8o1b4-7937d88b--ButtonExpand-7937d88b--Style...">
ModerateLandmarks should have a unique role or role/label/title (i.e. accessible name) combination1 element
Each landmark on a page must have either a unique role or a unique accessible name. Duplicate landmarks confuse screen reader users about which section they're navigating to, making it difficult to efficiently move through the page structure.
Failing Elements
<section id="media-card-0" shape="vertical" tabindex="0" aria-label="Watch in full screen" data-e2e="feed-video" class="css-dv33hf-7937d88b--SectionMediaCardContainer ezfgn9c0">
Fix any of the following:
- The landmark must have a unique aria-label, aria-labelledby, or title to make landmarks distinguishable
ModeratePage should contain a level-one heading1 element
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.
Failing Elements
<html lang="en" data-tux-color-scheme="light" dir="ltr" data-theme="light" data-rh="lang,data-theme">
Fix all of the following:
- Page must have a level-one heading
ModerateAll page content should be contained by landmarks4 elements
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.
Failing Elements
<a data-e2e="tiktok-logo" aria-label="Go to TikTok For You feed" class="css-1g8z8e3-7937d88b--StyledLinkLogo e1m2fri00 link-a11y-focus" href="/" style="position: relative;">
Fix any of the following:
- Some page content is not contained by landmarks
<div class="css-pfg1ov-7937d88b--DivSearchWrapper e15mfzh74">
Fix any of the following:
- Some page content is not contained by landmarks
<div class="css-tfue59-7937d88b--DivMainNavContainer eqhuzff6">
Fix any of the following:
- Some page content is not contained by landmarks
<div class="css-1gvgfgc-7937d88b--SubMainNavFooterContainer e15mfzh79">
Fix any of the following:
- Some page content is not contained by landmarks
MinorARIA role should be appropriate for the element10 elements
Invalid ARIA role and HTML element combinations can break accessibility for entire sections of your application. When roles are used incorrectly, assistive technologies may report confusing or nonsensical information to users, making it impossible for them to understand and interact with the interface properly.
Failing Elements
<button class="TUXButton TUXButton--capsule TUXButton--medium TUXButton--secondary css-15kigdg-7937d88b--StyledTUXSearchButton eqhuzff9" aria-disabled="false" type="button" data-e2e="nav-search" aria-label="Search" role="searchbox">
Fix any of the following:
- ARIA role searchbox is not allowed for given element
<button class="TUXButton TUXButton--default TUXButton--medium TUXButton--secondary css-1nj9u0d-7937d88b--StyledTUXNavButton eqhuzff0" aria-disabled="false" type="button" aria-label="For You" role="listitem">
Fix any of the following:
- ARIA role listitem is not allowed for given element
<button class="TUXButton TUXButton--default TUXButton--medium TUXButton--secondary css-1t1gyuu-7937d88b--StyledTUXNavButton eqhuzff0" aria-disabled="false" type="button" aria-label="Shop" role="listitem">
Fix any of the following:
- ARIA role listitem is not allowed for given element
<button class="TUXButton TUXButton--default TUXButton--medium TUXButton--secondary css-1t1gyuu-7937d88b--StyledTUXNavButton eqhuzff0" aria-disabled="false" type="button" aria-label="Explore" role="listitem">
Fix any of the following:
- ARIA role listitem is not allowed for given element
<button class="TUXButton TUXButton--default TUXButton--medium TUXButton--secondary css-1t1gyuu-7937d88b--StyledTUXNavButton eqhuzff0" aria-disabled="false" type="button" aria-label="Following" role="listitem">
Fix any of the following:
- ARIA role listitem is not allowed for given element
<button class="TUXButton TUXButton--default TUXButton--medium TUXButton--secondary css-1t1gyuu-7937d88b--StyledTUXNavButton eqhuzff0" aria-disabled="false" type="button" aria-label="Short dramas" role="listitem">
Fix any of the following:
- ARIA role listitem is not allowed for given element
<button class="TUXButton TUXButton--default TUXButton--medium TUXButton--secondary css-1t1gyuu-7937d88b--StyledTUXNavButton eqhuzff0" aria-disabled="false" type="button" aria-label="LIVE" role="listitem">
Fix any of the following:
- ARIA role listitem is not allowed for given element
<button class="TUXButton TUXButton--default TUXButton--medium TUXButton--secondary css-1t1gyuu-7937d88b--StyledTUXNavButton eqhuzff0" aria-disabled="false" type="button" aria-label="Upload" role="listitem">
Fix any of the following:
- ARIA role listitem is not allowed for given element
<button class="TUXButton TUXButton--default TUXButton--medium TUXButton--secondary css-1t1gyuu-7937d88b--StyledTUXNavButton eqhuzff0" aria-disabled="false" type="button" aria-label="Profile" role="listitem">
Fix any of the following:
- ARIA role listitem is not allowed for given element
<button class="TUXButton TUXButton--default TUXButton--medium TUXButton--secondary css-1t1gyuu-7937d88b--StyledTUXNavButton eqhuzff0" aria-disabled="false" type="button" data-e2e="nav-more-menu" aria-label="More" role="listitem" aria-pressed="false">
Fix any of the following:
- ARIA role listitem is not allowed for given element
Passed audits36 across 1 page
<html> element must have a lang attribute1 element
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.
Audit Elements
<html lang="en" data-tux-color-scheme="light" dir="ltr" data-theme="light" data-rh="lang,data-theme">
<html> element must have a valid value for the lang attribute1 element
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.
Audit Elements
<html lang="en" data-tux-color-scheme="light" dir="ltr" data-theme="light" data-rh="lang,data-theme">
<li> elements must be contained in a <ul> or <ol>1 element
Lists require proper semantic hierarchy with ul or ol parent elements and li child elements. This structure allows screen readers to announce when users enter a list, how many items it contains, and which item they're currently on, providing essential context for understanding the content.
Audit Elements
<li tabindex="0" class="inapp-notif__item" data-sonner-toast="" data-styled="true" data-mounted="true" data-promise="false" data-swiped="false" data-removed="false" data-visible="true" data-y-position="bottom" data-x-position="right" data-index="0" data-front="true" data-swiping="false" ...>
<ul> and <ol> must only directly contain <li>, <script> or <template> elements1 element
Lists must contain only li elements as direct children (besides non-content elements like script or style). When other content elements appear within ul or ol tags, screen readers cannot properly inform users they're listening to list items, breaking the expected list navigation experience.
Audit Elements
<ol dir="ltr" tabindex="-1" class="css-1k3egxz" data-sonner-toaster="true" data-theme="light" data-y-position="bottom" data-lifted="false" data-x-position="right" style="--front-toast-height...">
All page content should be contained by landmarks469 elements
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.
Audit Elements
<svg style="position:absolute;width:0;height:0" id="svg-sprite-container"></svg>
<div id="app" style="min-height: 100vh; display: flex; flex-direction: column; justify-content: flex-start" data-csr="1">
<section aria-label="Notifications alt+T" tabindex="-1" aria-live="polite" aria-relevant="additions text" aria-atomic="false">
<ol dir="ltr" tabindex="-1" class="css-1k3egxz" data-sonner-toaster="true" data-theme="light" data-y-position="bottom" data-lifted="false" data-x-position="right" style="--front-toast-height...">
<li tabindex="0" class="inapp-notif__item" data-sonner-toast="" data-styled="true" data-mounted="true" data-promise="false" data-swiped="false" data-removed="false" data-visible="true" data-y-position="bottom" data-x-position="right" data-index="0" data-front="true" data-swiping="false" ...>
Showing first 5 of 469 audited elements.
Alternative text of images should not be repeated as text4 elements
Duplicating alternative text adjacent to an image or link forces screen readers to announce the same information twice. This redundancy is unnecessary and confusing, especially when image buttons repeat their labels in nearby text.
Audit Elements
<img alt="i’m scared" fetchpriority="high" decoding="async" srcset="https://p16-common-s..." src="https://p16-common-s..." imagex-type="react" imagex-version="0.3.10" data-fmp="true" style="position: absolute; ...">
<img loading="lazy" alt="jul.spamz.fr" src="https://p16-common-s..." class="css-10s4roi-7937d88b...">
<img alt="Paper Towel Mystery ..." fetchpriority="high" decoding="async" src="data:image/gif;base6..." imagex-type="react" imagex-version="0.3.10" style="position: absolute; ...">
<img loading="lazy" alt="little_bros_games" src="https://p19-common-s..." class="css-10s4roi-7937d88b...">
ARIA attributes must be used as specified for the element's role52 elements
Using ARIA attributes where they're not expected causes unpredictable behavior in assistive technologies. Following the ARIA specification ensures that screen readers and other tools can properly interpret and communicate your content's meaning to people with disabilities.
Audit Elements
<section aria-label="Notifications alt+T" tabindex="-1" aria-live="polite" aria-relevant="additions text" aria-atomic="false">
<button aria-label="Close toast" data-disabled="false" data-close-button="true" class="inapp-notif__close">
<a data-e2e="tiktok-logo" aria-label="Go to TikTok For You feed" class="css-1g8z8e3-7937d88b--StyledLinkLogo e1m2fri00 link-a11y-focus" href="/" style="position: relative;">
<div role="button" aria-label="Collapse sidebar" tabindex="0" aria-expanded="false" aria-haspopup="dialog" class="css-1fisppo-7937d88b--DivToggleTrigger e1hzmt9p0">
<button class="TUXButton TUXButton--capsule TUXButton--medium TUXButton--secondary css-15kigdg-7937d88b--StyledTUXSearchButton eqhuzff9" aria-disabled="false" type="button" data-e2e="nav-search" aria-label="Search" role="searchbox">
Showing first 5 of 52 audited elements.
ARIA attributes must conform to valid names52 elements
Misspelled or non-existent ARIA attributes cannot perform their intended accessibility function. Assistive technologies rely on correctly spelled, current ARIA attributes to convey proper user interface behaviors and structural information to people with disabilities.
Audit Elements
<section aria-label="Notifications alt+T" tabindex="-1" aria-live="polite" aria-relevant="additions text" aria-atomic="false">
<button aria-label="Close toast" data-disabled="false" data-close-button="true" class="inapp-notif__close">
<a data-e2e="tiktok-logo" aria-label="Go to TikTok For You feed" class="css-1g8z8e3-7937d88b--StyledLinkLogo e1m2fri00 link-a11y-focus" href="/" style="position: relative;">
<div role="button" aria-label="Collapse sidebar" tabindex="0" aria-expanded="false" aria-haspopup="dialog" class="css-1fisppo-7937d88b--DivToggleTrigger e1hzmt9p0">
<button class="TUXButton TUXButton--capsule TUXButton--medium TUXButton--secondary css-15kigdg-7937d88b--StyledTUXSearchButton eqhuzff9" aria-disabled="false" type="button" data-e2e="nav-search" aria-label="Search" role="searchbox">
Showing first 5 of 52 audited elements.
ARIA attributes must conform to valid values52 elements
ARIA attributes must contain correctly spelled values that match the attribute's expected options. Invalid values prevent the accessibility feature from working, making content inaccessible to assistive technology users who depend on these attributes for navigation and interaction.
Audit Elements
<section aria-label="Notifications alt+T" tabindex="-1" aria-live="polite" aria-relevant="additions text" aria-atomic="false">
<button aria-label="Close toast" data-disabled="false" data-close-button="true" class="inapp-notif__close">
<a data-e2e="tiktok-logo" aria-label="Go to TikTok For You feed" class="css-1g8z8e3-7937d88b--StyledLinkLogo e1m2fri00 link-a11y-focus" href="/" style="position: relative;">
<div role="button" aria-label="Collapse sidebar" tabindex="0" aria-expanded="false" aria-haspopup="dialog" class="css-1fisppo-7937d88b--DivToggleTrigger e1hzmt9p0">
<button class="TUXButton TUXButton--capsule TUXButton--medium TUXButton--secondary css-15kigdg-7937d88b--StyledTUXSearchButton eqhuzff9" aria-disabled="false" type="button" data-e2e="nav-search" aria-label="Search" role="searchbox">
Showing first 5 of 52 audited elements.
ARIA commands must have an accessible name9 elements
Screen reader users cannot determine the purpose of interactive elements with role="link", role="button", or role="menuitem" that lack an accessible name. Without a name, these controls are essentially invisible to assistive technology users.
Audit Elements
<div role="button" aria-label="Collapse sidebar" tabindex="0" aria-expanded="false" aria-haspopup="dialog" class="css-1fisppo-7937d88b--DivToggleTrigger e1hzmt9p0">
<div role="button" tabindex="0" aria-label="Like video 25.6M likes" aria-pressed="false" data-e2e="like-icon" class="css-11wvys0-7937d88b--ButtonActionItemV1 e12fjiyr3">
<div role="button" tabindex="0" aria-label="Read or add comments 248.1K comments" data-e2e="comment-icon" class="css-11wvys0-7937d88b--ButtonActionItemV1 e12fjiyr3">
<div role="button" tabindex="0" aria-label="Add to Favorites. 2M added to Favorites" data-e2e="favorite-icon" class="css-11wvys0-7937d88b--ButtonActionItemV1 e12fjiyr3">
<div role="button" tabindex="0" aria-label="Share video 3.3M shares" aria-expanded="false" data-e2e="share-icon" class="css-11wvys0-7937d88b--ButtonActionItemV1 e12fjiyr3">
Showing first 5 of 9 audited elements.
ARIA input fields must have an accessible name2 elements
ARIA input fields with roles like combobox, listbox, searchbox, slider, spinbutton, and textbox must have accessible names. Without names, screen reader users cannot identify what information these fields expect or their purpose in the form.
Audit Elements
<div tabindex="0" role="slider" aria-label="Video progress" aria-valuenow="0.7225249085657284" aria-valuetext="00:04" class="css-1or1egi-7937d88b--DivProgressBarElapsed eer0cdn3"></div>
<div tabindex="0" role="slider" aria-label="Video progress" aria-valuenow="0" aria-valuetext="00:00" class="css-1or1egi-7937d88b--DivProgressBarElapsed eer0cdn3"></div>
ARIA role should be appropriate for the element14 elements
Invalid ARIA role and HTML element combinations can break accessibility for entire sections of your application. When roles are used incorrectly, assistive technologies may report confusing or nonsensical information to users, making it impossible for them to understand and interact with the interface properly.
Audit Elements
<div role="separator" class="tux-separator tux-separator-thin--vertical" style="background-color: var(--ui-shape-neutral-3);"></div>
<input placeholder="Search" name="q" type="search" autocomplete="off" role="combobox" aria-controls="" aria-label="Search" aria-expanded="false" aria-autocomplete="list" data-e2e="search-user-input" class="css-cnn5nr-7937d88b--InputElement e1vdpl643" value="">
<i id="header-more-menu-icon" tabindex="0" role="button" aria-label="Open settings menu" aria-expanded="false" aria-controls="" data-e2e="see-more-icon" class="css-1dosst1-7937d88b--IMoreIconWrapper e1ke3b1r3">
<div role="button" aria-label="Collapse sidebar" tabindex="0" aria-expanded="false" aria-haspopup="dialog" class="css-1fisppo-7937d88b--DivToggleTrigger e1hzmt9p0">
<div tabindex="0" role="slider" aria-label="Video progress" aria-valuenow="0.7225249085657284" aria-valuetext="00:04" class="css-1or1egi-7937d88b--DivProgressBarElapsed eer0cdn3"></div>
Showing first 5 of 14 audited elements.
ARIA roles used must conform to valid values22 elements
Invalid ARIA role values prevent assistive technologies from understanding and communicating the element's purpose to users. Without valid roles, screen readers cannot provide information about the element's features, properties, or how users should interact with it.
Audit Elements
<div role="separator" class="tux-separator tux-separator-thin--vertical" style="background-color: var(--ui-shape-neutral-3);"></div>
<div role="button" aria-label="Collapse sidebar" tabindex="0" aria-expanded="false" aria-haspopup="dialog" class="css-1fisppo-7937d88b--DivToggleTrigger e1hzmt9p0">
<button class="TUXButton TUXButton--capsule TUXButton--medium TUXButton--secondary css-15kigdg-7937d88b--StyledTUXSearchButton eqhuzff9" aria-disabled="false" type="button" data-e2e="nav-search" aria-label="Search" role="searchbox">
<button class="TUXButton TUXButton--default TUXButton--medium TUXButton--secondary css-1nj9u0d-7937d88b--StyledTUXNavButton eqhuzff0" aria-disabled="false" type="button" aria-label="For You" role="listitem">
<button class="TUXButton TUXButton--default TUXButton--medium TUXButton--secondary css-1t1gyuu-7937d88b--StyledTUXNavButton eqhuzff0" aria-disabled="false" type="button" aria-label="Shop" role="listitem">
Showing first 5 of 22 audited elements.
aria-hidden="true" must not be present on the document body1 element
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.
Audit Elements
<body style="margin: 0px;">
Buttons must have discernible text20 elements
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.
Audit Elements
<button aria-label="Close toast" data-disabled="false" data-close-button="true" class="inapp-notif__close">
<button class="TUXButton TUXButton--capsule TUXButton--medium TUXButton--secondary css-15kigdg-7937d88b--StyledTUXSearchButton eqhuzff9" aria-disabled="false" type="button" data-e2e="nav-search" aria-label="Search" role="searchbox">
<button class="TUXButton TUXButton--default TUXButton--medium TUXButton--secondary css-1nj9u0d-7937d88b--StyledTUXNavButton eqhuzff0" aria-disabled="false" type="button" aria-label="For You" role="listitem">
<button class="TUXButton TUXButton--default TUXButton--medium TUXButton--secondary css-1t1gyuu-7937d88b--StyledTUXNavButton eqhuzff0" aria-disabled="false" type="button" aria-label="Shop" role="listitem">
<button class="TUXButton TUXButton--default TUXButton--medium TUXButton--secondary css-1t1gyuu-7937d88b--StyledTUXNavButton eqhuzff0" aria-disabled="false" type="button" aria-label="Explore" role="listitem">
Showing first 5 of 20 audited elements.
Deprecated ARIA roles must not be used22 elements
Deprecated ARIA roles are not recognized by modern screen readers and assistive technologies. Using outdated roles means some users cannot access essential information or functionality on your site.
Audit Elements
<div role="separator" class="tux-separator tux-separator-thin--vertical" style="background-color: var(--ui-shape-neutral-3);"></div>
<div role="button" aria-label="Collapse sidebar" tabindex="0" aria-expanded="false" aria-haspopup="dialog" class="css-1fisppo-7937d88b--DivToggleTrigger e1hzmt9p0">
<button class="TUXButton TUXButton--capsule TUXButton--medium TUXButton--secondary css-15kigdg-7937d88b--StyledTUXSearchButton eqhuzff9" aria-disabled="false" type="button" data-e2e="nav-search" aria-label="Search" role="searchbox">
<button class="TUXButton TUXButton--default TUXButton--medium TUXButton--secondary css-1nj9u0d-7937d88b--StyledTUXNavButton eqhuzff0" aria-disabled="false" type="button" aria-label="For You" role="listitem">
<button class="TUXButton TUXButton--default TUXButton--medium TUXButton--secondary css-1t1gyuu-7937d88b--StyledTUXNavButton eqhuzff0" aria-disabled="false" type="button" aria-label="Shop" role="listitem">
Showing first 5 of 22 audited elements.
Document should have one main landmark1 element
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.
Audit Elements
<html lang="en" data-tux-color-scheme="light" dir="ltr" data-theme="light" data-rh="lang,data-theme">
Document should not have more than one main landmark1 element
Multiple main landmarks confuse screen reader users about where the primary content is located. Each page should have only one main landmark so users can quickly and predictably navigate to the primary content area.
Audit Elements
<main id="main-content-homepage_hot" class="css-qelder-7937d88b--DivMainContainer er8k1k70">
Documents must have <title> element to aid in navigation1 element
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.
Audit Elements
<html lang="en" data-tux-color-scheme="light" dir="ltr" data-theme="light" data-rh="lang,data-theme">
Elements must meet minimum color contrast ratio thresholds17 elements
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.
Audit Elements
<h4 class="TUXText TUXText--tiktok-sans TUXText--weight-medium css-15so7zd-7937d88b--StyledTUXText e1gw1eda0" letter-spacing="0.06" style="color: inherit; font-size: 15px;">TikTok Shop is now available on web!</h4>
<p class="TUXText TUXText--tiktok-sans e1b86o4g13 css-1e4khdc-7937d88b--StyledTUXText-7937d88b--TextNoticeMessage e1gw1eda0" letter-spacing="0.09380000000000001" style="color: inherit; font-size: 14px;">Browse your favorite items.</p>
<input placeholder="Search" name="q" type="search" autocomplete="off" role="combobox" aria-controls="" aria-label="Search" aria-expanded="false" aria-autocomplete="list" data-e2e="search-user-input" class="css-cnn5nr-7937d88b--InputElement e1vdpl643" value="">
<div class="TUXButton-label">Shop</div>
<div class="TUXButton-label">Explore</div>
Showing first 5 of 17 audited elements.
Elements must only use permitted ARIA attributes52 elements
Using prohibited ARIA attributes prevents important information from reaching assistive technology users. It also causes assistive technologies to behave inconsistently as they attempt to compensate for the error.
Audit Elements
<section aria-label="Notifications alt+T" tabindex="-1" aria-live="polite" aria-relevant="additions text" aria-atomic="false">
<button aria-label="Close toast" data-disabled="false" data-close-button="true" class="inapp-notif__close">
<a data-e2e="tiktok-logo" aria-label="Go to TikTok For You feed" class="css-1g8z8e3-7937d88b--StyledLinkLogo e1m2fri00 link-a11y-focus" href="/" style="position: relative;">
<div role="button" aria-label="Collapse sidebar" tabindex="0" aria-expanded="false" aria-haspopup="dialog" class="css-1fisppo-7937d88b--DivToggleTrigger e1hzmt9p0">
<button class="TUXButton TUXButton--capsule TUXButton--medium TUXButton--secondary css-15kigdg-7937d88b--StyledTUXSearchButton eqhuzff9" aria-disabled="false" type="button" data-e2e="nav-search" aria-label="Search" role="searchbox">
Showing first 5 of 52 audited elements.
Elements must only use supported ARIA attributes46 elements
Using ARIA attributes in roles where they're not allowed can disable accessibility for entire sections of your application. Invalid attribute-role combinations create conflicts that cause assistive technologies to report incorrect or nonsensical information about your interface.
Audit Elements
<section aria-label="Notifications alt+T" tabindex="-1" aria-live="polite" aria-relevant="additions text" aria-atomic="false">
<button aria-label="Close toast" data-disabled="false" data-close-button="true" class="inapp-notif__close">
<a data-e2e="tiktok-logo" aria-label="Go to TikTok For You feed" class="css-1g8z8e3-7937d88b--StyledLinkLogo e1m2fri00 link-a11y-focus" href="/" style="position: relative;">
<div role="button" aria-label="Collapse sidebar" tabindex="0" aria-expanded="false" aria-haspopup="dialog" class="css-1fisppo-7937d88b--DivToggleTrigger e1hzmt9p0">
<button class="TUXButton TUXButton--capsule TUXButton--medium TUXButton--secondary css-15kigdg-7937d88b--StyledTUXSearchButton eqhuzff9" aria-disabled="false" type="button" data-e2e="nav-search" aria-label="Search" role="searchbox">
Showing first 5 of 46 audited elements.
Elements should not have tabindex greater than zero32 elements
Using tabindex values greater than 0 creates unexpected tab orders that disorient users. It makes elements appear to be skipped when users tab past them, requires setting tabindex on every element to maintain order, and forces all tabindex items to be visited before any normal elements, breaking natural navigation flow.
Audit Elements
<section aria-label="Notifications alt+T" tabindex="-1" aria-live="polite" aria-relevant="additions text" aria-atomic="false">
<ol dir="ltr" tabindex="-1" class="css-1k3egxz" data-sonner-toaster="true" data-theme="light" data-y-position="bottom" data-lifted="false" data-x-position="right" style="--front-toast-height...">
<li tabindex="0" class="inapp-notif__item" data-sonner-toast="" data-styled="true" data-mounted="true" data-promise="false" data-swiped="false" data-removed="false" data-visible="true" data-y-position="bottom" data-x-position="right" data-index="0" data-front="true" data-swiping="false" ...>
<div role="button" aria-label="Collapse sidebar" tabindex="0" aria-expanded="false" aria-haspopup="dialog" class="css-1fisppo-7937d88b--DivToggleTrigger e1hzmt9p0">
<a data-e2e="nav-foryou" tabindex="-1" class="link-a11y-focus" href="/">
Showing first 5 of 32 audited elements.
Heading levels should only increase by one11 elements
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.
Audit Elements
<h4 class="TUXText TUXText--tiktok-sans TUXText--weight-medium css-15so7zd-7937d88b--StyledTUXText e1gw1eda0" letter-spacing="0.06" style="color: inherit; font-size: 15px;">TikTok Shop is now available on web!</h4>
<h2>
<h2>
<h2>
<h2>
Showing first 5 of 11 audited elements.
Headings should not be empty11 elements
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.
Audit Elements
<h4 class="TUXText TUXText--tiktok-sans TUXText--weight-medium css-15so7zd-7937d88b--StyledTUXText e1gw1eda0" letter-spacing="0.06" style="color: inherit; font-size: 15px;">TikTok Shop is now available on web!</h4>
<h2>
<h2>
<h2>
<h2>
Showing first 5 of 11 audited elements.
Images must have alternative text4 elements
Screen readers cannot translate images into text without alt attributes. Alternative text is essential for blind users and beneficial for users with low vision or color blindness, providing the same information that sighted users get from viewing the image.
Audit Elements
<img alt="i’m scared" fetchpriority="high" decoding="async" srcset="https://p16-common-s..." src="https://p16-common-s..." imagex-type="react" imagex-version="0.3.10" data-fmp="true" style="position: absolute; ...">
<img loading="lazy" alt="jul.spamz.fr" src="https://p16-common-s..." class="css-10s4roi-7937d88b...">
<img alt="Paper Towel Mystery ..." fetchpriority="high" decoding="async" src="data:image/gif;base6..." imagex-type="react" imagex-version="0.3.10" style="position: absolute; ...">
<img loading="lazy" alt="little_bros_games" src="https://p19-common-s..." class="css-10s4roi-7937d88b...">
Inline text spacing must be adjustable with custom stylesheets97 elements
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.
Audit Elements
<body style="margin: 0px;">
<div id="app" style="min-height: 100vh; display: flex; flex-direction: column; justify-content: flex-start" data-csr="1">
<ol dir="ltr" tabindex="-1" class="css-1k3egxz" data-sonner-toaster="true" data-theme="light" data-y-position="bottom" data-lifted="false" data-x-position="right" style="--front-toast-height...">
<li tabindex="0" class="inapp-notif__item" data-sonner-toast="" data-styled="true" data-mounted="true" data-promise="false" data-swiped="false" data-removed="false" data-visible="true" data-y-position="bottom" data-x-position="right" data-index="0" data-front="true" data-swiping="false" ...>
<h4 class="TUXText TUXText--tiktok-sans TUXText--weight-medium css-15so7zd-7937d88b--StyledTUXText e1gw1eda0" letter-spacing="0.06" style="color: inherit; font-size: 15px;">TikTok Shop is now available on web!</h4>
Showing first 5 of 97 audited elements.
Interactive controls must not be nested32 elements
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.
Audit Elements
<button aria-label="Close toast" data-disabled="false" data-close-button="true" class="inapp-notif__close">
<div role="separator" class="tux-separator tux-separator-thin--vertical" style="background-color: var(--ui-shape-neutral-3);"></div>
<div role="button" aria-label="Collapse sidebar" tabindex="0" aria-expanded="false" aria-haspopup="dialog" class="css-1fisppo-7937d88b--DivToggleTrigger e1hzmt9p0">
<button class="TUXButton TUXButton--default TUXButton--medium TUXButton--primary css-z0yv3q-7937d88b--StyledLeftSidePrimaryButtonRedesign eltikj10" aria-disabled="false" type="button" id="header-login-button"><div class="TUXButton-content"><div class="TUXButton-label">Log in</div></div></button>
<img alt="i’m scared" fetchpriority="high" decoding="async" srcset="https://p16-common-s..." src="https://p16-common-s..." imagex-type="react" imagex-version="0.3.10" data-fmp="true" style="position: absolute; ...">
Showing first 5 of 32 audited elements.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination3 elements
Each landmark on a page must have either a unique role or a unique accessible name. Duplicate landmarks confuse screen reader users about which section they're navigating to, making it difficult to efficiently move through the page structure.
Audit Elements
<section aria-label="Notifications alt+T" tabindex="-1" aria-live="polite" aria-relevant="additions text" aria-atomic="false">
<main id="main-content-homepage_hot" class="css-qelder-7937d88b--DivMainContainer er8k1k70">
<aside class="css-1vxkjq6-7937d88b--AsideOneColumnSidebar e1xw80nk0">
Links must have discernible text18 elements
Keyboard users and screen reader users can only interact with links that have accessible names and can receive focus. Without proper names, users don't know where links lead. Without keyboard focus, users who cannot use a mouse cannot activate the links at all.
Audit Elements
<a data-e2e="tiktok-logo" aria-label="Go to TikTok For You feed" class="css-1g8z8e3-7937d88b--StyledLinkLogo e1m2fri00 link-a11y-focus" href="/" style="position: relative;">
<a data-e2e="nav-foryou" tabindex="-1" class="link-a11y-focus" href="/">
<a data-e2e="nav-shop" rel="noopener noreferrer" tabindex="-1" class="link-a11y-focus" href="https://shop.tiktok.com/us" target="_blank">
<a data-e2e="nav-explore" tabindex="-1" class="link-a11y-focus" href="/explore">
<a data-e2e="nav-following" tabindex="-1" class="link-a11y-focus" href="/following">
Showing first 5 of 18 audited elements.
Main landmark should not be contained in another landmark1 element
The main landmark must be at the top level and not nested inside other landmarks. This ensures screen reader users can quickly navigate to the primary content without searching through complex hierarchy, making page navigation simpler and more predictable.
Audit Elements
<main id="main-content-homepage_hot" class="css-qelder-7937d88b--DivMainContainer er8k1k70">
Page must have means to bypass repeated blocks1 element
Keyboard-only users must tab through all navigation and header content before reaching the main content, which can take several minutes and cause physical pain for users with motor limitations. Bypass mechanisms like skip links allow these users to jump directly to main content, saving time and reducing fatigue.
Audit Elements
<html lang="en" data-tux-color-scheme="light" dir="ltr" data-theme="light" data-rh="lang,data-theme">
Required ARIA attributes must be provided22 elements
ARIA widget roles need required attributes to describe their current state. Without these attributes, screen readers cannot communicate essential information like whether a checkbox is checked or a slider's current value, leaving users unable to interact effectively with the widget.
Audit Elements
<div role="separator" class="tux-separator tux-separator-thin--vertical" style="background-color: var(--ui-shape-neutral-3);"></div>
<div role="button" aria-label="Collapse sidebar" tabindex="0" aria-expanded="false" aria-haspopup="dialog" class="css-1fisppo-7937d88b--DivToggleTrigger e1hzmt9p0">
<button class="TUXButton TUXButton--capsule TUXButton--medium TUXButton--secondary css-15kigdg-7937d88b--StyledTUXSearchButton eqhuzff9" aria-disabled="false" type="button" data-e2e="nav-search" aria-label="Search" role="searchbox">
<button class="TUXButton TUXButton--default TUXButton--medium TUXButton--secondary css-1nj9u0d-7937d88b--StyledTUXNavButton eqhuzff0" aria-disabled="false" type="button" aria-label="For You" role="listitem">
<button class="TUXButton TUXButton--default TUXButton--medium TUXButton--secondary css-1t1gyuu-7937d88b--StyledTUXNavButton eqhuzff0" aria-disabled="false" type="button" aria-label="Shop" role="listitem">
Showing first 5 of 22 audited elements.
Scrollable region must have keyboard access1 element
Scrollable regions must contain focusable elements or be focusable themselves to enable keyboard navigation. Without keyboard access, users cannot scroll to view content that extends beyond the visible area, making that content completely inaccessible to keyboard-only users.
Audit Elements
<div id="column-list-container" class="css-acgxju-7937d88b--DivColumnListContainer e3bfsj60">
Users should be able to zoom and scale the text up to 500%1 element
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.
Audit Elements
<meta name="viewport" content="width=device-width, initial-scale=1.0">
Zooming and scaling must not be disabled1 element
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.
Audit Elements
<meta name="viewport" content="width=device-width, initial-scale=1.0">
How does your site stack up against TikTok?
Run the same automated WCAG 2.2 checks we run on the scoreboard.
More in Social Media
