Apple TV+ tv.apple.com
Accessibility score
League position
10thof 10
Issues found
5
Audits passed
47
Accessibility score over time
weekly scans · last 6 months- Good · 90+
- Needs improvement · 70–89
- Poor · Below 70
This month's scan
Issues found
CriticalCertain ARIA roles must be contained by particular parents7 elements
ARIA roles with missing required parent elements cannot function as intended for assistive technology users. Parent-child relationships convey essential hierarchy and context, like showing where an item sits within a tree structure. Without proper parents, this critical relationship information is lost.
Failing Elements
<li class="carousel__item svelte-lxalbw" role="tab" aria-selected="true">
Fix any of the following:
- Required ARIA parent role not present: tablist
<li class="carousel__item svelte-lxalbw" role="tab" aria-selected="false">
Fix any of the following:
- Required ARIA parent role not present: tablist
<li class="carousel__item svelte-lxalbw" role="tab" aria-selected="false">
Fix any of the following:
- Required ARIA parent role not present: tablist
<li class="carousel__item svelte-lxalbw" role="tab" aria-selected="false">
Fix any of the following:
- Required ARIA parent role not present: tablist
<li class="carousel__item svelte-lxalbw" role="tab" aria-selected="false">
Fix any of the following:
- Required ARIA parent role not present: tablist
<li class="carousel__item svelte-lxalbw" role="tab" aria-selected="false">
Fix any of the following:
- Required ARIA parent role not present: tablist
<li class="carousel__item svelte-lxalbw" role="tab" aria-selected="false">
Fix any of the following:
- Required ARIA parent role not present: tablist
CriticalARIA 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.
Failing Elements
<button id="tab-0" role="tab" aria-selected="true" aria-controls="tabpanel-0" data-testid="pagination-dot-0" class="pagination__dot svelte-1hqu0wd dot--visible-first dot--active dot--visible"><span class="svelte-1hqu0wd">Item 1</span> </button>
Fix all of the following:
- Invalid ARIA attribute value: aria-controls="tabpanel-0"
CriticalButtons must have discernible text4 elements
Screen reader users cannot determine the purpose of buttons without an accessible name. Without a name, users don't know what action the button will perform when activated.
Failing Elements
<button class="svelte-1tpikrn">
Fix any of the following:
- Element does not have inner text that is visible to screen readers
- aria-label attribute does not exist or is empty
- aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
- Element has no title attribute
- Element does not have an implicit (wrapped) <label>
- Element does not have an explicit <label>
- Element's default semantics were not overridden with role="none" or role="presentation"
<button class="pagination-back svelte-99lgtg" disabled="">
Fix any of the following:
- Element does not have inner text that is visible to screen readers
- aria-label attribute does not exist or is empty
- aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
- Element has no title attribute
- Element does not have an implicit (wrapped) <label>
- Element does not have an explicit <label>
- Element's default semantics were not overridden with role="none" or role="presentation"
<button class="pagination-next svelte-99lgtg">
Fix any of the following:
- Element does not have inner text that is visible to screen readers
- aria-label attribute does not exist or is empty
- aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
- Element has no title attribute
- Element does not have an implicit (wrapped) <label>
- Element does not have an explicit <label>
- Element's default semantics were not overridden with role="none" or role="presentation"
<button class="carousel__pause-button svelte-lxalbw" data-testid="carousel-pause-button">
Fix any of the following:
- Element does not have inner text that is visible to screen readers
- aria-label attribute does not exist or is empty
- aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
- Element has no title attribute
- Element does not have an implicit (wrapped) <label>
- Element does not have an explicit <label>
- Element's default semantics were not overridden with role="none" or role="presentation"
Serious<ul> and <ol> must only directly contain <li>, <script> or <template> elements1 element
Lists must contain only li elements as direct children (besides non-content elements like script or style). When other content elements appear within ul or ol tags, screen readers cannot properly inform users they're listening to list items, breaking the expected list navigation experience.
Failing Elements
<ul class="carousel__list svelte-lxalbw">
Fix all of the following:
- List element has direct children that are not allowed: [role=tab]
SeriousInteractive controls must not be nested7 elements
Nested interactive elements create empty tab stops where screen readers remain silent. When users tab to a focusable element inside another interactive control, they receive no information about its name, role, or state, creating a confusing and broken navigation experience.
Failing Elements
<li class="carousel__item svelte-lxalbw" role="tab" aria-selected="true">
Fix any of the following:
- Element has focusable descendants. Move them outside of the element, or remove them.
<li class="carousel__item svelte-lxalbw" role="tab" aria-selected="false">
Fix any of the following:
- Element has focusable descendants. Move them outside of the element, or remove them.
<li class="carousel__item svelte-lxalbw" role="tab" aria-selected="false">
Fix any of the following:
- Element has focusable descendants. Move them outside of the element, or remove them.
<li class="carousel__item svelte-lxalbw" role="tab" aria-selected="false">
Fix any of the following:
- Element has focusable descendants. Move them outside of the element, or remove them.
<li class="carousel__item svelte-lxalbw" role="tab" aria-selected="false">
Fix any of the following:
- Element has focusable descendants. Move them outside of the element, or remove them.
<li class="carousel__item svelte-lxalbw" role="tab" aria-selected="false">
Fix any of the following:
- Element has focusable descendants. Move them outside of the element, or remove them.
<li class="carousel__item svelte-lxalbw" role="tab" aria-selected="false">
Fix any of the following:
- Element has focusable descendants. Move them outside of the element, or remove them.
Passed audits47 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 dir="ltr" lang="en-US" hydrated="">
<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 dir="ltr" lang="en-US" hydrated="">
<li> elements must be contained in a <ul> or <ol>80 elements
Lists require proper semantic hierarchy with ul or ol parent elements and li child elements. This structure allows screen readers to announce when users enter a list, how many items it contains, and which item they're currently on, providing essential context for understanding the content.
Audit Elements
<li class="offer svelte-17b416c">
<li class="offer svelte-17b416c">
<li style="transform: matrix(1, 0, 0, 1, 0, 55); opacity: 0;">New Releases Weekly.</li>
<li style="transform: matrix(1, 0, 0, 1, 0, 55); opacity: 0;">No Ads on Apple TV.</li>
<li style="transform: matrix(1, 0, 0, 1, 0, 55); opacity: 0;">Watch on Any Device.</li>
Showing first 5 of 80 audited elements.
<ul> and <ol> must only directly contain <li>, <script> or <template> elements16 elements
Lists must contain only li elements as direct children (besides non-content elements like script or style). When other content elements appear within ul or ol tags, screen readers cannot properly inform users they're listening to list items, breaking the expected list navigation experience.
Audit Elements
<ul class="platter svelte-17b416c">
<ul>
<ul class="plans-list svelte-99lgtg">
<ul class="badges svelte-1atbtw4"><li class="svelte-1atbtw4">No ads</li></ul>
<ul class="description svelte-1atbtw4">
Showing first 5 of 16 audited elements.
All page content should be contained by landmarks520 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 class="body-container">
<div class="app-container svelte-1x5dh6f app-container--hard-wall" data-testid="app-container">
<div data-testid="main-section" class="scrollable-page svelte-4odvlq" id="scrollable-page" data-main-content="" aria-hidden="false">
<main data-testid="main" class="svelte-fhtihb">
<div class="content-container svelte-fhtihb" data-testid="content-container">
Showing first 5 of 520 audited elements.
All touch targets must be 24px large, or leave sufficient space57 elements
Touch targets must be large enough or spaced far enough apart to be activated without accidentally hitting adjacent controls. This helps users on mobile devices, people with hand tremors or mobility impairments, users in shaking environments like public transit, and anyone using one hand or large fingers to interact with the interface.
Audit Elements
<a href="https://tv.apple.com" data-testid="open-in-tv" class="open-in-tv svelte-lmovmu">
<button tabindex="0" data-testid="sign-in-button" class="commerce-button signin svelte-q2kuuf signin--compact">
<button class="theme-primary svelte-hnf0gl" data-testid="capsule-button"> <span class="label svelte-hnf0gl">Accept Free Trial</span></button>
<button class="theme-primary svelte-hnf0gl" data-testid="capsule-button"> <span class="label svelte-hnf0gl">Bundle and Save</span></button>
<button class="svelte-1tpikrn">
Showing first 5 of 57 audited elements.
Alternative text of images should not be repeated as text15 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="" loading="lazy" src="/assets/artwork/1x1.gif" class="svelte-4qfefc">
<img alt="Ted Lasso" class="artwork-component__contents artwork-component__image svelte-1fla0gl" loading="lazy" src="/assets/artwork/1x1.gif" decoding="async" width="800" height="1000" fetchpriority="auto" style="opacity: 1;">
<img alt="Ted Lasso" loading="lazy" src="/assets/artwork/1x1.gif" class="svelte-4qfefc">
<img alt="Mayday" class="artwork-component__contents artwork-component__image svelte-1fla0gl" loading="lazy" src="/assets/artwork/1x1.gif" decoding="async" width="800" height="1000" fetchpriority="auto" style="opacity: 1;">
<img alt="Mayday" loading="lazy" src="/assets/artwork/1x1.gif" class="svelte-4qfefc">
Showing first 5 of 15 audited elements.
ARIA attributes must be used as specified for the element's role36 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
<div data-testid="main-section" class="scrollable-page svelte-4odvlq" id="scrollable-page" data-main-content="" aria-hidden="false">
<div class="header-image svelte-1atbtw4" aria-hidden=""><div class="logo theme-dark svelte-88gm1e"><div class="artwork brand apple-tv svelte-88gm1e"></div> </div></div>
<div class="header-image svelte-1atbtw4" aria-hidden=""><div class="logo theme-dark svelte-88gm1e partner"><div class="artwork brand apple-tv svelte-88gm1e"></div> <span class="divider svelte-88gm1e"></span> <div class="artwork brand partner-brand peacock svelte-88gm1e"></div></div></div>
<section class="subscription-plans svelte-99lgtg" aria-labelledby="sec-heading-i6snrij">
<div class="header-image svelte-1atbtw4" aria-hidden=""><div class="logo theme-dark svelte-88gm1e"><div class="artwork brand apple-tv svelte-88gm1e"></div> </div></div>
Showing first 5 of 36 audited elements.
ARIA attributes must conform to valid names36 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
<div data-testid="main-section" class="scrollable-page svelte-4odvlq" id="scrollable-page" data-main-content="" aria-hidden="false">
<div class="header-image svelte-1atbtw4" aria-hidden=""><div class="logo theme-dark svelte-88gm1e"><div class="artwork brand apple-tv svelte-88gm1e"></div> </div></div>
<div class="header-image svelte-1atbtw4" aria-hidden=""><div class="logo theme-dark svelte-88gm1e partner"><div class="artwork brand apple-tv svelte-88gm1e"></div> <span class="divider svelte-88gm1e"></span> <div class="artwork brand partner-brand peacock svelte-88gm1e"></div></div></div>
<section class="subscription-plans svelte-99lgtg" aria-labelledby="sec-heading-i6snrij">
<div class="header-image svelte-1atbtw4" aria-hidden=""><div class="logo theme-dark svelte-88gm1e"><div class="artwork brand apple-tv svelte-88gm1e"></div> </div></div>
Showing first 5 of 36 audited elements.
ARIA attributes must conform to valid values28 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
<div data-testid="main-section" class="scrollable-page svelte-4odvlq" id="scrollable-page" data-main-content="" aria-hidden="false">
<section class="subscription-plans svelte-99lgtg" aria-labelledby="sec-heading-i6snrij">
<section class="content-lockup-shelf svelte-aj6kq5" data-testid="content-lockup-shelf" aria-labelledby="sec-heading-ucqkgxs">
<li class="carousel__item svelte-lxalbw" role="tab" aria-selected="true">
<button data-testid="epic-showcase-item" class="epic-showcase-item portrait flavor-1 epic-artwork svelte-139c878 content-lockup-variant" aria-label="">
Showing first 5 of 28 audited elements.
ARIA hidden element must not be focusable or contain focusable elements26 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
<amp-background-video aria-hidden="true" class="svelte-14j5wys background-video cover" muted="" fit="cover" hydrated="" style="--joe-color: rgb(0,0,0);"></amp-background-video>
<div class="video-control__container svelte-1mqmv95" data-testid="video-control-container" aria-hidden="true">
<div class="slides svelte-oryfud" aria-hidden="true">
<div class="snap-range svelte-oryfud" aria-hidden="true"></div>
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 167.294 120" aria-hidden="true">
Showing first 5 of 26 audited elements.
ARIA role should be appropriate for the element30 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
<li class="carousel__item svelte-lxalbw" role="tab" aria-selected="true">
<li class="carousel__item svelte-lxalbw" role="tab" aria-selected="false">
<li class="carousel__item svelte-lxalbw" role="tab" aria-selected="false">
<li class="carousel__item svelte-lxalbw" role="tab" aria-selected="false">
<li class="carousel__item svelte-lxalbw" role="tab" aria-selected="false">
Showing first 5 of 30 audited elements.
ARIA roles used must conform to valid values16 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
<li class="carousel__item svelte-lxalbw" role="tab" aria-selected="true">
<li class="carousel__item svelte-lxalbw" role="tab" aria-selected="false">
<li class="carousel__item svelte-lxalbw" role="tab" aria-selected="false">
<li class="carousel__item svelte-lxalbw" role="tab" aria-selected="false">
<li class="carousel__item svelte-lxalbw" role="tab" aria-selected="false">
Showing first 5 of 16 audited elements.
ARIA tab nodes must have an accessible name7 elements
Ensure every ARIA tab node has an accessible name
Audit Elements
<li class="carousel__item svelte-lxalbw" role="tab" aria-selected="true">
<li class="carousel__item svelte-lxalbw" role="tab" aria-selected="false">
<li class="carousel__item svelte-lxalbw" role="tab" aria-selected="false">
<li class="carousel__item svelte-lxalbw" role="tab" aria-selected="false">
<li class="carousel__item svelte-lxalbw" role="tab" aria-selected="false">
Showing first 5 of 7 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 data-anim-scroll-group="body">
Buttons must have discernible text23 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 tabindex="0" data-testid="sign-in-button" class="commerce-button signin svelte-q2kuuf signin--compact">
<button class="theme-primary svelte-hnf0gl" data-testid="capsule-button"> <span class="label svelte-hnf0gl">Accept Free Trial</span></button>
<button class="theme-primary svelte-hnf0gl" data-testid="capsule-button"> <span class="label svelte-hnf0gl">Bundle and Save</span></button>
<button class="theme-outline svelte-hnf0gl" data-testid="capsule-button"> <span class="label svelte-hnf0gl">View Plans</span></button>
<button class="theme-primary svelte-hnf0gl" data-testid="capsule-button"> <span class="label svelte-hnf0gl">Subscribe</span></button>
Showing first 5 of 23 audited elements.
Certain ARIA roles must be contained by particular parents7 elements
ARIA roles with missing required parent elements cannot function as intended for assistive technology users. Parent-child relationships convey essential hierarchy and context, like showing where an item sits within a tree structure. Without proper parents, this critical relationship information is lost.
Audit Elements
<button id="tab-0" role="tab" aria-selected="true" aria-controls="tabpanel-0" data-testid="pagination-dot-0" class="pagination__dot svelte-1hqu0wd dot--visible-first dot--active dot--visible"><span class="svelte-1hqu0wd">Item 1</span> </button>
<button id="tab-1" role="tab" aria-selected="false" aria-controls="tabpanel-1" data-testid="pagination-dot-1" class="pagination__dot svelte-1hqu0wd dot--visible-second dot--visible"><span class="svelte-1hqu0wd">Item 2</span> </button>
<button id="tab-2" role="tab" aria-selected="false" aria-controls="tabpanel-2" data-testid="pagination-dot-2" class="pagination__dot svelte-1hqu0wd dot--visible"><span class="svelte-1hqu0wd">Item 3</span> </button>
<button id="tab-3" role="tab" aria-selected="false" aria-controls="tabpanel-3" data-testid="pagination-dot-3" class="pagination__dot svelte-1hqu0wd dot--visible"><span class="svelte-1hqu0wd">Item 4</span> </button>
<button id="tab-4" role="tab" aria-selected="false" aria-controls="tabpanel-4" data-testid="pagination-dot-4" class="pagination__dot svelte-1hqu0wd dot--visible"><span class="svelte-1hqu0wd">Item 5</span> </button>
Showing first 5 of 7 audited elements.
Certain ARIA roles must contain particular children2 elements
ARIA roles missing required child elements cannot perform their intended accessibility functions. Children provide essential context, like how a treeitem relates to its parent container and siblings. Without proper children, assistive technologies cannot convey this structural information to users.
Audit Elements
<div role="tablist" class="pagination-dots__list svelte-1hqu0wd pagination--start pagination--end pagination-dots__list--no-scaling">
<ul class="snap-points svelte-oryfud" role="list" aria-label="Every lap, match, and at-bat. All right here.">
Content must reflow without two-dimensional scrolling0 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.
Deprecated ARIA roles must not be used16 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
<li class="carousel__item svelte-lxalbw" role="tab" aria-selected="true">
<li class="carousel__item svelte-lxalbw" role="tab" aria-selected="false">
<li class="carousel__item svelte-lxalbw" role="tab" aria-selected="false">
<li class="carousel__item svelte-lxalbw" role="tab" aria-selected="false">
<li class="carousel__item svelte-lxalbw" role="tab" aria-selected="false">
Showing first 5 of 16 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 dir="ltr" lang="en-US" hydrated="">
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 class="landing-page-header full-width svelte-4tgynq">
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 class="cta svelte-1atbtw4"><div style="display: contents; --size: 12px;"><button class="theme-primary svelte-hnf0gl" data-testid="capsule-button"> <span class="label svelte-hnf0gl">Accept Free Trial</span></button></div></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 data-testid="main" class="svelte-fhtihb">
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 dir="ltr" lang="en-US" hydrated="">
Elements marked as presentational should be consistently ignored1 element
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 alt="" loading="lazy" src="/assets/artwork/1x1.gif" class="svelte-4qfefc">
Elements must only use permitted ARIA attributes36 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
<div data-testid="main-section" class="scrollable-page svelte-4odvlq" id="scrollable-page" data-main-content="" aria-hidden="false">
<div class="header-image svelte-1atbtw4" aria-hidden=""><div class="logo theme-dark svelte-88gm1e"><div class="artwork brand apple-tv svelte-88gm1e"></div> </div></div>
<div class="header-image svelte-1atbtw4" aria-hidden=""><div class="logo theme-dark svelte-88gm1e partner"><div class="artwork brand apple-tv svelte-88gm1e"></div> <span class="divider svelte-88gm1e"></span> <div class="artwork brand partner-brand peacock svelte-88gm1e"></div></div></div>
<section class="subscription-plans svelte-99lgtg" aria-labelledby="sec-heading-i6snrij">
<div class="header-image svelte-1atbtw4" aria-hidden=""><div class="logo theme-dark svelte-88gm1e"><div class="artwork brand apple-tv svelte-88gm1e"></div> </div></div>
Showing first 5 of 36 audited elements.
Elements must only use supported ARIA attributes36 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
<div data-testid="main-section" class="scrollable-page svelte-4odvlq" id="scrollable-page" data-main-content="" aria-hidden="false">
<div class="header-image svelte-1atbtw4" aria-hidden=""><div class="logo theme-dark svelte-88gm1e"><div class="artwork brand apple-tv svelte-88gm1e"></div> </div></div>
<div class="header-image svelte-1atbtw4" aria-hidden=""><div class="logo theme-dark svelte-88gm1e partner"><div class="artwork brand apple-tv svelte-88gm1e"></div> <span class="divider svelte-88gm1e"></span> <div class="artwork brand partner-brand peacock svelte-88gm1e"></div></div></div>
<section class="subscription-plans svelte-99lgtg" aria-labelledby="sec-heading-i6snrij">
<div class="header-image svelte-1atbtw4" aria-hidden=""><div class="logo theme-dark svelte-88gm1e"><div class="artwork brand apple-tv svelte-88gm1e"></div> </div></div>
Showing first 5 of 36 audited elements.
Elements should not have tabindex greater than zero9 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 tabindex="0" data-testid="sign-in-button" class="commerce-button signin svelte-q2kuuf signin--compact">
<summary tabindex="0" class="svelte-5os2io">
<summary tabindex="0" class="svelte-5os2io">
<summary tabindex="0" class="svelte-5os2io">
<summary tabindex="0" class="svelte-5os2io">
Showing first 5 of 9 audited elements.
Focused elements must not be entirely hidden by author-created content46 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
<a href="https://tv.apple.com" data-testid="open-in-tv" class="open-in-tv svelte-lmovmu">
<button tabindex="0" data-testid="sign-in-button" class="commerce-button signin svelte-q2kuuf signin--compa...">
<button class="theme-primary svelte-hnf0gl" data-testid="capsule-button">
<button class="theme-primary svelte-hnf0gl" data-testid="capsule-button">
<button class="svelte-1tpikrn">
Showing first 5 of 46 audited elements.
Heading levels should only increase by one19 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
<h1 class="title svelte-1tpikrn">Apple Originals, Formula 1<sup>®</sup>, MLS, and more. All on Apple TV.</h1>
<h2 class="sticky-cta__headline svelte-1qooxhq" data-testid="content-lockup-headline" id="sec-heading-i6snrij">Apple Originals, Formula 1®, MLS, and more. Plans start at $14.99/month.</h2>
<h2 class="visually-hidden svelte-1atbtw4">Apple TV</h2>
<h2 class="visually-hidden svelte-1atbtw4">Apple TV and Peacock</h2>
<h2 class="visually-hidden svelte-1atbtw4">Apple TV and Peacock Premium Plus</h2>
Showing first 5 of 19 audited elements.
Headings should not be empty19 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
<h1 class="title svelte-1tpikrn">Apple Originals, Formula 1<sup>®</sup>, MLS, and more. All on Apple TV.</h1>
<h2 class="sticky-cta__headline svelte-1qooxhq" data-testid="content-lockup-headline" id="sec-heading-i6snrij">Apple Originals, Formula 1®, MLS, and more. Plans start at $14.99/month.</h2>
<h2 class="visually-hidden svelte-1atbtw4">Apple TV</h2>
<h2 class="visually-hidden svelte-1atbtw4">Apple TV and Peacock</h2>
<h2 class="visually-hidden svelte-1atbtw4">Apple TV and Peacock Premium Plus</h2>
Showing first 5 of 19 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
<h2 class="sticky-cta__headline svelte-1qooxhq" data-testid="content-lockup-headline" id="sec-heading-i6snrij">Apple Originals, Formula 1®, MLS, and more. Plans start at $14.99/month.</h2>
<h2 class="content-lockup-header__headline svelte-xlng1b" data-testid="content-lockup-headline" id="sec-heading-ucqkgxs">Thousands of hours of exclusive shows and movies with new releases weekly.</h2>
<h2 class="landing-devices__headline svelte-15s8z0" id="sec-heading-hz5ijce">Watch here and on your TV.</h2>
<h2 class="svelte-13u5em7" id="sec-heading-qfzxigq">Questions? Answers.</h2>
Images must have alternative text15 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="" loading="lazy" src="/assets/artwork/1x1.gif" class="svelte-4qfefc">
<img alt="Ted Lasso" class="artwork-component__contents artwork-component__image svelte-1fla0gl" loading="lazy" src="/assets/artwork/1x1.gif" decoding="async" width="800" height="1000" fetchpriority="auto" style="opacity: 1;">
<img alt="Ted Lasso" loading="lazy" src="/assets/artwork/1x1.gif" class="svelte-4qfefc">
<img alt="Mayday" class="artwork-component__contents artwork-component__image svelte-1fla0gl" loading="lazy" src="/assets/artwork/1x1.gif" decoding="async" width="800" height="1000" fetchpriority="auto" style="opacity: 1;">
<img alt="Mayday" loading="lazy" src="/assets/artwork/1x1.gif" class="svelte-4qfefc">
Showing first 5 of 15 audited elements.
Inline text spacing must be adjustable with custom stylesheets4 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
<section class="unentitled-epic-stage svelte-1tpikrn" style="opacity: 1;">
<article class="lockup svelte-1tpikrn" style="transform: matrix(1, 0, 0, 1, 0, 0); opacity: 1;">
<div style="display: contents; --size: 12px;"><button class="theme-primary svelte-hnf0gl" data-testid="capsule-button"> <span class="label svelte-hnf0gl">Accept Free Trial</span></button></div>
<div style="display: contents; --size: 12px;"><button class="theme-primary svelte-hnf0gl" data-testid="capsule-button"> <span class="label svelte-hnf0gl">Bundle and Save</span></button></div>
Interactive controls must not be nested49 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 tabindex="0" data-testid="sign-in-button" class="commerce-button signin svelte-q2kuuf signin--compact">
<button class="theme-primary svelte-hnf0gl" data-testid="capsule-button"> <span class="label svelte-hnf0gl">Accept Free Trial</span></button>
<button class="theme-primary svelte-hnf0gl" data-testid="capsule-button"> <span class="label svelte-hnf0gl">Bundle and Save</span></button>
<button class="svelte-1tpikrn">
<button class="theme-outline svelte-hnf0gl" data-testid="capsule-button"> <span class="label svelte-hnf0gl">View Plans</span></button>
Showing first 5 of 49 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
<a href="https://tv.apple.com" data-testid="open-in-tv" class="open-in-tv svelte-lmovmu">
<button tabindex="0" data-testid="sign-in-button" class="commerce-button signin svelte-q2kuuf signin--compa...">
<button class="theme-primary svelte-hnf0gl" data-testid="capsule-button">
<button class="theme-primary svelte-hnf0gl" data-testid="capsule-button">
<button class="svelte-1tpikrn">
Showing first 5 of 50 audited elements.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination6 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
<main data-testid="main" class="svelte-fhtihb">
<section class="subscription-plans svelte-99lgtg" aria-labelledby="sec-heading-i6snrij">
<section class="content-lockup-shelf svelte-aj6kq5" data-testid="content-lockup-shelf" aria-labelledby="sec-heading-ucqkgxs">
<nav class="pagination-dots svelte-1hqu0wd" data-testid="pagination-dots" aria-label="">
<section data-testid="devices-module" class="landing-devices svelte-15s8z0" aria-labelledby="sec-heading-hz5ijce">
Showing first 5 of 6 audited elements.
Links must have discernible text24 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 href="https://tv.apple.com" data-testid="open-in-tv" class="open-in-tv svelte-lmovmu">
<a href="https://tv.apple.com/us/apple-tv" rel="noopener" dir="auto">Browse Apple TV</a>
<a href="https://tv.apple.com/us/channel/formula-1/tvs.sbd.241000" rel="noopener" dir="auto">Formula 1®</a>
<a href="https://tv.apple.com/us/channel/mls/tvs.sbd.7000" rel="noopener" dir="auto">Major League Soccer</a>
<a href="https://tv.apple.com/us/room/edt.item.62327df1-6874-470e-98b2-a5bbeac509a2" rel="noopener" dir="auto">Friday Night Baseball</a>
Showing first 5 of 24 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 data-testid="main" class="svelte-fhtihb">
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 dir="ltr" lang="en-US" hydrated="">
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 dir="ltr" lang="en-US" hydrated="">
Required ARIA attributes must be provided16 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
<li class="carousel__item svelte-lxalbw" role="tab" aria-selected="true">
<li class="carousel__item svelte-lxalbw" role="tab" aria-selected="false">
<li class="carousel__item svelte-lxalbw" role="tab" aria-selected="false">
<li class="carousel__item svelte-lxalbw" role="tab" aria-selected="false">
<li class="carousel__item svelte-lxalbw" role="tab" aria-selected="false">
Showing first 5 of 16 audited elements.
Scrollable region must have keyboard access3 elements
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 data-testid="main-section" class="scrollable-page svelte-4odvlq" id="scrollable-page" data-main-content="" aria-hidden="false">
<ul class="plans-list svelte-99lgtg">
<ul class="carousel__list svelte-lxalbw">
Summary elements must have discernible text8 elements
Screen reader users cannot identify the purpose of summary elements without an accessible name. Without a name, users won't understand what the control does and will likely miss information hidden within the associated details element.
Audit Elements
<summary tabindex="0" class="svelte-5os2io">
<summary tabindex="0" class="svelte-5os2io">
<summary tabindex="0" class="svelte-5os2io">
<summary tabindex="0" class="svelte-5os2io">
<summary tabindex="0" class="svelte-5os2io">
Showing first 5 of 8 audited elements.
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">
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">
How does your site stack up against Apple TV+?
Run the same automated WCAG 2.2 checks we run on the scoreboard.
More in Streaming & Entertainment