Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

6 PASS 1 REVIEW 6 FIX

404 Error Page

Action

HTTP 404, bare page

FIX

HTTP 404, bare page

Correct 404 status code returned

Got: HTTP 404

Bare server default 404 page

The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.

404 Page Quality Default 404 Page

Status Code HTTP 404 ✓Page Title 404 Not Found ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

favicon.ico present at site root

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

Web Manifest

Action

Not found

FIX

Not found

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.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Navigation UX

Action

1 navigation pattern(s)

FIX

1 navigation pattern(s)

Breadcrumb navigation detected

Got: aria-label

3 navigation landmark(s) detected

Hamburger menu detected (responsive design)

Breadcrumbs aria-label navigation

Skip Link

Labeled Navigation 3 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.

Landmark Structure

8 landmarks

REVIEW

8 landmarks

<main> landmark present

3 <nav> landmark(s) found

All <nav> elements are properly labeled

No banner (header) landmark

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.

Page Structure — as a screen reader sees it

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

A+

Heading Hierarchy

57 headings

PASS

57 headings

Single H1 present

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 TV & Home
H2 Shop TV & Home
H2 More from TV & Home
H2 Explore Entertainment
H2 Support
H2 Shop Accessories
H2 Explore Accessories
H2 Explore Support
H2 Get Help
H2 Helpful Topics
H2 Quick Links
H1 iTunes
H2 iTunes is going places.
H2 iTunes
H3 Download the latest version for Windows.
H2 iTunes
H3 Download the latest version from the Microsoft Store.
H2 iTunes is going places.
H2 Music, TV, and podcasts take center stage.
H2 Presenting Apple Music on Mac.
H2 Apple TV. Premiering on Mac.
H2 Listen up. Podcasts on Mac.
H2 iTunes Support can help answer your questions
H2 Looking for a previous version of iTunes?
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+

Alt Text Quality

No images

PASS

No images

No images on this page

No images on this page.

A+

Form Accessibility

All 1 controls labeled

PASS

All 1 controls labeled

1 control(s) properly labeled

1 controls

1 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
input	input	Search apple.com	aria-label

Link & Button Quality

1 issue(s) across 304 links and 33 buttons

PASS

1 issue(s) across 304 links and 33 buttons

1 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: https://apple.co/ms

303 link(s) with descriptive text

304 links

1 empty

0 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://apple.co/ms	(empty)	empty	Add link text or aria-label

336 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

https://apple.co/ms

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

A+

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

PASS

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

20 pass

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 iTunes	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Shop	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Quick Links	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Shop Special Stores	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Explore Mac	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Shop Mac	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 More from Mac	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Explore iPad	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Shop iPad	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 More from iPad	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Explore iPhone	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Shop iPhone	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 More from iPhone	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Explore Watch	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Shop Watch	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 More from Watch	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Explore Vision	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Shop Vision	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 More from Vision	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Explore AirPods	21.00:1	3.0:1	#000000	#FFFFFF	Pass

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+

Lighthouse Accessibility Audits

Score 97/100 — 1 failing, 29 passed

PASS

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.

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
Watch Ted Lasso on the Apple TV app `div.section-tv > p.legal > a.icon-wrapper > span.icon-copy`
Ted Lasso `p.legal > a.icon-wrapper > span.icon-copy > em`

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

●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

●`[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

●`[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

●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

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

○Image elements have `[alt]` attributes

○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.

○Uses ARIA roles only on compatible elements

○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.