Skip to content
https://www.apple.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
78
GRADE
C
FIX
6
REVIEW
4
PASS
14
INFO
0
Checks
24
14 PASS 4 REVIEW 6 FIX
D
Tabindex Anti-Patterns
Action
0 positive, 35 -1-on-focusable
FIX
0 positive, 35 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <button>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a id="endless-entertainment-gallery-item-2-trigger">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a id="endless-entertainment-gallery-item-3-trigger">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a id="endless-entertainment-gallery-item-4-trigger">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a id="endless-entertainment-gallery-item-5-trigger">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a id="endless-entertainment-gallery-item-6-trigger">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a id="endless-entertainment-gallery-item-7-trigger">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a id="endless-entertainment-gallery-item-8-trigger">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a id="endless-entertainment-gallery-item-9-trigger">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a id="media-gallery-item-2-link">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a id="media-gallery-item-3-link">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a id="media-gallery-item-4-link">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a id="media-gallery-item-5-link">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a id="media-gallery-item-6-link">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a id="media-gallery-item-7-link">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a id="media-gallery-item-8-link">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a id="media-gallery-item-9-link">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a id="media-gallery-item-2">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a id="media-gallery-item-3">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a id="media-gallery-item-4">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a id="media-gallery-item-5">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a id="media-gallery-item-6">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a id="media-gallery-item-7">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a id="media-gallery-item-8">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a id="media-gallery-item-9">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Info::
favicon.ico present at site root
Info::
No apple-touch-icon detected
iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.
✓ favicon.ico Present
✗ PNG Icons Missing
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
D
Web Manifest
Action
Not found
FIX
Not found
Info::
No web manifest found
No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark ModeNo Dark Mode Detected
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
No print-specific styles detected
When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.
Print Stylesheet No Print Styles
Print stylesheet Not found ✗Inline @media print Not detected ✗
D
Navigation UX
Action
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Info::
2 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search role='search' landmark
Skip Link
Labeled Navigation 2 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
B
Landmark Structure
8 landmarks
REVIEW
8 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
No banner (header) landmark
Warning::
Skip navigation link is missing (WCAG 2.4.1)
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER (missing!) NAV "Global" SEARCH MAIN ASIDE "Choose country or region" CONTENTINFO footer

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more ▾

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page Not Found - Apple ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

0 pass 20 fail WCAG AA
h1 Apple
1.01:1
#000000
on
#010101
needs 3.0:1 (large text)
32px · above the fold
h2 Shop
1.01:1
#000000
on
#010101
needs 3.0:1 (large text)
24px · above the fold
h2 Quick Links
1.03:1
#000000
on
#040507
needs 3.0:1 (large text)
24px · mid-page
h2 Shop Special Stores
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Explore Mac
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Shop Mac
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 More from Mac
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Explore iPad
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Shop iPad
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 More from iPad
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Explore iPhone
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Shop iPhone
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 More from iPhone
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Explore Watch
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Shop Watch
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 More from Watch
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Explore Vision
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Shop Vision
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 More from Vision
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Explore AirPods
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Apple1.01:13.0:1
#000000
#010101
Fail
h2 Shop1.01:13.0:1
#000000
#010101
Fail
h2 Quick Links1.03:13.0:1
#000000
#040507
Fail
h2 Shop Special Stores1.00:13.0:1
#000000
#000000
Fail
h2 Explore Mac1.00:13.0:1
#000000
#000000
Fail
h2 Shop Mac1.00:13.0:1
#000000
#000000
Fail
h2 More from Mac1.00:13.0:1
#000000
#000000
Fail
h2 Explore iPad1.00:13.0:1
#000000
#000000
Fail
h2 Shop iPad1.00:13.0:1
#000000
#000000
Fail
h2 More from iPad1.00:13.0:1
#000000
#000000
Fail
h2 Explore iPhone1.00:13.0:1
#000000
#000000
Fail
h2 Shop iPhone1.00:13.0:1
#000000
#000000
Fail
h2 More from iPhone1.00:13.0:1
#000000
#000000
Fail
h2 Explore Watch1.00:13.0:1
#000000
#000000
Fail
h2 Shop Watch1.00:13.0:1
#000000
#000000
Fail
h2 More from Watch1.00:13.0:1
#000000
#000000
Fail
h2 Explore Vision1.00:13.0:1
#000000
#000000
Fail
h2 Shop Vision1.00:13.0:1
#000000
#000000
Fail
h2 More from Vision1.00:13.0:1
#000000
#000000
Fail
h2 Explore AirPods1.00:13.0:1
#000000
#000000
Fail

Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.

A+
Heading Hierarchy
56 headings
PASS
56 headings
Info::
Single H1 present
  • H1 Apple
  • H2 Shop
  • H2 Quick Links
  • H2 Shop Special Stores
  • H2 Explore Mac
  • H2 Shop Mac
  • H2 More from Mac
  • H2 Explore iPad
  • H2 Shop iPad
  • H2 More from iPad
  • H2 Explore iPhone
  • H2 Shop iPhone
  • H2 More from iPhone
  • H2 Explore Watch
  • H2 Shop Watch
  • H2 More from Watch
  • H2 Explore Vision
  • H2 Shop Vision
  • H2 More from Vision
  • H2 Explore AirPods
  • H2 Shop AirPods
  • H2 More from AirPods
  • H2 Explore Home
  • H2 Shop Home
  • H2 More from Home
  • H2 Explore Entertainment
  • H2 Support
  • H2 Shop by Product
  • H2 Shop by Category
  • H2 More to Explore
  • H2 Explore Support
  • H2 Get Help
  • H2 Helpful Topics
  • H2 Quick Links
  • H2 MacBook Pro
  • H2 MacBook Pro
  • H2 iPhone Duo
  • H3 iMac
  • H3 iPhone 18 Pro
  • H3 HomePod mini 2
  • H3 <picture class="headline" aria-hidden="true"> <source srcset="/v/homepage/images/logos/apple-watch-series-12/a/promo_logo_apple_watch_series_12__eck6698frlqq_small.png, /v/homepage/images/l
  • H3 <picture class="headline" aria-hidden="true"> <source srcset="/v/homepage/images/logos/apple-upgrade/a/promo_logo_apple_upgrade__lwuohffdzjem_small.png, /v/homepage/images/logos/apple-upgrad
  • H3 <picture class="headline" aria-hidden="true"> <source srcset="/v/homepage/images/logos/apple-card/a/promo_logo_apple_card__28vxrcexz0ia_small.png, /v/homepage/images/logos/apple-card/a/promo
  • H2 Endless entertainment.
  • H2 Apple Footer
  • H3 Shop and Learn Shop and Learn
  • H3 Apple Wallet Apple Wallet
  • H3 Account Account
  • H3 Entertainment Entertainment
  • H3 Apple Store Apple Store
  • H3 For Business For Business
  • H3 For Education For Education
  • H3 For Healthcare For Healthcare
  • H3 For Government For Government
  • H3 Apple Values Apple Values
  • H3 About Apple About Apple
A
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Warning::
3 heading(s) are over 120 characters -- likely a misformatted paragraph
Headings beyond 120 characters are almost always full sentences or paragraphs that received heading semantics by mistake (e.g., a CMS editor selected the wrong block type, or a template wrapped a body paragraph in `<h2>`). Screen readers will announce these as "heading" and read the entire paragraph at heading prosody. Affected: - H3: 200 chars - H3: 200 chars - H3: 200 chars
Got: 3 >120-char heading(s)
A
Alt Text Quality
All 50 images OK
PASS
All 50 images OK
Info::
3 image(s) with alt text over 125 characters
Info::
41 decorative image(s) correctly marked
Info::
6 image(s) with good alt text
50 images 6 good alt text 41 decorative
IssueCount
too long3 image(s)
A+
Form Accessibility
All 1 controls labeled
PASS
All 1 controls labeled
Info::
1 control(s) properly labeled
1 controls
1 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
inputinputSearch apple.comaria-label
A+
Form Input Types
1 input(s) using type=text where a specific type would help
PASS
1 input(s) using type=text where a specific type would help
Info::
Input "Search apple.com" should use type="search" (currently type="text")
Field name "Search apple.com" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
A+
Form Input Quality
1 form control(s) checked, no input-semantic issues
PASS
1 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
A+
Document Language
Lang attribute set to "en-US"
PASS
Lang attribute set to "en-US"
Info::
<html lang="en-US"> is set and valid
Got: en-US
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
No iframes on this page
A+
Tap Target Adequacy
All tap targets meet WCAG 2.5.5/2.5.8 sizing
PASS
All tap targets meet WCAG 2.5.5/2.5.8 sizing
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
Mobile-Readable Font Sizes
All 74 visible text node(s) render at >= 12 CSS pixels
PASS
All 74 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
2 mobile-depth signal(s) detected
PASS
2 mobile-depth signal(s) detected
Info::
No `<meta name="theme-color">` -- browser chrome falls back to default
Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.
Info::
Viewport `viewport-fit=cover` -- supports notched / dynamic-island devices
The viewport meta declares `viewport-fit=cover`, which lets the page draw into the safe-area edges (notch, dynamic island, home indicator) on iPhone X+ devices. Pair with `env(safe-area-inset-*)` CSS to keep critical UI inside the inset rectangle while letting backgrounds extend edge-to-edge.
A
Lighthouse Accessibility Audits
Score 92/100 — 2 failing, 31 passed
PASS
92

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

ARIA

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Stream now Comedy New season. Stream now Crime The only way to save a villai… section.section-endless-entertainment-gallery > div.endless-entertainment > div#tv-media-gallery > ul.media-gallery-item-container
Play now Hello Kitty Island Adventure Listen now Miley: The Zane Lowe Interv… section.section-endless-entertainment-gallery > div.endless-entertainment > div#fam-media-gallery > ul.media-gallery-item-container

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Stream now a#media-gallery-item-2-link > div.media-gallery-contents > div.media-gallery-bottom-content > div.button
F1 on Apple TV a#media-gallery-item-3-link > div.media-gallery-contents > div.media-gallery-bottom-content > div.button
Stream now a#media-gallery-item-4-link > div.media-gallery-contents > div.media-gallery-bottom-content > div.button
MLS on Apple TV a#media-gallery-item-5-link > div.media-gallery-contents > div.media-gallery-bottom-content > div.button
Stream now a#media-gallery-item-6-link > div.media-gallery-contents > div.media-gallery-bottom-content > div.button
Stream now a#media-gallery-item-7-link > div.media-gallery-contents > div.media-gallery-bottom-content > div.button
Stream now a#media-gallery-item-8-link > div.media-gallery-contents > div.media-gallery-bottom-content > div.button
Listen now a#media-gallery-item-2 > div.media-gallery-contents > div.media-gallery-bottom-content > div.button
Watch now a#media-gallery-item-3 > div.media-gallery-contents > div.media-gallery-bottom-content > div.button
Play now a#media-gallery-item-4 > div.media-gallery-contents > div.media-gallery-bottom-content > div.button
Listen now a#media-gallery-item-5 > div.media-gallery-contents > div.media-gallery-bottom-content > div.button
Watch now a#media-gallery-item-6 > div.media-gallery-contents > div.media-gallery-bottom-content > div.button
Watch now a#media-gallery-item-9 > div.media-gallery-contents > div.media-gallery-bottom-content > div.button

These are opportunities to improve the legibility of your content.

○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]`s are contained by their required parent element
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●`button`, `link`, and `menuitem` elements have accessible names
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●Links have a discernible name
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
●`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●Uses ARIA roles only on compatible elements
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Form elements have associated labels
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Image elements do not have `[alt]` attributes that are redundant text.
○Identical links have the same purpose.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback