Disney+disneyplus.com
Accessibility Score
Issues Found
Issues Found
SeriousARIA hidden element must not be focusable or contain focusable elements2 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.
Failing Elements
<i tabindex="0" role="none" data-tabster-dummy="" aria-hidden="true" style="position: fixed; height: 1px; width: 1px; opacity: 0.001; z-index: -1; content-visibility: hidden; top: 0px; left: 0px;"></i>
Fix all of the following:
- Focusable content should have tabindex="-1" or be removed from the DOM
<i tabindex="0" role="none" data-tabster-dummy="" aria-hidden="true" style="position: fixed; height: 1px; width: 1px; opacity: 0.001; z-index: -1; content-visibility: hidden; top: 0px; left: 0px;"></i>
Fix all of the following:
- Focusable content should have tabindex="-1" or be removed from the DOM
ModerateDocument 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.
Failing Elements
<html lang="en">
Fix all of the following:
- Document does not have a main landmark
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">
Fix all of the following:
- Page must have a level-one heading
Passed Audits
<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">
<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">
All page content should be contained by landmarks9 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="__next">
<source src="//cnbl-cdn.bamgrid.com/assets/27dd2e72fcb96a7019dea8210f72b593f5a635a85ddb4eb87bc80131dbede177/original" type="video/mp4">
<source src="//cnbl-cdn.bamgrid.com/assets/cabe72dbe90c3aa97e2565825189ed7ef4a8e052715879ff8590cf4750ca51f6/original" type="video/mp4">
<source src="//cnbl-cdn.bamgrid.com/assets/8084bbe655829745bd0153dd3ec12c90df92d48928277d0d66a99f84de920cdc/original" type="video/mp4">
<source src="//cnbl-cdn.bamgrid.com/assets/9c12ecf20f88c3d0852571a24a2244033abeafe99d3a2ed9ea71454f06fb491f/original" type="video/mp4">
<source src="//cnbl-cdn.bamgrid.com/assets/7c50a1bbb85b95289b6250bcaccfbc84c138a13e445ce5a927573e424573c1b5/original" type="video/mp4">
<source src="//cnbl-cdn.bamgrid.com/assets/b7db8f3cd3b1f026afe8ae2e49eeb9d7e9f1618ec413416a69a379fd5e464a36/original" type="video/mp4">
<next-route-announcer>
<p aria-live="assertive" id="__next-route-announcer__" role="alert" style="border: 0px; clip: rect(0px, 0px, 0px, 0px); height: 1px; margin: -1px; overflow: hidden; padding: 0px; position: absolute; top: 0px; width: 1px; white-space: nowrap; overflow-wrap: normal;"></p>
ARIA attributes must be used as specified for the element's role1 element
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
<p aria-live="assertive" id="__next-route-announcer__" role="alert" style="border: 0px; clip: rect(0px, 0px, 0px, 0px); height: 1px; margin: -1px; overflow: hidden; padding: 0px; position: absolute; top: 0px; width: 1px; white-space: nowrap; overflow-wrap: normal;"></p>
ARIA attributes must conform to valid names1 element
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
<p aria-live="assertive" id="__next-route-announcer__" role="alert" style="border: 0px; clip: rect(0px, 0px, 0px, 0px); height: 1px; margin: -1px; overflow: hidden; padding: 0px; position: absolute; top: 0px; width: 1px; white-space: nowrap; overflow-wrap: normal;"></p>
ARIA attributes must conform to valid values1 element
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
<p aria-live="assertive" id="__next-route-announcer__" role="alert" style="border: 0px; clip: rect(0px, 0px, 0px, 0px); height: 1px; margin: -1px; overflow: hidden; padding: 0px; position: absolute; top: 0px; width: 1px; white-space: nowrap; overflow-wrap: normal;"></p>
ARIA hidden element must not be focusable or contain focusable elements33 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 class="block w-[45px] h-[45px] rotate-90 rtl:-rotate-90" data-testid="chevron" viewBox="0 0 24 24" fill="currentColor" xmlns="http://www.w3.org/2000/svg" focusable="false" aria-hidden="true">
<svg class="block w-[45px] h-[45px] -rotate-90 rtl:rotate-90" data-testid="chevron" viewBox="0 0 24 24" fill="currentColor" xmlns="http://www.w3.org/2000/svg" focusable="false" aria-hidden="true">
<svg class="block w-[45px] h-[45px] rotate-90 rtl:-rotate-90" data-testid="chevron" viewBox="0 0 24 24" fill="currentColor" xmlns="http://www.w3.org/2000/svg" focusable="false" aria-hidden="true">
<svg class="block w-[45px] h-[45px] -rotate-90 rtl:rotate-90" data-testid="chevron" viewBox="0 0 24 24" fill="currentColor" xmlns="http://www.w3.org/2000/svg" focusable="false" aria-hidden="true">
<svg class="w-4" data-testid="chevron" viewBox="0 0 24 24" fill="currentColor" xmlns="http://www.w3.org/2000/svg" focusable="false" aria-hidden="true">
<svg class="block w-[45px] h-[45px] rotate-90 rtl:-rotate-90" data-testid="chevron" viewBox="0 0 24 24" fill="currentColor" xmlns="http://www.w3.org/2000/svg" focusable="false" aria-hidden="true">
<svg class="block w-[45px] h-[45px] -rotate-90 rtl:rotate-90" data-testid="chevron" viewBox="0 0 24 24" fill="currentColor" xmlns="http://www.w3.org/2000/svg" focusable="false" aria-hidden="true">
<svg class="block w-[45px] h-[45px] rotate-90 rtl:-rotate-90" data-testid="chevron" viewBox="0 0 24 24" fill="currentColor" xmlns="http://www.w3.org/2000/svg" focusable="false" aria-hidden="true">
<svg class="block w-[45px] h-[45px] -rotate-90 rtl:rotate-90" data-testid="chevron" viewBox="0 0 24 24" fill="currentColor" xmlns="http://www.w3.org/2000/svg" focusable="false" aria-hidden="true">
<svg class="block w-[45px] h-[45px] rotate-90 rtl:-rotate-90" data-testid="chevron" viewBox="0 0 24 24" fill="currentColor" xmlns="http://www.w3.org/2000/svg" focusable="false" aria-hidden="true">
Showing first 10 of 33 audited elements.
ARIA role should be appropriate for the element225 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
<i tabindex="0" role="none" data-tabster-dummy="" aria-hidden="true" style="position: fixed; height: 1px; width: 1px; opacity: 0.001; z-index: -1; content-visibility: hidden; top: 0px; left: 0px;"></i>
<div class="w-full overflow-x-scroll scroll-smooth snap-x snap-mandatory touch-pan-x pt-xs no-scrollbar scroll-ps-[calc(3.5vw+14px)]" data-testid="slider-container" role="region">
<div class="w-full overflow-x-scroll scroll-smooth snap-x snap-mandatory touch-pan-x pt-xs no-scrollbar scroll-ps-[calc(3.5vw+14px)]" data-testid="slider-container" role="region">
<div role="tabpanel" id="tabpanel-d6ynmkg67rw70fpm" aria-labelledby="tab-d6ynmkg67rw70fpm" class="px-[40px] pb-[24px] block mt-6">
<div role="table" class="bg-inherit" data-testid="comparison-chart-table">
<div class="sr-only" role="rowgroup">
<div role="row" class="grid max-md:flex max..." data-testid="comparison-chart-dat...">
<div role="columnheader" data-testid="comparison-chart-cell-header-cell-d6ynnpg67rw70fpr-1" class="flex w-full md:flex-1 flex-col justify-center px-1 md:px-3 bg-inherit flex-1 max-md:w-auto text-center items-center">
<div role="columnheader" data-testid="comparison-chart-cell-header-cell-d6ynnt867rw70fpt-2" class="flex w-full md:flex-1 flex-col justify-center px-1 md:px-3 bg-inherit flex-1 max-md:w-auto text-center items-center">
<div role="row" class="grid w-full max-md:f..." data-testid="comparison-chart-dat...">
Showing first 10 of 225 audited elements.
ARIA roles used must conform to valid values1 element
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
<p aria-live="assertive" id="__next-route-announcer__" role="alert" style="border: 0px; clip: rect(0px, 0px, 0px, 0px); height: 1px; margin: -1px; overflow: hidden; padding: 0px; position: absolute; top: 0px; width: 1px; white-space: nowrap; overflow-wrap: normal;"></p>
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 class="typeramp-inspire id-welcome disney" data-tabster="{"root":{}}">Deprecated ARIA roles must not be used1 element
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
<p aria-live="assertive" id="__next-route-announcer__" role="alert" style="border: 0px; clip: rect(0px, 0px, 0px, 0px); height: 1px; margin: -1px; overflow: hidden; padding: 0px; position: absolute; top: 0px; width: 1px; white-space: nowrap; overflow-wrap: normal;"></p>
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">
Elements must meet minimum color contrast ratio thresholds2 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
<select class="w-full text-[13px] md:text-[18px] px-3 pe-8 py-3 rounded border-none text-onSurface bg-surfaceVariant cursor-pointer overflow-hidden truncate flex-1 mx-2 appearance-none bg-no-repeat focus:outline-2 focus:outline-outline" aria-label="Selection {item_type} option"><select name="langSelector" class="_1m0ltk2 _1m0ltk7" data-testid="langSelector" id="language-selector" data-key="langSelect">
Elements must only use permitted ARIA attributes1 element
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
<p aria-live="assertive" id="__next-route-announcer__" role="alert" style="border: 0px; clip: rect(0px, 0px, 0px, 0px); height: 1px; margin: -1px; overflow: hidden; padding: 0px; position: absolute; top: 0px; width: 1px; white-space: nowrap; overflow-wrap: normal;"></p>
Elements must only use supported ARIA attributes1 element
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
<p aria-live="assertive" id="__next-route-announcer__" role="alert" style="border: 0px; clip: rect(0px, 0px, 0px, 0px); height: 1px; margin: -1px; overflow: hidden; padding: 0px; position: absolute; top: 0px; width: 1px; white-space: nowrap; overflow-wrap: normal;"></p>
IDs used in ARIA and labels must be unique21 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
<div class="flex justify-center gap-[15px] flex-1 pt-0 px-4 pb-5" id="flipcard-summary-:R69qimupm:"><h4 class="whitespace-pre-wrap text-center">Discover the all-new Disney+ Perks</h4></div>
<div class="flex justify-center gap-[15px] flex-1 pt-0 px-4 pb-5" id="flipcard-summary-:R6aqimupm:"><h4 class="whitespace-pre-wrap text-center">Access all of ESPN's networks & services</h4></div>
<div class="flex justify-center gap-[15px] flex-1 pt-0 px-4 pb-5" id="flipcard-summary-:R6bqimupm:"><h4 class="whitespace-pre-wrap text-center">Set parental controls</h4></div>
<div class="flex justify-center gap-[15px] flex-1 pt-0 px-4 pb-5" id="flipcard-summary-:R6cqimupm:"><h4 class="whitespace-pre-wrap text-center">Watch on multiple devices at once</h4></div>
<div class="flex justify-center gap-[15px] flex-1 pt-0 px-4 pb-5" id="flipcard-summary-:R6dqimupm:"><h4 class="whitespace-pre-wrap text-center">Stunning visuals and sound</h4></div>
<div class="flex justify-center gap-[15px] flex-1 pt-0 px-4 pb-5" id="flipcard-summary-:R6eqimupm:"><h4 class="whitespace-pre-wrap text-center">Stream Hulu and ESPN on Disney+ with an eligible plan</h4></div>
<summary aria-controls="accordion-content-d5..." aria-expanded="false" id="accordion-button-d52..." class="[&::-webkit-details-...">
<div class="py-0 px-6 w-full overflow-hidden max-h-[var(--accordion-max-height)]" role="region" id="accordion-content-d52vvhkv8ey325uw" aria-labelledby="accordion-button-d52vvhkv8ey325uw" style="--accordion-max-height: 0px; transition: max-height 0.18s cubic-bezier(0.4, 0, 0.2, 1);">
<summary aria-controls="accordion-content-d2..." aria-expanded="false" id="accordion-button-d20..." class="[&::-webkit-details-...">
<div class="py-0 px-6 w-full overflow-hidden max-h-[var(--accordion-max-height)]" role="region" id="accordion-content-d20fcbezwv6n0b26" aria-labelledby="accordion-button-d20fcbezwv6n0b26" style="--accordion-max-height: 0px; transition: max-height 0.18s cubic-bezier(0.4, 0, 0.2, 1);">
Showing first 10 of 21 audited elements.
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">
Required ARIA attributes must be provided1 element
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
<p aria-live="assertive" id="__next-route-announcer__" role="alert" style="border: 0px; clip: rect(0px, 0px, 0px, 0px); height: 1px; margin: -1px; overflow: hidden; padding: 0px; position: absolute; top: 0px; width: 1px; white-space: nowrap; overflow-wrap: normal;"></p>
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">