Twitch twitch.tv
Accessibility score
League position
7thof 10
Issues found
6
Audits passed
44
Accessibility score over time
weekly scans · last 6 months- Good · 90+
- Needs improvement · 70–89
- Poor · Below 70
This month's scan
Issues found
Seriousautocomplete attribute must be used correctly1 element
Missing or incorrect autocomplete values make forms inaccessible to screen reader users. Screen readers cannot provide adequate information about form fields without proper autocomplete attributes, preventing users from understanding what information is required and how to complete forms correctly.
Failing Elements
<input id="tw-d21b210c7c104563a..." aria-label="Search Input" aria-haspopup="grid" type="search" class="ScInputBase-sc-vu7u7..." placeholder="Search" autocapitalize="off" autocorrect="off" autocomplete="twitch-nav-search" data-a-target="tw-input" maxlength="65" spellcheck="false" value="">
Fix all of the following:
- the autocomplete attribute is incorrectly formatted
SeriousInteractive controls must not be nested1 element
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
<button data-a-target="user-menu-toggle" data-test-selector="user-menu__toggle" aria-label="User Menu" aria-expanded="false">
Fix any of the following:
- Element has focusable descendants
Serious[role="img"] and [role="image"] elements must have alternative text2 elements
Screen readers cannot convert visual images with role="img" into text without an accessible alternative. All users with visual disabilities, from complete blindness to low vision and color blindness, require text alternatives to access the information that images convey.
Failing Elements
<div role="img" class="Layout-sc-1xcs6mc-0 hype-train-icon hype-train-icon__train hype-train-icon__train--default" style="margin-top: 0.25rem;"></div>
Fix any of the following:
- 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
<div role="img" class="Layout-sc-1xcs6mc-0 hype-train-icon hype-train-icon__train hype-train-icon__train--default" style="margin-top: 0.25rem;"></div>
Fix any of the following:
- 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
SeriousText must remain readable when spacing is increased7 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
<p title="yourragegaming" data-a-target="side-nav-title" class="CoreText-sc-1txzju1-0 cbeJYP InjectLayout-sc-1i43x...">
<p title="Hype Train • Level 8" class="CoreText-sc-1txzju1-0 dStynu">
<p title="Maximilian_DOOD" data-a-target="side-nav-title" class="CoreText-sc-1txzju1-0 cbeJYP InjectLayout-sc-1i43x...">
<p title="Hype Train • Level 1" class="CoreText-sc-1txzju1-0 dStynu">
<p dir="auto" title="Rainbow Six Siege" class="CoreText-sc-1txzju1-0 bAgiYF">
<p aria-label="Show more" class="CoreText-sc-1txzju1-0 fJYwSz">
<p aria-label="Show all" class="CoreText-sc-1txzju1-0 fJYwSz">
ModerateHeading levels should only increase by one1 element
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.
Failing Elements
<h4 dir="auto" title="(DAY 5) BEATING GIOVANNI TODAY... RADICAL RED NUZLOCKE !badge !names !nuzlocke" class="CoreText-sc-1txzju1-0 dEwqHs" style="font-family: var(--font-body);">(DAY 5) BEATING GIOVANNI TODAY... RADICAL RED NUZLOCKE !badge !names !nuzlocke</h4>
Fix any of the following:
- Heading order invalid
ModerateAll page content should be contained by landmarks2 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
<div class="Layout-sc-1xcs6mc-0 hligZH"><img alt="Cookies" class="tw-image" src="https://assets.twitch.tv/assets/cookie_pink-0c7a47e3c9de4083001d.png"></div>
Fix any of the following:
- Some page content is not contained by landmarks
<div class="Layout-sc-1xcs6mc-0 kMJAXn">
Fix any of the following:
- Some page content is not contained by landmarks
Passed audits44 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 class="tw-root--hover js-focus-visible tw-root--theme-light" data-js-focus-visible="" lang="en-US">
<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 class="tw-root--hover js-focus-visible tw-root--theme-light" data-js-focus-visible="" lang="en-US">
<svg> elements with an img or image role must have alternative text5 elements
SVG images need text alternatives so their information can be accessed through any sensory modality - visual, auditory, or tactile. Text alternatives enable screen readers to convert visual information into speech or braille, support future translation into sign language, and ensure content is accessible regardless of a user's sensory abilities.
Audit Elements
<svg width="12" height="12" viewBox="0 0 12 12" role="img"><title>Verified</title><path fill-rule="evenodd" d="M10 2 6 1 2 2 1 6l1 4 4 1 4-1 1-4-1-4ZM5.5 8.5 9 5 7.5 3.5l-2 2-1-1L3 6l2.5 2.5Z" clip-rule="evenodd"></path></svg>
<svg width="12" height="12" viewBox="0 0 12 12" role="img"><title>Verified</title><path fill-rule="evenodd" d="M10 2 6 1 2 2 1 6l1 4 4 1 4-1 1-4-1-4ZM5.5 8.5 9 5 7.5 3.5l-2 2-1-1L3 6l2.5 2.5Z" clip-rule="evenodd"></path></svg>
<svg width="12" height="12" viewBox="0 0 12 12" role="img"><title>Verified</title><path fill-rule="evenodd" d="M10 2 6 1 2 2 1 6l1 4 4 1 4-1 1-4-1-4ZM5.5 8.5 9 5 7.5 3.5l-2 2-1-1L3 6l2.5 2.5Z" clip-rule="evenodd"></path></svg>
<svg width="12" height="12" viewBox="0 0 12 12" role="img"><title>Verified</title><path fill-rule="evenodd" d="M10 2 6 1 2 2 1 6l1 4 4 1 4-1 1-4-1-4ZM5.5 8.5 9 5 7.5 3.5l-2 2-1-1L3 6l2.5 2.5Z" clip-rule="evenodd"></path></svg>
<svg width="12" height="12" viewBox="0 0 12 12" role="img"><title>Verified</title><path fill-rule="evenodd" d="M10 2 6 1 2 2 1 6l1 4 4 1 4-1 1-4-1-4ZM5.5 8.5 9 5 7.5 3.5l-2 2-1-1L3 6l2.5 2.5Z" clip-rule="evenodd"></path></svg>
All page content should be contained by landmarks1288 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
<div id="root" class="root">
<div class="Layout-sc-1xcs6mc-0 ioqHeC">
<div class="Layout-sc-1xcs6mc-0 fkkvRk">
<div class="Layout-sc-1xcs6mc-0 iuktUJ">
<div class="Layout-sc-1xcs6mc-0 kmASAh consent-banner" data-a-target="consent-banner">
Showing first 5 of 1288 audited elements.
Alternative text of images should not be repeated as text36 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="Cookies" class="tw-image" src="https://assets.twitch.tv/assets/cookie_pink-0c7a47e3c9de4083001d.png">
<img class="InjectLayout-sc-1i43xsx-0 ceDQrC tw-image-avatar" src="https://static-cdn.jtvnw.net/jtv_user_pictures/70c63d12-ecae-485c-9bca-3d3f3ad5782a-profile_image-70x70.png" alt="" style="object-fit: cover;">
<img class="InjectLayout-sc-1i43xsx-0 ceDQrC tw-image-avatar" src="https://static-cdn.jtvnw.net/jtv_user_pictures/abbb9153-593b-42c8-b13b-887ca41de9a1-profile_image-70x70.png" alt="" style="object-fit: cover;">
<img class="InjectLayout-sc-1i43xsx-0 ceDQrC tw-image-avatar" src="https://static-cdn.jtvnw.net/jtv_user_pictures/c2aca19b-b318-4398-99a5-fb6a597536fd-profile_image-70x70.png" alt="" style="object-fit: cover;">
<img class="InjectLayout-sc-1i43xsx-0 ceDQrC tw-image-avatar" src="https://static-cdn.jtvnw.net/jtv_user_pictures/bde8aaf5-35d4-4503-9797-842401da900f-profile_image-70x70.png" alt="" style="object-fit: cover;">
Showing first 5 of 36 audited elements.
ARIA attributes must be used as specified for the element's role108 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
<button aria-keyshortcuts="alt+p" title="Menu for skipping to content (Alt+P)" aria-expanded="false" class="ScCoreButton-sc-ocjdkq-0 ftXRRI">
<a data-a-target="home-link" aria-label="Twitch Home" class="ScCoreLink-sc-16kq0mq-0 eUxSUd InjectLayout-sc-1i43xsx-0 fsEGCG tw-link" href="/">
<a aria-label="Browse" class="navigation-link" link="2" data-a-target="browse-link" data-test-selector="top-nav__browse-link" label="Browse" href="/directory">
<button class="ScCoreButton-sc-ocjdkq-0 fUHGSu ScButtonIcon-sc-9yap0r-0 jhFpVx" aria-label="More Options" data-a-target="ellipsis-button">
<div aria-haspopup="grid" class="Layout-sc-1xcs6mc-0 geVlrj">
Showing first 5 of 108 audited elements.
ARIA attributes must conform to valid names108 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
<button aria-keyshortcuts="alt+p" title="Menu for skipping to content (Alt+P)" aria-expanded="false" class="ScCoreButton-sc-ocjdkq-0 ftXRRI">
<a data-a-target="home-link" aria-label="Twitch Home" class="ScCoreLink-sc-16kq0mq-0 eUxSUd InjectLayout-sc-1i43xsx-0 fsEGCG tw-link" href="/">
<a aria-label="Browse" class="navigation-link" link="2" data-a-target="browse-link" data-test-selector="top-nav__browse-link" label="Browse" href="/directory">
<button class="ScCoreButton-sc-ocjdkq-0 fUHGSu ScButtonIcon-sc-9yap0r-0 jhFpVx" aria-label="More Options" data-a-target="ellipsis-button">
<div aria-haspopup="grid" class="Layout-sc-1xcs6mc-0 geVlrj">
Showing first 5 of 108 audited elements.
ARIA attributes must conform to valid values108 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
<button aria-keyshortcuts="alt+p" title="Menu for skipping to content (Alt+P)" aria-expanded="false" class="ScCoreButton-sc-ocjdkq-0 ftXRRI">
<a data-a-target="home-link" aria-label="Twitch Home" class="ScCoreLink-sc-16kq0mq-0 eUxSUd InjectLayout-sc-1i43xsx-0 fsEGCG tw-link" href="/">
<a aria-label="Browse" class="navigation-link" link="2" data-a-target="browse-link" data-test-selector="top-nav__browse-link" label="Browse" href="/directory">
<button class="ScCoreButton-sc-ocjdkq-0 fUHGSu ScButtonIcon-sc-9yap0r-0 jhFpVx" aria-label="More Options" data-a-target="ellipsis-button">
<div aria-haspopup="grid" class="Layout-sc-1xcs6mc-0 geVlrj">
Showing first 5 of 108 audited elements.
ARIA hidden element must not be focusable or contain focusable elements22 elements
Elements with aria-hidden="true" are removed from the accessibility API but remain keyboard-focusable, creating confusion about their visibility state. When users tab to these hidden elements, screen readers stay silent, leaving users unaware of what they've focused on or why nothing is being announced.
Audit Elements
<svg width="24" height="24" viewBox="0 0 24 24" focusable="false" aria-hidden="true" role="presentation"><path d="M10 5a2 2 0 1 1 4 0 2 2 0 0 1-4 0Zm0 7a2 2 0 1 1 4 0 2 2 0 0 1-4 0Zm2 5a2 2 0 1 0 0 4 2 2 0 0 0 0-4Z"></path></svg>
<svg width="24" height="24" viewBox="0 0 24 24" focusable="false" aria-hidden="true" role="presentation">
<svg width="24" height="24" viewBox="0 0 24 24" focusable="false" aria-hidden="true" role="presentation"><path fill-rule="evenodd" d="M16.852 12.68 12 7.828 7.148 12.68 4 10.161V17h16v-6.839l-3.148 2.519ZM22 6v11a2 2 0 0 1-2 2H4a2 2 0 0 1-2-2V6l5 4 5-5 5 5 5-4Z" clip-rule="evenodd"></path></svg>
<svg width="24" height="24" viewBox="0 0 24 24" focusable="false" aria-hidden="true" role="presentation">
<svg width="24" height="24" viewBox="0 0 24 24" focusable="false" aria-hidden="true" role="presentation"><path d="M21.414 5h-2v14h2V5Z"></path><path fill-rule="evenodd" d="M8.707 5.293 2 12l6.707 6.707 1.414-1.414L5.828 13h11.586v-2H5.828l4.293-4.293-1.414-1.414Z" clip-rule="evenodd"></path></svg>
Showing first 5 of 22 audited elements.
ARIA role should be appropriate for the element25 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
<svg width="24" height="24" viewBox="0 0 24 24" focusable="false" aria-hidden="true" role="presentation"><path d="M10 5a2 2 0 1 1 4 0 2 2 0 0 1-4 0Zm0 7a2 2 0 1 1 4 0 2 2 0 0 1-4 0Zm2 5a2 2 0 1 0 0 4 2 2 0 0 0 0-4Z"></path></svg>
<form role="search">
<svg width="24" height="24" viewBox="0 0 24 24" focusable="false" aria-hidden="true" role="presentation">
<svg width="24" height="24" viewBox="0 0 24 24" focusable="false" aria-hidden="true" role="presentation"><path fill-rule="evenodd" d="M16.852 12.68 12 7.828 7.148 12.68 4 10.161V17h16v-6.839l-3.148 2.519ZM22 6v11a2 2 0 0 1-2 2H4a2 2 0 0 1-2-2V6l5 4 5-5 5 5 5-4Z" clip-rule="evenodd"></path></svg>
<svg width="24" height="24" viewBox="0 0 24 24" focusable="false" aria-hidden="true" role="presentation">
Showing first 5 of 25 audited elements.
ARIA roles used must conform to valid values13 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
<form role="search">
<div class="Layout-sc-1xcs6mc-0 jcmJqG side-nav side-nav--expanded" data-test-selector="side-nav" data-a-target="side-nav-bar" role="complementary">
<div aria-label="Live Channels" class="Layout-sc-1xcs6mc-0 dQMmwU side-nav-section" role="group">
<div role="img" class="Layout-sc-1xcs6mc-0 hype-train-icon hype-train-icon__train hype-train-icon__train--default" style="margin-top: 0.25rem;"></div>
<div role="img" class="Layout-sc-1xcs6mc-0 hype-train-icon hype-train-icon__train hype-train-icon__train--default" style="margin-top: 0.25rem;"></div>
Showing first 5 of 13 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>
Buttons must have discernible text25 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 data-a-target="consent-banner-manage-preferences" class="ScCoreButton-sc-ocjdkq-0 ftXRRI">
<button class="ScCoreButton-sc-ocjdkq-0 kBJXYw"><div class="ScCoreButtonLabel-sc-s7h2b7-0 bfhate"><div data-a-target="tw-core-button-label-text" class="Layout-sc-1xcs6mc-0 zdujK"><div class="Layout-sc-1xcs6mc-0 kMJAXn">Proceed</div></div></div></button>
<button aria-keyshortcuts="alt+p" title="Menu for skipping to content (Alt+P)" aria-expanded="false" class="ScCoreButton-sc-ocjdkq-0 ftXRRI">
<button class="ScCoreButton-sc-ocjdkq-0 fUHGSu ScButtonIcon-sc-9yap0r-0 jhFpVx" aria-label="More Options" data-a-target="ellipsis-button">
<button class="ScCoreButton-sc-ocjdkq-0 ifNpey InjectLayout-sc-1i43xsx-0 bRowwC tw-combo-input__button-icon tw-combo-input__button-icon--large" type="secondary" aria-label="Search Button" disabled="">
Showing first 5 of 25 audited elements.
Content must reflow without two-dimensional scrolling6 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.
Audit Elements
<div class="Layout-sc-1xcs6mc-0 jCxYDG">
<div class="featured-content-carousel__item-container featured..." style="position: absolute; top: 0px; inset-inline-start: ...">
<div class="featured-content-carousel__item-container featured..." data-a-target="featured-item-index-0" style="position: absolute; top: 0px; inset-inline-start: ...">
<div class="featured-content-carousel__item-container featured..." style="position: absolute; top: 0px; inset-inline-start: ...">
<div class="featured-content-carousel__item-container featured..." style="position: absolute; top: 0px; inset-inline-start: ...">
Showing first 5 of 6 audited elements.
Contentinfo landmark should not be contained in another landmark1 element
The contentinfo landmark must be at the top level to help screen reader users quickly navigate to footer information. When nested inside another landmark, it becomes harder to find, defeating its purpose of providing quick access to content information.
Audit Elements
<footer id="twilight-sticky-footer-root"></footer>
Deprecated ARIA roles must not be used13 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
<form role="search">
<div class="Layout-sc-1xcs6mc-0 jcmJqG side-nav side-nav--expanded" data-test-selector="side-nav" data-a-target="side-nav-bar" role="complementary">
<div aria-label="Live Channels" class="Layout-sc-1xcs6mc-0 dQMmwU side-nav-section" role="group">
<div role="img" class="Layout-sc-1xcs6mc-0 hype-train-icon hype-train-icon__train hype-train-icon__train--default" style="margin-top: 0.25rem;"></div>
<div role="img" class="Layout-sc-1xcs6mc-0 hype-train-icon hype-train-icon__train hype-train-icon__train--default" style="margin-top: 0.25rem;"></div>
Showing first 5 of 13 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 class="tw-root--hover js-focus-visible tw-root--theme-light" data-js-focus-visible="" lang="en-US">
Document should not have more than one banner landmark1 element
Multiple banner landmarks force screen reader users to sort through duplicate options to find header information. Each page should have only one banner landmark to enable quick, predictable navigation to the header without overwhelming users with unnecessary choices.
Audit Elements
<header id="twilight-sticky-header-root"></header>
Document should not have more than one contentinfo landmark1 element
Multiple contentinfo landmarks force screen reader users to sort through extra options to find footer information. Each page should have only one content info landmark to enable quick, predictable navigation without overwhelming users with duplicate structural markers.
Audit Elements
<footer id="twilight-sticky-footer-root"></footer>
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 class="InjectLayout-sc-1i43xsx-0 dUtJpw twilight-main">
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 class="tw-root--hover js-focus-visible tw-root--theme-light" data-js-focus-visible="" lang="en-US">
Elements marked as presentational should be consistently ignored15 elements
Elements with role="none" or role="presentation" should be removed from the accessibility tree. Adding global ARIA attributes or making these elements focusable prevents their removal, leaving them accessible to screen readers when they should be ignored, creating unexpected and confusing behavior.
Audit Elements
<img class="InjectLayout-sc-1i43xsx-0 ceDQrC tw-image-avatar" src="https://static-cdn.jtvnw.net/jtv_user_pictures/70c63d12-ecae-485c-9bca-3d3f3ad5782a-profile_image-70x70.png" alt="" style="object-fit: cover;">
<img class="InjectLayout-sc-1i43xsx-0 ceDQrC tw-image-avatar" src="https://static-cdn.jtvnw.net/jtv_user_pictures/abbb9153-593b-42c8-b13b-887ca41de9a1-profile_image-70x70.png" alt="" style="object-fit: cover;">
<img class="InjectLayout-sc-1i43xsx-0 ceDQrC tw-image-avatar" src="https://static-cdn.jtvnw.net/jtv_user_pictures/c2aca19b-b318-4398-99a5-fb6a597536fd-profile_image-70x70.png" alt="" style="object-fit: cover;">
<img class="InjectLayout-sc-1i43xsx-0 ceDQrC tw-image-avatar" src="https://static-cdn.jtvnw.net/jtv_user_pictures/bde8aaf5-35d4-4503-9797-842401da900f-profile_image-70x70.png" alt="" style="object-fit: cover;">
<img class="InjectLayout-sc-1i43xsx-0 ceDQrC tw-image-avatar" src="https://static-cdn.jtvnw.net/jtv_user_pictures/99aa4739-21d6-40af-86ae-4b4d3457fce4-profile_image-70x70.png" alt="" style="object-fit: cover;">
Showing first 5 of 15 audited elements.
Elements must meet minimum color contrast ratio thresholds10 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
<p class="CoreText-sc-1txzju1-0 ScTitleText-sc-d9mj2s-0 fPJBrv GsAAv tw-title">Cookies and Advertising Choices<br></p>
<p class="CoreText-sc-1txzju1-0 fJYwSz">
<div class="Layout-sc-1xcs6mc-0 kMJAXn">Cookies & Ads Choices</div>
<div class="Layout-sc-1xcs6mc-0 kMJAXn">Proceed</div>
<p class="CoreText-sc-1txzju1-0 ScTitleText-sc-d9mj2s-0 fPJBrv GsAAv InjectLayout-sc-1i43xsx-0 iDaFMd tw-title">Browse</p>
Showing first 5 of 10 audited elements.
Elements must only use permitted ARIA attributes105 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
<button aria-keyshortcuts="alt+p" title="Menu for skipping to content (Alt+P)" aria-expanded="false" class="ScCoreButton-sc-ocjdkq-0 ftXRRI">
<a data-a-target="home-link" aria-label="Twitch Home" class="ScCoreLink-sc-16kq0mq-0 eUxSUd InjectLayout-sc-1i43xsx-0 fsEGCG tw-link" href="/">
<a aria-label="Browse" class="navigation-link" link="2" data-a-target="browse-link" data-test-selector="top-nav__browse-link" label="Browse" href="/directory">
<button class="ScCoreButton-sc-ocjdkq-0 fUHGSu ScButtonIcon-sc-9yap0r-0 jhFpVx" aria-label="More Options" data-a-target="ellipsis-button">
<div aria-haspopup="grid" class="Layout-sc-1xcs6mc-0 geVlrj">
Showing first 5 of 105 audited elements.
Elements must only use supported ARIA attributes108 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
<button aria-keyshortcuts="alt+p" title="Menu for skipping to content (Alt+P)" aria-expanded="false" class="ScCoreButton-sc-ocjdkq-0 ftXRRI">
<a data-a-target="home-link" aria-label="Twitch Home" class="ScCoreLink-sc-16kq0mq-0 eUxSUd InjectLayout-sc-1i43xsx-0 fsEGCG tw-link" href="/">
<a aria-label="Browse" class="navigation-link" link="2" data-a-target="browse-link" data-test-selector="top-nav__browse-link" label="Browse" href="/directory">
<button class="ScCoreButton-sc-ocjdkq-0 fUHGSu ScButtonIcon-sc-9yap0r-0 jhFpVx" aria-label="More Options" data-a-target="ellipsis-button">
<div aria-haspopup="grid" class="Layout-sc-1xcs6mc-0 geVlrj">
Showing first 5 of 108 audited elements.
Elements should not have tabindex greater than zero24 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
<button data-test-selector="StreamTitle" data-a-target="preview-card-title-link" tabindex="-1" class="ScCoreLink-sc-16kq0mq-0 eCwVpW Layout-sc-1xcs6mc-0 RpXvf ScCoreLink-sc-bhsr9c-0 kgscaa tw-link">
<p data-a-target="preview-card-channel-link" tabindex="-1" class="CoreText-sc-1txzju1-0 bKVzPb">
<a data-test-selector="preview-card-avatar" tabindex="-1" class="ScCoreLink-sc-16kq0mq-0 eUxSUd preview-card-avatar tw-link" href="/yourragegaming">
<a data-a-target="preview-card-image-link" tabindex="-1" class="ScCoreLink-sc-16kq0mq-0 eUxSUd InjectLayout-sc-1i43xsx-0 ensATL preview-card-image-link tw-link" href="/yourragegaming">
<button data-test-selector="StreamTitle" data-a-target="preview-card-title-link" tabindex="-1" class="ScCoreLink-sc-16kq0mq-0 eCwVpW Layout-sc-1xcs6mc-0 RpXvf ScCoreLink-sc-bhsr9c-0 kgscaa tw-link">
Showing first 5 of 24 audited elements.
Focused elements must not be entirely hidden by author-created content50 elements
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.
Audit Elements
<button data-a-target="consent-banner-manage-preferences" class="ScCoreButton-sc-ocjdkq-0 ftXRRI focus-visible" data-focus-visible-added="">
<button class="ScCoreButton-sc-ocjdkq-0 kBJXYw focus-visible" data-focus-visible-added="">
<button aria-keyshortcuts="alt+p" title="Menu for skipping to content (Alt+P)" aria-expanded="false" class="ScCoreButton-sc-ocjdkq-0 ftXRRI focus-visible" data-focus-visible-added="">
<a data-a-target="home-link" aria-label="Twitch Home" class="ScCoreLink-sc-16kq0mq-0 eUxSUd InjectLayout-sc-1i4..." href="/" data-focus-visible-added="">
<a aria-label="Browse" class="navigation-link focus-visible" link="2" data-a-target="browse-link" data-test-selector="top-nav__browse-link" label="Browse" href="/directory" data-focus-visible-added="">
Showing first 5 of 50 audited elements.
Form elements must have labels1 element
Form labels are essential for screen reader users to understand what information each field requires. Without proper labels, screen readers cannot identify input expectations, fields don't receive focus when announced, and users with motor impairments lose the benefit of larger clickable areas that labels provide.
Audit Elements
<input id="tw-d21b210c7c104563a..." aria-label="Search Input" aria-haspopup="grid" type="search" class="ScInputBase-sc-vu7u7..." placeholder="Search" autocapitalize="off" autocorrect="off" autocomplete="twitch-nav-search" data-a-target="tw-input" maxlength="65" spellcheck="false" value="">
Form elements should have a visible label1 element
The title and aria-describedby attributes provide supplementary hints, not labels. Screen readers treat these as advisory information rather than true labels, which prevents them from properly conveying the form element's purpose. Form fields need proper labels that can be programmatically determined.
Audit Elements
<input id="tw-d21b210c7c104563a..." aria-label="Search Input" aria-haspopup="grid" type="search" class="ScInputBase-sc-vu7u7..." placeholder="Search" autocapitalize="off" autocorrect="off" autocomplete="twitch-nav-search" data-a-target="tw-input" maxlength="65" spellcheck="false" value="">
Form field must not have multiple label elements1 element
Multiple labels on the same form field cause inconsistent behavior across screen reader and browser combinations. Some will read the first label, others the last, and some will read both, creating confusion about what information the field requires.
Audit Elements
<input id="tw-d21b210c7c104563a..." aria-label="Search Input" aria-haspopup="grid" type="search" class="ScInputBase-sc-vu7u7..." placeholder="Search" autocapitalize="off" autocorrect="off" autocomplete="twitch-nav-search" data-a-target="tw-input" maxlength="65" spellcheck="false" value="">
Heading levels should only increase by one14 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
<h3 class="CoreText-sc-1txzju1-0 dvalrg">Live Channels</h3>
<h2 id="e073c442722643ff" class="CoreText-sc-1txzju1-0 ScTitleText-sc-d9mj2s-0 fPJBrv GsAAv tw-title"><a class="ScCoreLink-sc-16kq0mq-0 eUxSUd tw-link" href="/directory/all">Live on Twitch</a></h2>
<h4 dir="auto" title="!MOUSEATHON DAY 6 AHHHH 50% TO IMMUNE DEF | !9th | !apari | !omocat | !fox | !cheeky | !ht | !starforge | !tts | !merch | !razer" class="CoreText-sc-1txzju1-0 dEwqHs" style="font-family: var(--font-body);">
<h4 dir="auto" title="Radio Surprise The LIVE DJ Radio • 24/7 EDM • LIVE DJ Shows • Techhouse • Trance • Techno • Made in Austria • www.calltv4u.com" class="CoreText-sc-1txzju1-0 dEwqHs" style="font-family: var(--font-body);">
<h2 id="40b5cd2dbef24a86" class="CoreText-sc-1txzju1-0 ScTitleText-sc-d9mj2s-0 fPJBrv GsAAv tw-title"><a class="ScCoreLink-sc-16kq0mq-0 eUxSUd tw-link" href="/directory">Categories</a><span class="CoreText-sc-1txzju1-0 ScTitleText-sc-d9mj2s-0 fPJBrv GsAAv tw-title"> we think you’ll like</span></h2>
Showing first 5 of 14 audited elements.
Headings should not be empty16 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
<h3 class="CoreText-sc-1txzju1-0 dvalrg">Live Channels</h3>
<h2 id="e073c442722643ff" class="CoreText-sc-1txzju1-0 ScTitleText-sc-d9mj2s-0 fPJBrv GsAAv tw-title"><a class="ScCoreLink-sc-16kq0mq-0 eUxSUd tw-link" href="/directory/all">Live on Twitch</a></h2>
<h4 dir="auto" title="(DAY 5) BEATING GIOVANNI TODAY... RADICAL RED NUZLOCKE !badge !names !nuzlocke" class="CoreText-sc-1txzju1-0 dEwqHs" style="font-family: var(--font-body);">(DAY 5) BEATING GIOVANNI TODAY... RADICAL RED NUZLOCKE !badge !names !nuzlocke</h4>
<h4 dir="auto" title="!MOUSEATHON DAY 6 AHHHH 50% TO IMMUNE DEF | !9th | !apari | !omocat | !fox | !cheeky | !ht | !starforge | !tts | !merch | !razer" class="CoreText-sc-1txzju1-0 dEwqHs" style="font-family: var(--font-body);">
<h4 dir="auto" title="Radio Surprise The LIVE DJ Radio • 24/7 EDM • LIVE DJ Shows • Techhouse • Trance • Techno • Made in Austria • www.calltv4u.com" class="CoreText-sc-1txzju1-0 dEwqHs" style="font-family: var(--font-body);">
Showing first 5 of 16 audited elements.
IDs used in ARIA and labels must be unique4 elements
Duplicate IDs break the accessibility of ARIA elements, form labels, and table headers. When IDs are duplicated, assistive technologies and scripts only reference the first instance, causing subsequent elements with the same ID to be ignored or incorrectly associated.
Audit Elements
<input id="player-volume-slider..." aria-valuemin="0" aria-valuemax="100" aria-valuenow="100" aria-valuetext="100%" class="ScRangeInput-sc-q01w..." type="range" min="0" max="1" step="0.01" data-a-target="player-volume-slider" data-a-visible="false" value="1">
<h2 id="e073c442722643ff" class="CoreText-sc-1txzju1-0 ScTitleText-sc-d9mj2s-0 fPJBrv GsAAv tw-title"><a class="ScCoreLink-sc-16kq0mq-0 eUxSUd tw-link" href="/directory/all">Live on Twitch</a></h2>
<h2 id="40b5cd2dbef24a86" class="CoreText-sc-1txzju1-0 ScTitleText-sc-d9mj2s-0 fPJBrv GsAAv tw-title"><a class="ScCoreLink-sc-16kq0mq-0 eUxSUd tw-link" href="/directory">Categories</a><span class="CoreText-sc-1txzju1-0 ScTitleText-sc-d9mj2s-0 fPJBrv GsAAv tw-title"> we think you’ll like</span></h2>
<h2 id="17b4a88cacdf45c7" class="CoreText-sc-1txzju1-0 ScTitleText-sc-d9mj2s-0 fPJBrv GsAAv tw-title"><a class="ScCoreLink-sc-16kq0mq-0 eUxSUd tw-link" href="/directory/collection/just-chatting-irl-streams">Just Chatting & IRL</a></h2>
Images must have alternative text36 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="Cookies" class="tw-image" src="https://assets.twitch.tv/assets/cookie_pink-0c7a47e3c9de4083001d.png">
<img class="InjectLayout-sc-1i43xsx-0 ceDQrC tw-image-avatar" src="https://static-cdn.jtvnw.net/jtv_user_pictures/70c63d12-ecae-485c-9bca-3d3f3ad5782a-profile_image-70x70.png" alt="" style="object-fit: cover;">
<img class="InjectLayout-sc-1i43xsx-0 ceDQrC tw-image-avatar" src="https://static-cdn.jtvnw.net/jtv_user_pictures/abbb9153-593b-42c8-b13b-887ca41de9a1-profile_image-70x70.png" alt="" style="object-fit: cover;">
<img class="InjectLayout-sc-1i43xsx-0 ceDQrC tw-image-avatar" src="https://static-cdn.jtvnw.net/jtv_user_pictures/c2aca19b-b318-4398-99a5-fb6a597536fd-profile_image-70x70.png" alt="" style="object-fit: cover;">
<img class="InjectLayout-sc-1i43xsx-0 ceDQrC tw-image-avatar" src="https://static-cdn.jtvnw.net/jtv_user_pictures/bde8aaf5-35d4-4503-9797-842401da900f-profile_image-70x70.png" alt="" style="object-fit: cover;">
Showing first 5 of 36 audited elements.
Inline text spacing must be adjustable with custom stylesheets43 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
<div class="Layout-sc-1xcs6mc-0 ioVgJA" style="overflow: auto;">
<nav class="InjectLayout-sc-1i43xsx-0 UAQUH top-nav" data-a-target="top-nav-container" style="height: 5rem;">
<div data-test-selector="toggle-balloon-wrapper__mouse-enter-detector" style="display: inherit;">
<div data-test-selector="toggle-balloon-wrapper__mouse-enter-detector" style="display: inherit;">
<div data-test-selector="toggle-balloon-wrapper__mouse-enter-detector" style="display: inherit;">
Showing first 5 of 43 audited elements.
Interactive controls must not be nested52 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
<img alt="Cookies" class="tw-image" src="https://assets.twitch.tv/assets/cookie_pink-0c7a47e3c9de4083001d.png">
<button data-a-target="consent-banner-manage-preferences" class="ScCoreButton-sc-ocjdkq-0 ftXRRI">
<button class="ScCoreButton-sc-ocjdkq-0 kBJXYw"><div class="ScCoreButtonLabel-sc-s7h2b7-0 bfhate"><div data-a-target="tw-core-button-label-text" class="Layout-sc-1xcs6mc-0 zdujK"><div class="Layout-sc-1xcs6mc-0 kMJAXn">Proceed</div></div></div></button>
<button aria-keyshortcuts="alt+p" title="Menu for skipping to content (Alt+P)" aria-expanded="false" class="ScCoreButton-sc-ocjdkq-0 ftXRRI">
<button class="ScCoreButton-sc-ocjdkq-0 fUHGSu ScButtonIcon-sc-9yap0r-0 jhFpVx" aria-label="More Options" data-a-target="ellipsis-button">
Showing first 5 of 52 audited elements.
Interactive elements must have a visible focus indicator50 elements
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.
Audit Elements
<button data-a-target="consent-banner-manage-preferences" class="ScCoreButton-sc-ocjdkq-0 ftXRRI focus-visible" data-focus-visible-added="">
<button class="ScCoreButton-sc-ocjdkq-0 kBJXYw focus-visible" data-focus-visible-added="">
<button aria-keyshortcuts="alt+p" title="Menu for skipping to content (Alt+P)" aria-expanded="false" class="ScCoreButton-sc-ocjdkq-0 ftXRRI focus-visible" data-focus-visible-added="">
<a data-a-target="home-link" aria-label="Twitch Home" class="ScCoreLink-sc-16kq0mq-0 eUxSUd InjectLayout-sc-1i4..." href="/" data-focus-visible-added="">
<a aria-label="Browse" class="navigation-link focus-visible" link="2" data-a-target="browse-link" data-test-selector="top-nav__browse-link" label="Browse" href="/directory" data-focus-visible-added="">
Showing first 5 of 50 audited elements.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination8 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
<nav class="InjectLayout-sc-1i43xsx-0 UAQUH top-nav" data-a-target="top-nav-container" style="height: 5rem;">
<form role="search">
<div class="Layout-sc-1xcs6mc-0 jcmJqG side-nav side-nav--expanded" data-test-selector="side-nav" data-a-target="side-nav-bar" role="complementary">
<nav class="Layout-sc-1xcs6mc-0 skip-to-target" id="side-nav" aria-label="Left Navigation" aria-hidden="false">
<main class="InjectLayout-sc-1i43xsx-0 dUtJpw twilight-main">
Showing first 5 of 8 audited elements.
Links must have discernible text89 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-a-target="home-link" aria-label="Twitch Home" class="ScCoreLink-sc-16kq0mq-0 eUxSUd InjectLayout-sc-1i43xsx-0 fsEGCG tw-link" href="/">
<a aria-label="Browse" class="navigation-link" link="2" data-a-target="browse-link" data-test-selector="top-nav__browse-link" label="Browse" href="/directory">
<a data-a-id="recommended-channel-0" data-test-selector="recommended-channel" aria-haspopup="dialog" class="ScCoreLink-sc-16kq0mq-0 eUxSUd InjectLayout-sc-1i43xsx-0 ernidy side-nav-card__link tw-link" href="/yourragegaming">
<a data-a-id="recommended-channel-1" data-test-selector="recommended-channel" aria-haspopup="dialog" class="ScCoreLink-sc-16kq0mq-0 eUxSUd InjectLayout-sc-1i43xsx-0 ernidy side-nav-card__link tw-link" href="/radiosurprise">
<a data-a-id="recommended-channel-2" data-test-selector="recommended-channel" aria-haspopup="dialog" class="ScCoreLink-sc-16kq0mq-0 eUxSUd InjectLayout-sc-1i43xsx-0 ernidy side-nav-card__link tw-link" href="/ironmouse">
Showing first 5 of 89 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 class="InjectLayout-sc-1i43xsx-0 dUtJpw twilight-main">
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 class="tw-root--hover js-focus-visible tw-root--theme-light" data-js-focus-visible="" lang="en-US">
Page 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.
Audit Elements
<html class="tw-root--hover js-focus-visible tw-root--theme-light" data-js-focus-visible="" lang="en-US">
Required ARIA attributes must be provided13 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
<form role="search">
<div class="Layout-sc-1xcs6mc-0 jcmJqG side-nav side-nav--expanded" data-test-selector="side-nav" data-a-target="side-nav-bar" role="complementary">
<div aria-label="Live Channels" class="Layout-sc-1xcs6mc-0 dQMmwU side-nav-section" role="group">
<div role="img" class="Layout-sc-1xcs6mc-0 hype-train-icon hype-train-icon__train hype-train-icon__train--default" style="margin-top: 0.25rem;"></div>
<div role="img" class="Layout-sc-1xcs6mc-0 hype-train-icon hype-train-icon__train hype-train-icon__train--default" style="margin-top: 0.25rem;"></div>
Showing first 5 of 13 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 class="scrollable-area root-scrollable root-scrollable__content" data-a-target="root-scroller" style="overflow-x: hidden;">
How does your site stack up against Twitch?
Run the same automated WCAG 2.2 checks we run on the scoreboard.
More in Streaming & Entertainment