YouTubeyoutube.com
Accessibility Score
Issues Found
Issues Found
CriticalElements must only use supported ARIA attributes4 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
<a id="endpoint" class="yt-simple-endpoint style-scope ytd-mini-guide-entry-renderer" aria-selected="true" aria-label="Home" title="Home" href="/">
Fix all of the following:
- ARIA attribute is not allowed: aria-selected="true"
<a id="endpoint" class="yt-simple-endpoint style-scope ytd-mini-guide-entry-renderer" aria-selected="false" aria-label="Shorts" title="Shorts" href="/shorts/">
Fix all of the following:
- ARIA attribute is not allowed: aria-selected="false"
<a id="endpoint" class="yt-simple-endpoint style-scope ytd-mini-guide-entry-renderer" aria-selected="false" aria-label="Subscriptions" title="Subscriptions" href="/feed/subscriptions">
Fix all of the following:
- ARIA attribute is not allowed: aria-selected="false"
<a id="endpoint" class="yt-simple-endpoint style-scope ytd-mini-guide-entry-renderer" aria-selected="false" aria-label="You" title="You" href="/feed/you">
Fix all of the following:
- ARIA attribute is not allowed: aria-selected="false"
Passed Audits
"role=text" should have no focusable descendants2 elements
Using role="text" prevents VoiceOver from splitting text into multiple phrases, but it also overrides all descendant element roles. If a focusable element exists within role="text", users can tab to it but won't hear its name, role, or value, creating an empty and confusing tab stop.
Audit Elements
<span class="ytAttributedStringHost ytAttributedStringWhiteSpaceNoWrap" role="text" style="">Skip navigation</span>
<span class="ytAttributedStringHost ytAttributedStringWhiteSpaceNoWrap" role="text" style="">Sign in</span>
<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 style="font-size: 10px;font-family: Roboto, Arial, sans-serif;" lang="en" darker-dark-theme="" darker-dark-theme-deprecate="" system-icons="" color-version="v2_0" typography="" typography-spacing="">
<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 style="font-size: 10px;font-family: Roboto, Arial, sans-serif;" lang="en" darker-dark-theme="" darker-dark-theme-deprecate="" system-icons="" color-version="v2_0" typography="" typography-spacing="">
All page content should be contained by landmarks135 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
<ytd-app fix-ambient-cutoff="" mini-guide-visible="">
<yt-guide-manager id="guide-service" class="style-scope ytd-app"> </yt-guide-manager>
<yt-mdx-manager class="style-scope ytd-app"></yt-mdx-manager>
<yt-playlist-manager class="style-scope ytd-app"></yt-playlist-manager>
<yt-hotkey-manager class="style-scope ytd-app"></yt-hotkey-manager>
<div id="content" class="style-scope ytd-app">
<div id="masthead-container" class="style-scope ytd-app">
<ytd-masthead id="masthead" logo-type="YOUTUBE_LOGO" slot="masthead" class="masthead-finish" frosted-glass-mode="loading-without-chipbar" role="banner" mini-guide-visible="">
<div id="ticker" class="style-scope ytd-masthead"></div>
<div id="interstitial" class="style-scope ytd-masthead"></div>
Showing first 10 of 135 audited elements.
ARIA attributes must be used as specified for the element's role17 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 id="button" class="style-scope yt-icon-button" aria-label="Guide">
<a class="yt-simple-endpoint style-scope ytd-topbar-logo-renderer" id="logo" aria-label="" href="/" title="YouTube Home">
<button class="ytSpecButtonShapeNextHost ytSpecButtonShapeNextTonal ytSpecButtonShapeNextMono ytSpecButtonShapeNextSizeM ytSpecButtonShapeNextEnableBackdropFilterExperiment" title="" aria-label="Skip navigation" aria-disabled="false">
<input class="ytSearchboxComponentInput yt-searchbox-input title" name="search_query" aria-controls="i0" aria-expanded="true" type="text" autocomplete="off" autocorrect="off" spellcheck="false" aria-autocomplete="list" role="combobox" placeholder="Search">
<button aria-label="Search" class="ytSearchboxComponentSearchButton" title="Search"><span class="ytIconWrapperHost"><span class="yt-icon-shape"></span></span></button>
<button class="ytSpecButtonShapeNextHost ytSpecButtonShapeNextText ytSpecButtonShapeNextMono ytSpecButtonShapeNextSizeM ytSpecButtonShapeNextIconOnlyDefault ytSpecButtonShapeNextEnableBackdropFilterExperiment" title="" aria-label="Search with your voice" aria-disabled="false">
<tp-yt-paper-tooltip offset="8" role="tooltip" tabindex="-1" aria-label="tooltip">
<button id="button" class="style-scope yt-icon-button" aria-label="Settings">
<a href="https://accounts.goo..." rel="nofollow" class="ytSpecButtonShapeNex..." aria-haspopup="false" force-new-state="true" aria-label="Sign in" aria-current="false" style="">
<a id="endpoint" class="yt-simple-endpoint style-scope ytd-mini-guide-entry-renderer" aria-selected="true" aria-label="Home" title="Home" href="/">
Showing first 10 of 17 audited elements.
ARIA attributes must conform to valid names17 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 id="button" class="style-scope yt-icon-button" aria-label="Guide">
<a class="yt-simple-endpoint style-scope ytd-topbar-logo-renderer" id="logo" aria-label="" href="/" title="YouTube Home">
<button class="ytSpecButtonShapeNextHost ytSpecButtonShapeNextTonal ytSpecButtonShapeNextMono ytSpecButtonShapeNextSizeM ytSpecButtonShapeNextEnableBackdropFilterExperiment" title="" aria-label="Skip navigation" aria-disabled="false">
<input class="ytSearchboxComponentInput yt-searchbox-input title" name="search_query" aria-controls="i0" aria-expanded="true" type="text" autocomplete="off" autocorrect="off" spellcheck="false" aria-autocomplete="list" role="combobox" placeholder="Search">
<button aria-label="Search" class="ytSearchboxComponentSearchButton" title="Search"><span class="ytIconWrapperHost"><span class="yt-icon-shape"></span></span></button>
<button class="ytSpecButtonShapeNextHost ytSpecButtonShapeNextText ytSpecButtonShapeNextMono ytSpecButtonShapeNextSizeM ytSpecButtonShapeNextIconOnlyDefault ytSpecButtonShapeNextEnableBackdropFilterExperiment" title="" aria-label="Search with your voice" aria-disabled="false">
<tp-yt-paper-tooltip offset="8" role="tooltip" tabindex="-1" aria-label="tooltip">
<button id="button" class="style-scope yt-icon-button" aria-label="Settings">
<a href="https://accounts.goo..." rel="nofollow" class="ytSpecButtonShapeNex..." aria-haspopup="false" force-new-state="true" aria-label="Sign in" aria-current="false" style="">
<a id="endpoint" class="yt-simple-endpoint style-scope ytd-mini-guide-entry-renderer" aria-selected="true" aria-label="Home" title="Home" href="/">
Showing first 10 of 17 audited elements.
ARIA attributes must conform to valid values17 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 id="button" class="style-scope yt-icon-button" aria-label="Guide">
<a class="yt-simple-endpoint style-scope ytd-topbar-logo-renderer" id="logo" aria-label="" href="/" title="YouTube Home">
<button class="ytSpecButtonShapeNextHost ytSpecButtonShapeNextTonal ytSpecButtonShapeNextMono ytSpecButtonShapeNextSizeM ytSpecButtonShapeNextEnableBackdropFilterExperiment" title="" aria-label="Skip navigation" aria-disabled="false">
<input class="ytSearchboxComponentInput yt-searchbox-input title" name="search_query" aria-controls="i0" aria-expanded="true" type="text" autocomplete="off" autocorrect="off" spellcheck="false" aria-autocomplete="list" role="combobox" placeholder="Search">
<button aria-label="Search" class="ytSearchboxComponentSearchButton" title="Search"><span class="ytIconWrapperHost"><span class="yt-icon-shape"></span></span></button>
<button class="ytSpecButtonShapeNextHost ytSpecButtonShapeNextText ytSpecButtonShapeNextMono ytSpecButtonShapeNextSizeM ytSpecButtonShapeNextIconOnlyDefault ytSpecButtonShapeNextEnableBackdropFilterExperiment" title="" aria-label="Search with your voice" aria-disabled="false">
<tp-yt-paper-tooltip offset="8" role="tooltip" tabindex="-1" aria-label="tooltip">
<button id="button" class="style-scope yt-icon-button" aria-label="Settings">
<a href="https://accounts.goo..." rel="nofollow" class="ytSpecButtonShapeNex..." aria-haspopup="false" force-new-state="true" aria-label="Sign in" aria-current="false" style="">
<a id="endpoint" class="yt-simple-endpoint style-scope ytd-mini-guide-entry-renderer" aria-selected="true" aria-label="Home" title="Home" href="/">
Showing first 10 of 17 audited elements.
ARIA hidden element must not be focusable or contain focusable elements12 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 style="position: absolute; height: 0; width: 0;" aria-hidden="true"><defs><clipPath id="android_messenger__a"><path fill="#fff" d="M0 0h60v60H0z"></path></clipPath></defs></svg>
<yt-touch-feedback-shape aria-hidden="true" class="ytSpecTouchFeedbackShapeHost ytSpecTouchFeedbackShapeTouchResponse"><div class="ytSpecTouchFeedbackShapeStroke"></div><div class="ytSpecTouchFeedbackShapeFill"></div></yt-touch-feedback-shape>
<div aria-hidden="true" class="ytSpecButtonShapeNextIcon"><span class="ytIconWrapperHost" style="width: 24px; height: 24px;"><span class="yt-icon-shape"></span></span></div>
<yt-touch-feedback-shape aria-hidden="true" class="ytSpecTouchFeedbackShapeHost ytSpecTouchFeedbackShapeTouchResponse"><div class="ytSpecTouchFeedbackShapeStroke"></div><div class="ytSpecTouchFeedbackShapeFill"></div></yt-touch-feedback-shape>
<div aria-hidden="true" class="ytSpecButtonShapeNextIcon"><span class="ytIconWrapperHost" style="width: 24px; height: 24px;"><span class="yt-icon-shape"></span></span></div>
<yt-touch-feedback-shape aria-hidden="true" class="ytSpecTouchFeedbackShapeHost ytSpecTouchFeedbackShapeTouchResponse"><div class="ytSpecTouchFeedbackShapeStroke"></div><div class="ytSpecTouchFeedbackShapeFill"></div></yt-touch-feedback-shape>
<tp-yt-paper-spinner-lite class="style-scope ytd-refresh" hidden="" aria-hidden="true" aria-label="loading">
<a id="thumbnail" class="yt-simple-endpoint inline-block style-scope ytd-thumbnail" aria-hidden="true" tabindex="-1">
<a id="thumbnail" class="yt-simple-endpoint inline-block style-scope ytd-thumbnail" aria-hidden="true" tabindex="-1">
<tp-yt-paper-tooltip aria-hidden="true" fit-to-visible-bounds="" class="style-scope ytd-channel-name" role="tooltip" tabindex="-1" aria-label="tooltip">
Showing first 10 of 12 audited elements.
ARIA role should be appropriate for the element17 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
<ytd-masthead id="masthead" logo-type="YOUTUBE_LOGO" slot="masthead" class="masthead-finish" frosted-glass-mode="loading-without-chipbar" role="banner" mini-guide-visible="">
<span class="ytAttributedStringHost ytAttributedStringWhiteSpaceNoWrap" role="text" style="">Skip navigation</span>
<yt-searchbox role="search" client-ve-type="10349" class="ytSearchboxComponentHost ytSearchboxComponentDesktop ytd-masthead">
<input class="ytSearchboxComponentInput yt-searchbox-input title" name="search_query" aria-controls="i0" aria-expanded="true" type="text" autocomplete="off" autocorrect="off" spellcheck="false" aria-autocomplete="list" role="combobox" placeholder="Search">
<div id="i0" role="listbox" hidden="true" class="ytSearchboxComponentSuggestionsContainer ytSearchboxComponentSuggestionsContainerScrollable" style="min-width: 536px;"></div>
<tp-yt-paper-tooltip offset="8" role="tooltip" tabindex="-1" aria-label="tooltip">
<span class="ytAttributedStringHost ytAttributedStringWhiteSpaceNoWrap" role="text" style="">Sign in</span>
<tp-yt-app-drawer id="guide" align="start" role="navigation" class="style-scope ytd-app" style="transition-duration: 200ms; touch-action: pan-y;" position="left" swipe-open="">
<ytd-mini-guide-renderer class="style-scope ytd-app" role="navigation" mini-guide-visible="">
<tp-yt-paper-tooltip animation-delay="0" offset="0" position="right" class="style-scope ytd-mini-guide-entry-renderer" role="tooltip" tabindex="-1" aria-label="tooltip" hidden="" style="--paper-tooltip-delay-in: 0ms;">
Showing first 10 of 17 audited elements.
ARIA roles used must conform to valid values8 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
<ytd-masthead id="masthead" logo-type="YOUTUBE_LOGO" slot="masthead" class="masthead-finish" frosted-glass-mode="loading-without-chipbar" role="banner" mini-guide-visible="">
<span class="ytAttributedStringHost ytAttributedStringWhiteSpaceNoWrap" role="text" style="">Skip navigation</span>
<yt-searchbox role="search" client-ve-type="10349" class="ytSearchboxComponentHost ytSearchboxComponentDesktop ytd-masthead">
<input class="ytSearchboxComponentInput yt-searchbox-input title" name="search_query" aria-controls="i0" aria-expanded="true" type="text" autocomplete="off" autocorrect="off" spellcheck="false" aria-autocomplete="list" role="combobox" placeholder="Search">
<tp-yt-paper-tooltip offset="8" role="tooltip" tabindex="-1" aria-label="tooltip">
<span class="ytAttributedStringHost ytAttributedStringWhiteSpaceNoWrap" role="text" style="">Sign in</span>
<ytd-mini-guide-renderer class="style-scope ytd-app" role="navigation" mini-guide-visible="">
<ytd-browse class="style-scope ytd-page-manager" rounded-container="" page-subtype="home" responsive-sizing="COMPACT" role="main" mini-guide-visible="">
ARIA tooltip nodes must have an accessible name1 element
Screen reader users cannot understand the purpose of role="tooltip" elements without an accessible name. The name provides the essential context or help text that the tooltip is meant to convey.
Audit Elements
<tp-yt-paper-tooltip offset="8" role="tooltip" tabindex="-1" aria-label="tooltip">
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 dir="ltr" rounded-container="">
autocomplete 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.
Audit Elements
<input class="ytSearchboxComponentInput yt-searchbox-input title" name="search_query" aria-controls="i0" aria-expanded="true" type="text" autocomplete="off" autocorrect="off" spellcheck="false" aria-autocomplete="list" role="combobox" placeholder="Search">
Banner landmark should not be contained in another landmark1 element
Banner landmarks must be top-level to effectively designate the header portion of the page. Nested banner landmarks fail to provide the structural information screen reader users need to navigate efficiently through the page layout.
Audit Elements
<ytd-masthead id="masthead" logo-type="YOUTUBE_LOGO" slot="masthead" class="masthead-finish" frosted-glass-mode="loading-without-chipbar" role="banner" mini-guide-visible="">
Buttons must have discernible text5 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 id="button" class="style-scope yt-icon-button" aria-label="Guide">
<button class="ytSpecButtonShapeNextHost ytSpecButtonShapeNextTonal ytSpecButtonShapeNextMono ytSpecButtonShapeNextSizeM ytSpecButtonShapeNextEnableBackdropFilterExperiment" title="" aria-label="Skip navigation" aria-disabled="false">
<button aria-label="Search" class="ytSearchboxComponentSearchButton" title="Search"><span class="ytIconWrapperHost"><span class="yt-icon-shape"></span></span></button>
<button class="ytSpecButtonShapeNextHost ytSpecButtonShapeNextText ytSpecButtonShapeNextMono ytSpecButtonShapeNextSizeM ytSpecButtonShapeNextIconOnlyDefault ytSpecButtonShapeNextEnableBackdropFilterExperiment" title="" aria-label="Search with your voice" aria-disabled="false">
<button id="button" class="style-scope yt-icon-button" aria-label="Settings">
Deprecated ARIA roles must not be used8 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
<ytd-masthead id="masthead" logo-type="YOUTUBE_LOGO" slot="masthead" class="masthead-finish" frosted-glass-mode="loading-without-chipbar" role="banner" mini-guide-visible="">
<span class="ytAttributedStringHost ytAttributedStringWhiteSpaceNoWrap" role="text" style="">Skip navigation</span>
<yt-searchbox role="search" client-ve-type="10349" class="ytSearchboxComponentHost ytSearchboxComponentDesktop ytd-masthead">
<input class="ytSearchboxComponentInput yt-searchbox-input title" name="search_query" aria-controls="i0" aria-expanded="true" type="text" autocomplete="off" autocorrect="off" spellcheck="false" aria-autocomplete="list" role="combobox" placeholder="Search">
<tp-yt-paper-tooltip offset="8" role="tooltip" tabindex="-1" aria-label="tooltip">
<span class="ytAttributedStringHost ytAttributedStringWhiteSpaceNoWrap" role="text" style="">Sign in</span>
<ytd-mini-guide-renderer class="style-scope ytd-app" role="navigation" mini-guide-visible="">
<ytd-browse class="style-scope ytd-page-manager" rounded-container="" page-subtype="home" responsive-sizing="COMPACT" role="main" mini-guide-visible="">
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 style="font-size: 10px;font-family: Roboto, Arial, sans-serif;" lang="en" darker-dark-theme="" darker-dark-theme-deprecate="" system-icons="" color-version="v2_0" typography="" typography-spacing="">
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
<ytd-masthead id="masthead" logo-type="YOUTUBE_LOGO" slot="masthead" class="masthead-finish" frosted-glass-mode="loading-without-chipbar" role="banner" mini-guide-visible="">
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
<ytd-browse class="style-scope ytd-page-manager" rounded-container="" page-subtype="home" responsive-sizing="COMPACT" role="main" mini-guide-visible="">
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 style="font-size: 10px;font-family: Roboto, Arial, sans-serif;" lang="en" darker-dark-theme="" darker-dark-theme-deprecate="" system-icons="" color-version="v2_0" typography="" typography-spacing="">
Elements must meet minimum color contrast ratio thresholds3 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
<input class="ytSearchboxComponentInput yt-searchbox-input title" name="search_query" aria-controls="i0" aria-expanded="true" type="text" autocomplete="off" autocorrect="off" spellcheck="false" aria-autocomplete="list" role="combobox" placeholder="Search">
<yt-formatted-string id="title" class="style-scope ytd-feed-nudge-renderer" aria-label="Try searching to get started">Try searching to get started</yt-formatted-string>
<yt-formatted-string id="subtitle" split-lines="" class="style-scope ytd-feed-nudge-renderer" aria-label="Start watching videos to help us build a feed of videos you'll love.">Start watching videos to help us build a feed of videos you'll love.</yt-formatted-string>
Elements must only use permitted ARIA attributes15 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 id="button" class="style-scope yt-icon-button" aria-label="Guide">
<a class="yt-simple-endpoint style-scope ytd-topbar-logo-renderer" id="logo" aria-label="" href="/" title="YouTube Home">
<button class="ytSpecButtonShapeNextHost ytSpecButtonShapeNextTonal ytSpecButtonShapeNextMono ytSpecButtonShapeNextSizeM ytSpecButtonShapeNextEnableBackdropFilterExperiment" title="" aria-label="Skip navigation" aria-disabled="false">
<input class="ytSearchboxComponentInput yt-searchbox-input title" name="search_query" aria-controls="i0" aria-expanded="true" type="text" autocomplete="off" autocorrect="off" spellcheck="false" aria-autocomplete="list" role="combobox" placeholder="Search">
<button aria-label="Search" class="ytSearchboxComponentSearchButton" title="Search"><span class="ytIconWrapperHost"><span class="yt-icon-shape"></span></span></button>
<button class="ytSpecButtonShapeNextHost ytSpecButtonShapeNextText ytSpecButtonShapeNextMono ytSpecButtonShapeNextSizeM ytSpecButtonShapeNextIconOnlyDefault ytSpecButtonShapeNextEnableBackdropFilterExperiment" title="" aria-label="Search with your voice" aria-disabled="false">
<tp-yt-paper-tooltip offset="8" role="tooltip" tabindex="-1" aria-label="tooltip">
<button id="button" class="style-scope yt-icon-button" aria-label="Settings">
<a href="https://accounts.goo..." rel="nofollow" class="ytSpecButtonShapeNex..." aria-haspopup="false" force-new-state="true" aria-label="Sign in" aria-current="false" style="">
<a id="endpoint" class="yt-simple-endpoint style-scope ytd-mini-guide-entry-renderer" aria-selected="true" aria-label="Home" title="Home" href="/">
Showing first 10 of 15 audited elements.
Elements must only use supported ARIA attributes13 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 id="button" class="style-scope yt-icon-button" aria-label="Guide">
<a class="yt-simple-endpoint style-scope ytd-topbar-logo-renderer" id="logo" aria-label="" href="/" title="YouTube Home">
<button class="ytSpecButtonShapeNextHost ytSpecButtonShapeNextTonal ytSpecButtonShapeNextMono ytSpecButtonShapeNextSizeM ytSpecButtonShapeNextEnableBackdropFilterExperiment" title="" aria-label="Skip navigation" aria-disabled="false">
<input class="ytSearchboxComponentInput yt-searchbox-input title" name="search_query" aria-controls="i0" aria-expanded="true" type="text" autocomplete="off" autocorrect="off" spellcheck="false" aria-autocomplete="list" role="combobox" placeholder="Search">
<button aria-label="Search" class="ytSearchboxComponentSearchButton" title="Search"><span class="ytIconWrapperHost"><span class="yt-icon-shape"></span></span></button>
<button class="ytSpecButtonShapeNextHost ytSpecButtonShapeNextText ytSpecButtonShapeNextMono ytSpecButtonShapeNextSizeM ytSpecButtonShapeNextIconOnlyDefault ytSpecButtonShapeNextEnableBackdropFilterExperiment" title="" aria-label="Search with your voice" aria-disabled="false">
<tp-yt-paper-tooltip offset="8" role="tooltip" tabindex="-1" aria-label="tooltip">
<button id="button" class="style-scope yt-icon-button" aria-label="Settings">
<a href="https://accounts.goo..." rel="nofollow" class="ytSpecButtonShapeNex..." aria-haspopup="false" force-new-state="true" aria-label="Sign in" aria-current="false" style="">
<h2 id="title-container" class="style-scope ytd-feed-nudge-renderer" aria-label="Try searching to get started">
<yt-formatted-string id="title" class="style-scope ytd-feed-nudge-renderer" aria-label="Try searching to get started">Try searching to get started</yt-formatted-string>
</h2>Showing first 10 of 13 audited elements.
Elements should not have tabindex greater than zero2 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
<tp-yt-paper-tooltip offset="8" role="tooltip" tabindex="-1" aria-label="tooltip">
<a class="yt-simple-endpoint style-scope ytd-topbar-menu-button-renderer" tabindex="-1">
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 class="ytSearchboxComponentInput yt-searchbox-input title" name="search_query" aria-controls="i0" aria-expanded="true" type="text" autocomplete="off" autocorrect="off" spellcheck="false" aria-autocomplete="list" role="combobox" placeholder="Search">
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 class="ytSearchboxComponentInput yt-searchbox-input title" name="search_query" aria-controls="i0" aria-expanded="true" type="text" autocomplete="off" autocorrect="off" spellcheck="false" aria-autocomplete="list" role="combobox" placeholder="Search">
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 class="ytSearchboxComponentInput yt-searchbox-input title" name="search_query" aria-controls="i0" aria-expanded="true" type="text" autocomplete="off" autocorrect="off" spellcheck="false" aria-autocomplete="list" role="combobox" placeholder="Search">
Heading 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.
Audit Elements
<h2 id="title-container" class="style-scope ytd-feed-nudge-renderer" aria-label="Try searching to get started">
<yt-formatted-string id="title" class="style-scope ytd-feed-nudge-renderer" aria-label="Try searching to get started">Try searching to get started</yt-formatted-string>
</h2>Headings should not be empty1 element
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
<h2 id="title-container" class="style-scope ytd-feed-nudge-renderer" aria-label="Try searching to get started">
<yt-formatted-string id="title" class="style-scope ytd-feed-nudge-renderer" aria-label="Try searching to get started">Try searching to get started</yt-formatted-string>
</h2>IDs used in ARIA and labels must be unique1 element
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
<div id="i0" role="listbox" hidden="true" class="ytSearchboxComponentSuggestionsContainer ytSearchboxComponentSuggestionsContainerScrollable" style="min-width: 536px;"></div>
Inline text spacing must be adjustable with custom stylesheets5 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
<html style="font-size: 10px;font-family: Roboto, Arial, sans-serif;" lang="en" darker-dark-theme="" darker-dark-theme-deprecate="" system-icons="" color-version="v2_0" typography="" typography-spacing="">
<a href="https://accounts.goo..." rel="nofollow" class="ytSpecButtonShapeNex..." aria-haspopup="false" force-new-state="true" aria-label="Sign in" aria-current="false" style="">
<span class="ytAttributedStringHost ytAttributedStringWhiteSpaceNoWrap" role="text" style="">Sign in</span>
<ytd-two-column-browse-results-renderer class="style-scope ytd-browse grid grid-disabled" page-subtype="home" disable-grid-state-aware="" style="touch-action: pan-down;">
<ytd-rich-grid-renderer class="style-scope ytd-two-..." elements-per-row="3" is-default-grid="" style="--ytd-rich-grid-item...">
Interactive controls must not be nested5 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 id="button" class="style-scope yt-icon-button" aria-label="Guide">
<button class="ytSpecButtonShapeNextHost ytSpecButtonShapeNextTonal ytSpecButtonShapeNextMono ytSpecButtonShapeNextSizeM ytSpecButtonShapeNextEnableBackdropFilterExperiment" title="" aria-label="Skip navigation" aria-disabled="false">
<button aria-label="Search" class="ytSearchboxComponentSearchButton" title="Search"><span class="ytIconWrapperHost"><span class="yt-icon-shape"></span></span></button>
<button class="ytSpecButtonShapeNextHost ytSpecButtonShapeNextText ytSpecButtonShapeNextMono ytSpecButtonShapeNextSizeM ytSpecButtonShapeNextIconOnlyDefault ytSpecButtonShapeNextEnableBackdropFilterExperiment" title="" aria-label="Search with your voice" aria-disabled="false">
<button id="button" class="style-scope yt-icon-button" aria-label="Settings">
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination4 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
<ytd-masthead id="masthead" logo-type="YOUTUBE_LOGO" slot="masthead" class="masthead-finish" frosted-glass-mode="loading-without-chipbar" role="banner" mini-guide-visible="">
<yt-searchbox role="search" client-ve-type="10349" class="ytSearchboxComponentHost ytSearchboxComponentDesktop ytd-masthead">
<ytd-mini-guide-renderer class="style-scope ytd-app" role="navigation" mini-guide-visible="">
<ytd-browse class="style-scope ytd-page-manager" rounded-container="" page-subtype="home" responsive-sizing="COMPACT" role="main" mini-guide-visible="">
Links must have discernible text6 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 class="yt-simple-endpoint style-scope ytd-topbar-logo-renderer" id="logo" aria-label="" href="/" title="YouTube Home">
<a href="https://accounts.goo..." rel="nofollow" class="ytSpecButtonShapeNex..." aria-haspopup="false" force-new-state="true" aria-label="Sign in" aria-current="false" style="">
<a id="endpoint" class="yt-simple-endpoint style-scope ytd-mini-guide-entry-renderer" aria-selected="true" aria-label="Home" title="Home" href="/">
<a id="endpoint" class="yt-simple-endpoint style-scope ytd-mini-guide-entry-renderer" aria-selected="false" aria-label="Shorts" title="Shorts" href="/shorts/">
<a id="endpoint" class="yt-simple-endpoint style-scope ytd-mini-guide-entry-renderer" aria-selected="false" aria-label="Subscriptions" title="Subscriptions" href="/feed/subscriptions">
<a id="endpoint" class="yt-simple-endpoint style-scope ytd-mini-guide-entry-renderer" aria-selected="false" aria-label="You" title="You" href="/feed/you">
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
<ytd-browse class="style-scope ytd-page-manager" rounded-container="" page-subtype="home" responsive-sizing="COMPACT" role="main" mini-guide-visible="">
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 style="font-size: 10px;font-family: Roboto, Arial, sans-serif;" lang="en" darker-dark-theme="" darker-dark-theme-deprecate="" system-icons="" color-version="v2_0" typography="" typography-spacing="">
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 style="font-size: 10px;font-family: Roboto, Arial, sans-serif;" lang="en" darker-dark-theme="" darker-dark-theme-deprecate="" system-icons="" color-version="v2_0" typography="" typography-spacing="">
Required ARIA attributes must be provided8 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
<ytd-masthead id="masthead" logo-type="YOUTUBE_LOGO" slot="masthead" class="masthead-finish" frosted-glass-mode="loading-without-chipbar" role="banner" mini-guide-visible="">
<span class="ytAttributedStringHost ytAttributedStringWhiteSpaceNoWrap" role="text" style="">Skip navigation</span>
<yt-searchbox role="search" client-ve-type="10349" class="ytSearchboxComponentHost ytSearchboxComponentDesktop ytd-masthead">
<input class="ytSearchboxComponentInput yt-searchbox-input title" name="search_query" aria-controls="i0" aria-expanded="true" type="text" autocomplete="off" autocorrect="off" spellcheck="false" aria-autocomplete="list" role="combobox" placeholder="Search">
<tp-yt-paper-tooltip offset="8" role="tooltip" tabindex="-1" aria-label="tooltip">
<span class="ytAttributedStringHost ytAttributedStringWhiteSpaceNoWrap" role="text" style="">Sign in</span>
<ytd-mini-guide-renderer class="style-scope ytd-app" role="navigation" mini-guide-visible="">
<ytd-browse class="style-scope ytd-page-manager" rounded-container="" page-subtype="home" responsive-sizing="COMPACT" role="main" mini-guide-visible="">
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, viewport-fit=cover">
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, viewport-fit=cover">