Crunchyroll crunchyroll.com
Accessibility score
League position
6thof 10
Issues found
11
Audits passed
49
Accessibility score over time
weekly scans · last 6 months- Good · 90+
- Needs improvement · 70–89
- Poor · Below 70
This month's scan
Issues found
SeriousARIA dialog and alertdialog nodes should have an accessible name1 element
Screen reader users cannot identify the purpose of role="dialog" or role="alertdialog" elements without an accessible name. This leaves users confused about what dialog they've encountered and what it contains.
Failing Elements
<div tabindex="-1" role="dialog" class="content-wrapper--MF5LS">
Fix any of the following:
- aria-label attribute does not exist or is empty
- aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
- Element has no title attribute
SeriousElements must have their visible text as part of their accessible name3 elements
Interactive widgets that support name from content must have aria-label or aria-labelledby values that match their visible text. Mismatches confuse voice control users who speak the visible label but activate a different function based on the hidden accessible name.
Failing Elements
<button aria-label="button-premium" tabindex="0" class="button--xqVd0 button--is-type-one--3uIzT cr-start-premium-button" data-t="button-premium" type="button"><span class="call-to-action--PEidl call-to-action--is-m--RVdkI button__cta--LOqDH">Start free trial</span></button>
Fix any of the following:
- Text inside the element is not included in the accessible name
<button aria-label="Please be alert to potential phishing attempts. Crunchyroll will never ask for your personal information via email or SMS." tabindex="1" class="button--xqVd0 button--is-type-one--3uIzT" data-t="grant-anonymous-consent-btn" type="button">
Fix any of the following:
- Text inside the element is not included in the accessible name
<div role="button" aria-label="Language" tabindex="0" class="dropdown-trigger--P--FX dropdown-trigger--is-styled--Q3nCd select-trigger--is-type-filled--4DySC trigger" aria-haspopup="listbox" aria-expanded="false" data-t="language-select-trigger" ...>
Fix any of the following:
- Text inside the element is not included in the accessible name
Serious<ul> and <ol> must only directly contain <li>, <script> or <template> elements7 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.
Failing Elements
<ul class="section-list">
Fix all of the following:
- List element has direct children that are not allowed: a
<ul class="section-list">
Fix all of the following:
- List element has direct children that are not allowed: a
<ul class="section-list">
Fix all of the following:
- List element has direct children that are not allowed: a
<ul class="section-list">
Fix all of the following:
- List element has direct children that are not allowed: a
<ul class="section-list">
Fix all of the following:
- List element has direct children that are not allowed: a, button
<ul class="section-list">
Fix all of the following:
- List element has direct children that are not allowed: a
<ul class="section-list">
Fix all of the following:
- List element has direct children that are not allowed: a
Serious<svg> elements with an img or image role must have alternative text2 elements
SVG images need text alternatives so their information can be accessed through any sensory modality - visual, auditory, or tactile. Text alternatives enable screen readers to convert visual information into speech or braille, support future translation into sign language, and ensure content is accessible regardless of a user's sensory abilities.
Failing Elements
<svg xmlns="http://www.w3.org/2000/svg" width="21" height="20" viewBox="0 0 21 20" fill="none" class="product-best-deal-star product-best-deal-star-left" role="img">
Fix any of the following:
- Element has no child that is a title
- 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
<svg xmlns="http://www.w3.org/2000/svg" width="21" height="20" viewBox="0 0 21 20" fill="none" class="product-best-deal-star product-best-deal-star-right" role="img">
Fix any of the following:
- Element has no child that is a title
- 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
SeriousElements should not have tabindex greater than zero1 element
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.
Failing Elements
<button aria-label="Please be alert to potential phishing attempts. Crunchyroll will never ask for your personal information via email or SMS." tabindex="1" class="button--xqVd0 button--is-type-one--3uIzT" data-t="grant-anonymous-consent-btn" type="button">
Fix any of the following:
- Element has a tabindex greater than 0
SeriousFocused elements must not be entirely hidden by author-created content1 element
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.
Failing Elements
<button aria-label="button-premium" tabindex="0" class="button--xqVd0 button--is-type-one--3uIzT cr-start-..." data-t="button-premium" type="button">
ModerateHeading levels should only increase by one1 element
Headings convey page structure for screen reader users the same way text size does for sighted users. Properly ordered headings (h1 through h6) allow screen reader users to quickly navigate and understand content structure, saving significant time and frustration while also improving search engine optimization.
Failing Elements
<h4 class="text--gq6o- text--is-regular--M4487 text--is-m--pqiL- perk-section-card-title perk-section-card-title-active">Ad-free streaming</h4>
Fix any of the following:
- Heading order invalid
ModerateLandmarks should have a unique role or role/label/title (i.e. accessible name) combination1 element
Each landmark on a page must have either a unique role or a unique accessible name. Duplicate landmarks confuse screen reader users about which section they're navigating to, making it difficult to efficiently move through the page structure.
Failing Elements
<div class="carousel--uuuFa cards-carousel--TkKA1" aria-label="Cards" role="region" aria-roledescription="Carousel" style="--mobile-cols: 2; --mobile-rows: 1; --tablet-cols: 4; --tablet-rows: 1; --desktop-cols: 6; --desktop-rows: 1;">
Fix any of the following:
- The landmark must have a unique aria-label, aria-labelledby, or title to make landmarks distinguishable
ModerateZooming 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.
Failing Elements
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1.0, user-scalable=0">
Fix any of the following:
- user-scalable on <meta> tag disables zooming on mobile devices
ModerateAll page content should be contained by landmarks50 elements
Content should be organized within high-level landmark regions like <header>, <navigation>, <main>, and <footer>. Content outside these sections is difficult to find and its purpose may be unclear, making navigation inefficient for screen reader users who rely on landmarks to understand page structure.
Failing Elements
<picture class="cr-image">
Fix any of the following:
- Some page content is not contained by landmarks
<div class="campaign-hero-glyph">
Fix any of the following:
- Some page content is not contained by landmarks
<h1 class="cr-brand-heading cr-brand-heading--m cr-brand-heading--atyp campaign-hero-title">New Dubs!</h1>
Fix any of the following:
- Some page content is not contained by landmarks
<p class="text--gq6o- text--is-regular--M4487 text--is-l--iccTo campaign-hero-subtitle">Watch now with English dub</p>
Fix any of the following:
- Some page content is not contained by landmarks
<div class="products-heading"><h2 class="cr-brand-heading cr-brand-heading--xl cr-brand-heading--atyp title">Pick Your Premium</h2></div>
Fix any of the following:
- Some page content is not contained by landmarks
<div>
Fix any of the following:
- Some page content is not contained by landmarks
<div class="product-head">
Fix any of the following:
- Some page content is not contained by landmarks
<span class="text--gq6o- text--is-regular--M4487 text--is-m--pqiL- perk-text">No ads*</span>
Fix any of the following:
- Some page content is not contained by landmarks
<span class="text--gq6o- text--is-regular--M4487 text--is-m--pqiL- perk-text">Complete access to Crunchyroll's library</span>
Fix any of the following:
- Some page content is not contained by landmarks
<span class="text--gq6o- text--is-regular--M4487 text--is-m--pqiL- perk-text">New episodes shortly after airing in Japan</span>
Fix any of the following:
- Some page content is not contained by landmarks
Showing first 10 of 50 failing elements.
MinorHeadings should not be empty6 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.
Failing Elements
<h3 class="text--gq6o- text--is-regular--M4487 text--is-m--pqiL- browse-card-static__title--sQTcU"><a aria-label="" tabindex="-1" href="//www.crunchyroll.com/series/GYQWNXPZY" class="browse-card-static__title-link--EeNHn" aria-hidden="true">Fire Force</a></h3>
Fix any of the following:
- Element does not have 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
<h3 class="text--gq6o- text--is-regular--M4487 text--is-m--pqiL- browse-card-static__title--sQTcU"><a aria-label="" tabindex="-1" href="//www.crunchyroll.com/series/G4PH0WJQZ" class="browse-card-static__title-link--EeNHn" aria-hidden="true">Fate/strange Fake</a></h3>
Fix any of the following:
- Element does not have 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
<h3 class="text--gq6o- text--is-regular--M4487 text--is-m--pqiL- browse-card-static__title--sQTcU">
Fix any of the following:
- Element does not have 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
<h3 class="text--gq6o- text--is-regular--M4487 text--is-m--pqiL- browse-card-static__title--sQTcU"><a aria-label="" tabindex="-1" href="//www.crunchyroll.com/series/GRMG8ZQZR" class="browse-card-static__title-link--EeNHn" aria-hidden="true">One Piece</a></h3>
Fix any of the following:
- Element does not have 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
<h3 class="text--gq6o- text--is-regular--M4487 text--is-m--pqiL- browse-card-static__title--sQTcU"><a aria-label="" tabindex="-1" href="//www.crunchyroll.com/series/GEXH3W2W7" class="browse-card-static__title-link--EeNHn" aria-hidden="true">MF GHOST</a></h3>
Fix any of the following:
- Element does not have 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
<h3 class="text--gq6o- text--is-regular--M4487 text--is-m--pqiL- browse-card-static__title--sQTcU"><a aria-label="" tabindex="-1" href="//www.crunchyroll.com/series/GXJHM3PK5" class="browse-card-static__title-link--EeNHn" aria-hidden="true">TRIGUN STAMPEDE</a></h3>
Fix any of the following:
- Element does not have 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
Passed audits49 across 1 page
<html> element must have a lang attribute1 element
Screen readers need language information to switch between pronunciation libraries. Without a specified language, screen readers default to the user's preferred language, resulting in incorrect pronunciation that sounds like a strange accent and makes content difficult or impossible to understand.
Audit Elements
<html lang="en" dir="ltr">
<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" dir="ltr">
<li> elements must be contained in a <ul> or <ol>20 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="cr-product-card-perk cr-product-card-perk--brighter">
<li class="cr-product-card-perk cr-product-card-perk--brighter">
<li class="cr-product-card-perk cr-product-card-perk--brighter">
<li class="cr-product-card-perk cr-product-card-perk--brighter">
<li class="cr-product-card-perk cr-product-card-perk--brighter">
Showing first 5 of 20 audited elements.
<ul> and <ol> must only directly contain <li>, <script> or <template> elements3 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="perks-list" data-t="perks-list">
<ul class="perks-list" data-t="perks-list">
<ul class="perks-list" data-t="perks-list">
All page content should be contained by landmarks545 elements
Content should be organized within high-level landmark regions like <header>, <navigation>, <main>, and <footer>. Content outside these sections is difficult to find and its purpose may be unclear, making navigation inefficient for screen reader users who rely on landmarks to understand page structure.
Audit Elements
<div id="root">
<div class="cr-main-layout">
<div>
<header class="cr-header state-transparent">
<div class="cr-horizontal-wrapper header-content">
Showing first 5 of 545 audited elements.
All touch targets must be 24px large, or leave sufficient space118 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 aria-label="Log in" tabindex="0" data-t="button-login" class="button--xqVd0 button..." href="https://sso.crunchyr..." type="button">
<button aria-label="button-premium" tabindex="0" class="button--xqVd0 button--is-type-one--3uIzT cr-start-premium-button" data-t="button-premium" type="button"><span class="call-to-action--PEidl call-to-action--is-m--RVdkI button__cta--LOqDH">Start free trial</span></button>
<button aria-label="Please be alert to potential phishing attempts. Crunchyroll will never ask for your personal information via email or SMS." tabindex="1" class="button--xqVd0 button--is-type-one--3uIzT" data-t="grant-anonymous-consent-btn" type="button">
<button aria-label="Compare Plans" tabindex="0" class="call-to-action--PEidl call-to-action--is-m--RVdkI campaign-hero-plans-link" data-t="campaign-hero-plans-compare-plans">
<input type="radio" name="premium-plan-toggle" class="toggle-switch__input--LEtPT" id="premium-plan-toggle-first-option" tabindex="-1" value="" checked="">
Showing first 5 of 118 audited elements.
Alternative text of images should not be repeated as text3 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 srcset="https://static.crunc..." src="https://static.crunc..." alt="Crunchyroll promotio..." class="cr-promo-hero-image ...">
<img srcset="https://static.crunc..." src="https://static.crunc..." alt="Black Clover" class="campaign-hero-glyph-...">
<img srcset="https://static.crunc..." src="https://static.crunc..." alt="a screenshot of Crun..." class="manga-upsell-image">
ARIA attributes must be used as specified for the element's role125 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
<a aria-label="Log in" tabindex="0" data-t="button-login" class="button--xqVd0 button..." href="https://sso.crunchyr..." type="button">
<button aria-label="button-premium" tabindex="0" class="button--xqVd0 button--is-type-one--3uIzT cr-start-premium-button" data-t="button-premium" type="button"><span class="call-to-action--PEidl call-to-action--is-m--RVdkI button__cta--LOqDH">Start free trial</span></button>
<button aria-label="Please be alert to potential phishing attempts. Crunchyroll will never ask for your personal information via email or SMS." tabindex="1" class="button--xqVd0 button--is-type-one--3uIzT" data-t="grant-anonymous-consent-btn" type="button">
<button aria-label="Compare Plans" tabindex="0" class="call-to-action--PEidl call-to-action--is-m--RVdkI campaign-hero-plans-link" data-t="campaign-hero-plans-compare-plans">
<label aria-label="" tabindex="0" class="toggle-switch__label--d8jKM" for="premium-plan-toggle-first-option">
Showing first 5 of 125 audited elements.
ARIA attributes must conform to valid names125 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
<a aria-label="Log in" tabindex="0" data-t="button-login" class="button--xqVd0 button..." href="https://sso.crunchyr..." type="button">
<button aria-label="button-premium" tabindex="0" class="button--xqVd0 button--is-type-one--3uIzT cr-start-premium-button" data-t="button-premium" type="button"><span class="call-to-action--PEidl call-to-action--is-m--RVdkI button__cta--LOqDH">Start free trial</span></button>
<button aria-label="Please be alert to potential phishing attempts. Crunchyroll will never ask for your personal information via email or SMS." tabindex="1" class="button--xqVd0 button--is-type-one--3uIzT" data-t="grant-anonymous-consent-btn" type="button">
<button aria-label="Compare Plans" tabindex="0" class="call-to-action--PEidl call-to-action--is-m--RVdkI campaign-hero-plans-link" data-t="campaign-hero-plans-compare-plans">
<label aria-label="" tabindex="0" class="toggle-switch__label--d8jKM" for="premium-plan-toggle-first-option">
Showing first 5 of 125 audited elements.
ARIA attributes must conform to valid values124 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
<a aria-label="Log in" tabindex="0" data-t="button-login" class="button--xqVd0 button..." href="https://sso.crunchyr..." type="button">
<button aria-label="button-premium" tabindex="0" class="button--xqVd0 button--is-type-one--3uIzT cr-start-premium-button" data-t="button-premium" type="button"><span class="call-to-action--PEidl call-to-action--is-m--RVdkI button__cta--LOqDH">Start free trial</span></button>
<button aria-label="Please be alert to potential phishing attempts. Crunchyroll will never ask for your personal information via email or SMS." tabindex="1" class="button--xqVd0 button--is-type-one--3uIzT" data-t="grant-anonymous-consent-btn" type="button">
<button aria-label="Compare Plans" tabindex="0" class="call-to-action--PEidl call-to-action--is-m--RVdkI campaign-hero-plans-link" data-t="campaign-hero-plans-compare-plans">
<label aria-label="" tabindex="0" class="toggle-switch__label--d8jKM" for="premium-plan-toggle-first-option">
Showing first 5 of 124 audited elements.
ARIA commands must have an accessible name1 element
Screen reader users cannot determine the purpose of interactive elements with role="link", role="button", or role="menuitem" that lack an accessible name. Without a name, these controls are essentially invisible to assistive technology users.
Audit Elements
<div role="button" aria-label="Language" tabindex="0" class="dropdown-trigger--P--FX dropdown-trigger--is-styled--Q3nCd select-trigger--is-type-filled--4DySC trigger" aria-haspopup="listbox" aria-expanded="false" data-t="language-select-trigger" ...>
ARIA hidden element must not be focusable or contain focusable elements114 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="header-logo-symbol mobile-hidden" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 303 52" data-t="crunchyroll-horizontal-svg" aria-hidden="true" role="img">
<svg class="header-logo-mobile" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 48 48" data-t="crunchyroll-logo-only-svg" aria-hidden="true" role="img">
<svg class="campaign-hero-plans-link-icon" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" data-t="arrow-down-svg" aria-hidden="true" role="img">
<svg class="perk-icon" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" data-t="checkmark-svg" aria-hidden="true" role="img"><path d="M7 12a1 1 0 0 1-.707-.293l-3-3a.999.999 0 1 1 1.414-1.414l2.226 2.226 4.3-5.16a1 1 0 1 1 1.535 1.28l-5 6.001A1 1 0 0 1 7 12"></path></svg>
<svg class="perk-icon" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" data-t="checkmark-svg" aria-hidden="true" role="img"><path d="M7 12a1 1 0 0 1-.707-.293l-3-3a.999.999 0 1 1 1.414-1.414l2.226 2.226 4.3-5.16a1 1 0 1 1 1.535 1.28l-5 6.001A1 1 0 0 1 7 12"></path></svg>
Showing first 5 of 114 audited elements.
ARIA role should be appropriate for the element92 elements
Invalid ARIA role and HTML element combinations can break accessibility for entire sections of your application. When roles are used incorrectly, assistive technologies may report confusing or nonsensical information to users, making it impossible for them to understand and interact with the interface properly.
Audit Elements
<svg class="header-logo-symbol mobile-hidden" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 303 52" data-t="crunchyroll-horizontal-svg" aria-hidden="true" role="img">
<svg class="header-logo-mobile" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 48 48" data-t="crunchyroll-logo-only-svg" aria-hidden="true" role="img">
<div tabindex="-1" role="dialog" class="content-wrapper--MF5LS">
<svg class="campaign-hero-plans-link-icon" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" data-t="arrow-down-svg" aria-hidden="true" role="img">
<svg class="perk-icon" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" data-t="checkmark-svg" aria-hidden="true" role="img"><path d="M7 12a1 1 0 0 1-.707-.293l-3-3a.999.999 0 1 1 1.414-1.414l2.226 2.226 4.3-5.16a1 1 0 1 1 1.535 1.28l-5 6.001A1 1 0 0 1 7 12"></path></svg>
Showing first 5 of 92 audited elements.
ARIA roles used must conform to valid values20 elements
Invalid ARIA role values prevent assistive technologies from understanding and communicating the element's purpose to users. Without valid roles, screen readers cannot provide information about the element's features, properties, or how users should interact with it.
Audit Elements
<div tabindex="-1" role="dialog" class="content-wrapper--MF5LS">
<svg xmlns="http://www.w3.org/2000/svg" width="21" height="20" viewBox="0 0 21 20" fill="none" class="product-best-deal-star product-best-deal-star-left" role="img">
<svg xmlns="http://www.w3.org/2000/svg" width="21" height="20" viewBox="0 0 21 20" fill="none" class="product-best-deal-star product-best-deal-star-right" role="img">
<div class="cr-category-pills" role="group" aria-label="Filter by genre" data-t="category-pills">
<div class="carousel--uuuFa cards-carousel--TkKA1" aria-label="Cards" role="region" aria-roledescription="Carousel" style="--mobile-cols: 2; --mobile-rows: 1; --tablet-cols: 4; --tablet-rows: 1; --desktop-cols: 6; --desktop-rows: 1;">
Showing first 5 of 20 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>
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
<header class="cr-header state-transparent">
Buttons must have discernible text16 elements
Screen reader users cannot determine the purpose of buttons without an accessible name. Without a name, users don't know what action the button will perform when activated.
Audit Elements
<button aria-label="button-premium" tabindex="0" class="button--xqVd0 button--is-type-one--3uIzT cr-start-premium-button" data-t="button-premium" type="button"><span class="call-to-action--PEidl call-to-action--is-m--RVdkI button__cta--LOqDH">Start free trial</span></button>
<button aria-label="Please be alert to potential phishing attempts. Crunchyroll will never ask for your personal information via email or SMS." tabindex="1" class="button--xqVd0 button--is-type-one--3uIzT" data-t="grant-anonymous-consent-btn" type="button">
<button aria-label="Compare Plans" tabindex="0" class="call-to-action--PEidl call-to-action--is-m--RVdkI campaign-hero-plans-link" data-t="campaign-hero-plans-compare-plans">
<button type="button" class="cr-category-pill cr-category-pill--selected" aria-pressed="true" data-t="category-pill-action">Action</button>
<button type="button" class="cr-category-pill" aria-pressed="false" data-t="category-pill-adventure">Adventure</button>
Showing first 5 of 16 audited elements.
Content must reflow without two-dimensional scrolling1 element
People who zoom to 400% or use a narrow viewport must be able to scroll in one direction only. A layout that still requires horizontal scrolling at 320 CSS pixels forces magnified readers to pan left and right line by line, which makes the page close to unusable.
Audit Elements
<div class="manga-upsell-wrapper">
Contentinfo landmark should not be contained in another landmark1 element
The contentinfo landmark must be at the top level to help screen reader users quickly navigate to footer information. When nested inside another landmark, it becomes harder to find, defeating its purpose of providing quick access to content information.
Audit Elements
<footer class="cr-footer-seo">
Deprecated ARIA roles must not be used20 elements
Deprecated ARIA roles are not recognized by modern screen readers and assistive technologies. Using outdated roles means some users cannot access essential information or functionality on your site.
Audit Elements
<div tabindex="-1" role="dialog" class="content-wrapper--MF5LS">
<svg xmlns="http://www.w3.org/2000/svg" width="21" height="20" viewBox="0 0 21 20" fill="none" class="product-best-deal-star product-best-deal-star-left" role="img">
<svg xmlns="http://www.w3.org/2000/svg" width="21" height="20" viewBox="0 0 21 20" fill="none" class="product-best-deal-star product-best-deal-star-right" role="img">
<div class="cr-category-pills" role="group" aria-label="Filter by genre" data-t="category-pills">
<div class="carousel--uuuFa cards-carousel--TkKA1" aria-label="Cards" role="region" aria-roledescription="Carousel" style="--mobile-cols: 2; --mobile-rows: 1; --tablet-cols: 4; --tablet-rows: 1; --desktop-cols: 6; --desktop-rows: 1;">
Showing first 5 of 20 audited elements.
Document should have one main landmark1 element
Every page should have exactly one main landmark that identifies the primary content. Without a main landmark, screen reader users must navigate through all content linearly to find what they're looking for, making page navigation difficult and time-consuming.
Audit Elements
<html lang="en" dir="ltr">
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="cr-header state-transparent">
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="cr-footer-seo">
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" dir="ltr">
Elements must have their visible text as part of their accessible name12 elements
Interactive widgets that support name from content must have aria-label or aria-labelledby values that match their visible text. Mismatches confuse voice control users who speak the visible label but activate a different function based on the hidden accessible name.
Audit Elements
<a aria-label="Log in" tabindex="0" data-t="button-login" class="button--xqVd0 button..." href="https://sso.crunchyr..." type="button">
<button aria-label="Compare Plans" tabindex="0" class="call-to-action--PEidl call-to-action--is-m--RVdkI campaign-hero-plans-link" data-t="campaign-hero-plans-compare-plans">
<a aria-label="Start 7-Day free tri..." tabindex="0" data-t="product-button" class="button--xqVd0 button..." href="https://sso.crunchyr..." type="button">
<a aria-label="Skip free trial" tabindex="0" data-t="skip-free-trial-cta" class="button--xqVd0 button..." href="https://sso.crunchyr..." type="button">
<a aria-label="Start 7-Day free tri..." tabindex="0" data-t="product-button" class="button--xqVd0 button..." href="https://sso.crunchyr..." type="button">
Showing first 5 of 12 audited elements.
Elements must meet minimum color contrast ratio thresholds169 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
<span class="call-to-action--PEidl call-to-action--is-m--RVdkI button__cta--LOqDH">Log in</span>
<span class="call-to-action--PEidl call-to-action--is-m--RVdkI button__cta--LOqDH">Start free trial</span>
<span class="call-to-action--PEidl call-to-action--is-m--RVdkI button__cta--LOqDH">Continue</span>
<h2 class="cr-brand-heading cr-brand-heading--xl cr-brand-heading--atyp title">Pick Your Premium</h2>
<div>Monthly</div>
Showing first 5 of 169 audited elements.
Elements must only use permitted ARIA attributes125 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
<a aria-label="Log in" tabindex="0" data-t="button-login" class="button--xqVd0 button..." href="https://sso.crunchyr..." type="button">
<button aria-label="button-premium" tabindex="0" class="button--xqVd0 button--is-type-one--3uIzT cr-start-premium-button" data-t="button-premium" type="button"><span class="call-to-action--PEidl call-to-action--is-m--RVdkI button__cta--LOqDH">Start free trial</span></button>
<button aria-label="Please be alert to potential phishing attempts. Crunchyroll will never ask for your personal information via email or SMS." tabindex="1" class="button--xqVd0 button--is-type-one--3uIzT" data-t="grant-anonymous-consent-btn" type="button">
<button aria-label="Compare Plans" tabindex="0" class="call-to-action--PEidl call-to-action--is-m--RVdkI campaign-hero-plans-link" data-t="campaign-hero-plans-compare-plans">
<label aria-label="" tabindex="0" class="toggle-switch__label--d8jKM" for="premium-plan-toggle-first-option">
Showing first 5 of 125 audited elements.
Elements must only use supported ARIA attributes125 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
<a aria-label="Log in" tabindex="0" data-t="button-login" class="button--xqVd0 button..." href="https://sso.crunchyr..." type="button">
<button aria-label="button-premium" tabindex="0" class="button--xqVd0 button--is-type-one--3uIzT cr-start-premium-button" data-t="button-premium" type="button"><span class="call-to-action--PEidl call-to-action--is-m--RVdkI button__cta--LOqDH">Start free trial</span></button>
<button aria-label="Please be alert to potential phishing attempts. Crunchyroll will never ask for your personal information via email or SMS." tabindex="1" class="button--xqVd0 button--is-type-one--3uIzT" data-t="grant-anonymous-consent-btn" type="button">
<button aria-label="Compare Plans" tabindex="0" class="call-to-action--PEidl call-to-action--is-m--RVdkI campaign-hero-plans-link" data-t="campaign-hero-plans-compare-plans">
<label aria-label="" tabindex="0" class="toggle-switch__label--d8jKM" for="premium-plan-toggle-first-option">
Showing first 5 of 125 audited elements.
Elements should not have tabindex greater than zero107 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
<a aria-label="Log in" tabindex="0" data-t="button-login" class="button--xqVd0 button..." href="https://sso.crunchyr..." type="button">
<button aria-label="button-premium" tabindex="0" class="button--xqVd0 button--is-type-one--3uIzT cr-start-premium-button" data-t="button-premium" type="button"><span class="call-to-action--PEidl call-to-action--is-m--RVdkI button__cta--LOqDH">Start free trial</span></button>
<div tabindex="-1" role="dialog" class="content-wrapper--MF5LS">
<button aria-label="Compare Plans" tabindex="0" class="call-to-action--PEidl call-to-action--is-m--RVdkI campaign-hero-plans-link" data-t="campaign-hero-plans-compare-plans">
<label aria-label="" tabindex="0" class="toggle-switch__label--d8jKM" for="premium-plan-toggle-first-option">
Showing first 5 of 107 audited elements.
Focused elements must not be entirely hidden by author-created content48 elements
Keyboard users have no pointer to show where they are. The focus indicator is their only cue, and a sticky header, footer, cookie banner, or other author-created overlay that completely hides the focused control strands them with no idea what will activate next.
Audit Elements
<button aria-label="Please be alert to potential phishing attempts. Cr..." tabindex="1" class="button--xqVd0 button--is-type-one--3uIzT" data-t="grant-anonymous-consent-btn" type="button">
<button aria-label="Compare Plans" tabindex="0" class="call-to-action--PEidl call-to-action--is-m--RVdkI ..." data-t="campaign-hero-plans-compare-plans">
<label aria-label="" tabindex="0" class="toggle-switch__label--d8jKM" for="premium-plan-toggle-first-option">
<label aria-label="" tabindex="0" class="toggle-switch__label--d8jKM" for="premium-plan-toggle-second-option">
<a aria-label="Start 7-Day free trial" tabindex="0" data-t="product-button" class="button--xqVd0 button--is-type-five--qz0dA button--..." href="https://sso.crunchyroll.com/authorize?client_id=km..." type="button">
Showing first 5 of 48 audited elements.
Form elements must have labels2 elements
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 type="radio" name="premium-plan-toggle" class="toggle-switch__input--LEtPT" id="premium-plan-toggle-first-option" tabindex="-1" value="" checked="">
<input type="radio" name="premium-plan-toggle" class="toggle-switch__input--LEtPT" id="premium-plan-toggle-second-option" tabindex="-1" value="">
Form elements should have a visible label2 elements
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 type="radio" name="premium-plan-toggle" class="toggle-switch__input--LEtPT" id="premium-plan-toggle-first-option" tabindex="-1" value="" checked="">
<input type="radio" name="premium-plan-toggle" class="toggle-switch__input--LEtPT" id="premium-plan-toggle-second-option" tabindex="-1" value="">
Form field must not have multiple label elements2 elements
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 type="radio" name="premium-plan-toggle" class="toggle-switch__input--LEtPT" id="premium-plan-toggle-first-option" tabindex="-1" value="" checked="">
<input type="radio" name="premium-plan-toggle" class="toggle-switch__input--LEtPT" id="premium-plan-toggle-second-option" tabindex="-1" value="">
Heading levels should only increase by one40 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="cr-brand-heading cr-brand-heading--m cr-brand-heading--atyp campaign-hero-title">New Dubs!</h1>
<h2 class="cr-brand-heading cr-brand-heading--xl cr-brand-heading--atyp title">Pick Your Premium</h2>
<h3 class="heading--nKNOf heading--is-l--zGnGW heading--is-family-type-one--GqBzU product-title product-title--start">Fan</h3>
<h4 class="heading--nKNOf heading--is-s--x1e6g heading--is-family-type-one--GqBzU product-pricing"><span class="product-pricing--strikethrough" style="display: none;"></span>NZ$9.99/mo<span class="product-pricing--note" style="display: none;"></span></h4>
<h3 class="heading--nKNOf heading--is-l--zGnGW heading--is-family-type-one--GqBzU product-title product-title--start">Mega Fan</h3>
Showing first 5 of 40 audited elements.
Headings should not be empty35 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="cr-brand-heading cr-brand-heading--m cr-brand-heading--atyp campaign-hero-title">New Dubs!</h1>
<h2 class="cr-brand-heading cr-brand-heading--xl cr-brand-heading--atyp title">Pick Your Premium</h2>
<h3 class="heading--nKNOf heading--is-l--zGnGW heading--is-family-type-one--GqBzU product-title product-title--start">Fan</h3>
<h4 class="heading--nKNOf heading--is-s--x1e6g heading--is-family-type-one--GqBzU product-pricing"><span class="product-pricing--strikethrough" style="display: none;"></span>NZ$9.99/mo<span class="product-pricing--note" style="display: none;"></span></h4>
<h3 class="heading--nKNOf heading--is-l--zGnGW heading--is-family-type-one--GqBzU product-title product-title--start">Mega Fan</h3>
Showing first 5 of 35 audited elements.
IDs used in ARIA and labels must be unique2 elements
Duplicate IDs break the accessibility of ARIA elements, form labels, and table headers. When IDs are duplicated, assistive technologies and scripts only reference the first instance, causing subsequent elements with the same ID to be ignored or incorrectly associated.
Audit Elements
<input type="radio" name="premium-plan-toggle" class="toggle-switch__input--LEtPT" id="premium-plan-toggle-first-option" tabindex="-1" value="" checked="">
<input type="radio" name="premium-plan-toggle" class="toggle-switch__input--LEtPT" id="premium-plan-toggle-second-option" tabindex="-1" value="">
Images must have alternative text3 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 srcset="https://static.crunc..." src="https://static.crunc..." alt="Crunchyroll promotio..." class="cr-promo-hero-image ...">
<img srcset="https://static.crunc..." src="https://static.crunc..." alt="Black Clover" class="campaign-hero-glyph-...">
<img srcset="https://static.crunc..." src="https://static.crunc..." alt="a screenshot of Crun..." class="manga-upsell-image">
Inline text spacing must be adjustable with custom stylesheets2 elements
Single-spaced text makes it difficult for people with cognitive disabilities to track lines while reading. Providing line spacing between 1.5 to 2 helps these users start a new line more easily after finishing the previous one.
Audit Elements
<div class="carousel--uuuFa cards-carousel--TkKA1" aria-label="Cards" role="region" aria-roledescription="Carousel" style="--mobile-cols: 2; --mobile-rows: 1; --tablet-cols: 4; --tablet-rows: 1; --desktop-cols: 6; --desktop-rows: 1;">
<div class="carousel--uuuFa cards-carousel--TkKA1" aria-label="Cards" role="region" aria-roledescription="Carousel" style="--mobile-cols: 2; --tablet-cols: 4; --desktop-cols: 6;">
Interactive controls must not be nested32 elements
Nested interactive elements create empty tab stops where screen readers remain silent. When users tab to a focusable element inside another interactive control, they receive no information about its name, role, or state, creating a confusing and broken navigation experience.
Audit Elements
<button aria-label="button-premium" tabindex="0" class="button--xqVd0 button--is-type-one--3uIzT cr-start-premium-button" data-t="button-premium" type="button"><span class="call-to-action--PEidl call-to-action--is-m--RVdkI button__cta--LOqDH">Start free trial</span></button>
<button aria-label="Please be alert to potential phishing attempts. Crunchyroll will never ask for your personal information via email or SMS." tabindex="1" class="button--xqVd0 button--is-type-one--3uIzT" data-t="grant-anonymous-consent-btn" type="button">
<img srcset="https://static.crunc..." src="https://static.crunc..." alt="Crunchyroll promotio..." class="cr-promo-hero-image ...">
<img srcset="https://static.crunc..." src="https://static.crunc..." alt="Black Clover" class="campaign-hero-glyph-...">
<button aria-label="Compare Plans" tabindex="0" class="call-to-action--PEidl call-to-action--is-m--RVdkI campaign-hero-plans-link" data-t="campaign-hero-plans-compare-plans">
Showing first 5 of 32 audited elements.
Interactive elements must have a visible focus indicator50 elements
Sighted keyboard users rely on a visible focus indicator to know where they are on the page. When focus styles are missing, too subtle, or have insufficient contrast against the surrounding colors, users cannot tell which element will respond when they press Enter or Space, making keyboard navigation slow and error-prone. This especially affects people with motor impairments who cannot use a mouse and people with low vision who need clear, high-contrast indicators.
Audit Elements
<button aria-label="Please be alert to potential phishing attempts. Cr..." tabindex="1" class="button--xqVd0 button--is-type-one--3uIzT" data-t="grant-anonymous-consent-btn" type="button">
<a aria-label="Log in" tabindex="0" data-t="button-login" class="button--xqVd0 button--is-type-two-weak--VH7er butt..." href="https://sso.crunchyroll.com/authorize?client_id=km..." type="button">
<button aria-label="button-premium" tabindex="0" class="button--xqVd0 button--is-type-one--3uIzT cr-start-..." data-t="button-premium" type="button">
<button aria-label="Compare Plans" tabindex="0" class="call-to-action--PEidl call-to-action--is-m--RVdkI ..." data-t="campaign-hero-plans-compare-plans">
<label aria-label="" tabindex="0" class="toggle-switch__label--d8jKM" for="premium-plan-toggle-first-option">
Showing first 5 of 50 audited elements.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination2 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
<header class="cr-header state-transparent">
<footer class="cr-footer-seo">
Links must be distinguishable without relying on color1 element
People with low vision or color blindness cannot visually distinguish links from surrounding text without sufficient color contrast (3:1 ratio minimum). When link colors are too similar to regular text, users with visual impairments cannot identify which text is clickable.
Audit Elements
<a aria-label="Help Center" tabindex="0" data-t="help-center-link" class="link link--start" target="_blank" href="https://help.crunchyroll.com/hc/en-us">Help Center</a>
Links must have discernible text92 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 aria-label="Log in" tabindex="0" data-t="button-login" class="button--xqVd0 button..." href="https://sso.crunchyr..." type="button">
<a aria-label="Start 7-Day free tri..." tabindex="0" data-t="product-button" class="button--xqVd0 button..." href="https://sso.crunchyr..." type="button">
<a aria-label="Skip free trial" tabindex="0" data-t="skip-free-trial-cta" class="button--xqVd0 button..." href="https://sso.crunchyr..." type="button">
<a aria-label="Start 7-Day free tri..." tabindex="0" data-t="product-button" class="button--xqVd0 button..." href="https://sso.crunchyr..." type="button">
<a aria-label="Skip free trial" tabindex="0" data-t="skip-free-trial-cta" class="button--xqVd0 button..." href="https://sso.crunchyr..." type="button">
Showing first 5 of 92 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" dir="ltr">
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 lang="en" dir="ltr">
Required ARIA attributes must be provided20 elements
ARIA widget roles need required attributes to describe their current state. Without these attributes, screen readers cannot communicate essential information like whether a checkbox is checked or a slider's current value, leaving users unable to interact effectively with the widget.
Audit Elements
<div tabindex="-1" role="dialog" class="content-wrapper--MF5LS">
<svg xmlns="http://www.w3.org/2000/svg" width="21" height="20" viewBox="0 0 21 20" fill="none" class="product-best-deal-star product-best-deal-star-left" role="img">
<svg xmlns="http://www.w3.org/2000/svg" width="21" height="20" viewBox="0 0 21 20" fill="none" class="product-best-deal-star product-best-deal-star-right" role="img">
<div class="cr-category-pills" role="group" aria-label="Filter by genre" data-t="category-pills">
<div class="carousel--uuuFa cards-carousel--TkKA1" aria-label="Cards" role="region" aria-roledescription="Carousel" style="--mobile-cols: 2; --mobile-rows: 1; --tablet-cols: 4; --tablet-rows: 1; --desktop-cols: 6; --desktop-rows: 1;">
Showing first 5 of 20 audited elements.
Scrollable region must have keyboard access1 element
Scrollable regions must contain focusable elements or be focusable themselves to enable keyboard navigation. Without keyboard access, users cannot scroll to view content that extends beyond the visible area, making that content completely inaccessible to keyboard-only users.
Audit Elements
<div class="carousel-scroller__track--43f0L" data-t="cards">
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 class="faq__summary--xEB3p">
<summary class="faq__summary--xEB3p">
<summary class="faq__summary--xEB3p">
<summary class="faq__summary--xEB3p">
<summary class="faq__summary--xEB3p">
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, maximum-scale=1.0, user-scalable=0">
How does your site stack up against Crunchyroll?
Run the same automated WCAG 2.2 checks we run on the scoreboard.
More in Streaming & Entertainment