Skip to content
https://mac.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
53
GRADE
F
FIX
6
REVIEW
3
PASS
4
INFO
0
Checks
13
4 PASS 3 REVIEW 6 FIX
F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
Soft 404: server returns HTTP 200 for non-existent pages
The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.
Got: Status: 200 for /beavercheck-404-test-h4ezdp
404 Page Quality ✗ Soft 404 (HTTP 200)
Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

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
F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://mac.com/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://mac.com/manifest.json

Manifest contains invalid JSON.

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 ✗
B
Landmark Structure
10 landmarks
REVIEW
10 landmarks
Info::
<main> landmark present
Info::
5 <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 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
Alt Text Quality
16 of 63 images have issues
REVIEW
16 of 63 images have issues
Warning::
16 image(s) with generic alt text
Info::
5 image(s) with alt text over 125 characters
Info::
12 decorative image(s) correctly marked
Info::
30 image(s) with good alt text
63 images 30 good alt text 12 decorative 16 generic
IssueCount
generic16 image(s)
too long5 image(s)
C
Navigation UX
Action
2 navigation pattern(s)
REVIEW
2 navigation pattern(s)
Info::
Breadcrumb navigation detected
Got: aria-label
Info::
Search functionality detected
Got: role-search
Info::
5 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs aria-label navigation
Search role='search' landmark
Skip Link
Labeled Navigation 5 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
4 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
A+
Heading Hierarchy
63 headings
PASS
63 headings
Info::
Single H1 present
  • H1 Mac
  • H2 Explore the lineup.
  • H3 MacBook Neo
  • H3 MacBook Air 13” and 15”
  • H3 MacBook Pro 14” and 16”
  • H3 iMac
  • H3 Mac mini
  • H3 Mac Studio
  • H3 Studio Display
  • H3 Studio Display XDR
  • H3 MacBook Neo
  • H3 MacBook Air 13” and 15”
  • H3 MacBook Pro 14” and 16”
  • H3 iMac
  • H3 Mac mini
  • H3 Mac Studio
  • H3 Studio Display
  • H3 Studio Display XDR
  • H2 Why Apple is the bestplace to buy Mac.
  • H3 Ways to Buy
  • H3 Education Pricing
  • H3 Personal Setup
  • H3 Customize Your Mac
  • H3 Delivery & Pickup
  • H3 Guided Shopping
  • H3 Apple Store App
  • H2 Get to know Mac.
  • H3 Performance and Battery Life
  • H3 Built for AI
  • H3 macOS a⁠n⁠d⁠ ⁠A⁠p⁠p⁠l⁠e⁠ ⁠I⁠n⁠t⁠e⁠l⁠l⁠i⁠g⁠e⁠n⁠c⁠e
  • H3 Mac + iPhone
  • H3 Compatibility
  • H3 Privacy and Security
  • H3 Durability
  • H3 Apple Values
  • H2 Help me choose.
  • H3 Answer a few questions to find the best Mac for you.
  • H2 Switch to Mac.
  • H3 Give us the old. Save on the new.
  • H3 Mac does that.
  • H2 Mac essentials.
  • H3 Mac accessories
  • H3 Studio Display
  • H2 Unlock the world of Apple.
  • H3 Mac and iPhone
  • H3 Mac and iPad
  • H3 Mac and Apple Watch
  • H2 Mac
  • H3 Explore Mac
  • H3 Shop Mac
  • H3 More from Mac
  • 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+
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+
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)
ElementRatioRequiredFGBGResult
h2 Apple Footer12.39:13.0:1
#000000
#B9C9D6
Pass
h3 Explore Mac12.39:13.0:1
#000000
#B9C9D6
Pass
h3 Shop Mac12.39:13.0:1
#000000
#B9C9D6
Pass
h3 More from Mac12.39:13.0:1
#000000
#B9C9D6
Pass
title Mac - Apple18.45:14.5:1
#000000
#F0F0F2
Pass
span Apple18.45:14.5:1
#000000
#F0F0F2
Pass
span Store18.45:14.5:1
#000000
#F0F0F2
Pass
span Mac18.45:14.5:1
#000000
#F0F0F2
Pass
span iPad19.96:14.5:1
#000000
#F9F9FA
Pass
span iPhone21.00:14.5:1
#000000
#FFFFFF
Pass
span Watch19.29:14.5:1
#000000
#F5F5F7
Pass
span Vision20.31:14.5:1
#000000
#FBFBFC
Pass
span AirPods21.00:14.5:1
#000000
#FFFFFF
Pass
span TV & Home21.00:14.5:1
#000000
#FFFFFF
Pass
span Entertainment21.00:14.5:1
#000000
#FFFFFF
Pass
span Accessories21.00:14.5:1
#000000
#FFFFFF
Pass
span Support21.00:14.5:1
#000000
#FFFFFF
Pass
span Buy Mac with educati…21.00:14.5:1
#000000
#FFFFFF
Pass
span Shop21.00:14.5:1
#000000
#FFFFFF
Pass
span Mac19.96:14.5:1
#000000
#F9F9FA
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 95/100 — 1 failing, 29 passed
PASS
95

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.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.ProductTile_productImage__6tu_j > figure.ResponsivePicture_responsive-picture__VWL7l > picture.ResponsivePicture_responsive-picture__picture__jjeBP > img
div.ProductTile_productImage__6tu_j > figure.ResponsivePicture_responsive-picture__VWL7l > picture.ResponsivePicture_responsive-picture__picture__jjeBP > img
div.ProductTile_productImage__6tu_j > figure.ResponsivePicture_responsive-picture__VWL7l > picture.ResponsivePicture_responsive-picture__picture__jjeBP > img
div.ProductTile_productImage__6tu_j > figure.ResponsivePicture_responsive-picture__VWL7l > picture.ResponsivePicture_responsive-picture__picture__jjeBP > img
div.ProductTile_productImage__6tu_j > figure.ResponsivePicture_responsive-picture__VWL7l > picture.ResponsivePicture_responsive-picture__picture__jjeBP > img
div.ProductTile_productImage__6tu_j > figure.ResponsivePicture_responsive-picture__VWL7l > picture.ResponsivePicture_responsive-picture__picture__jjeBP > img
div.ProductTile_productImage__6tu_j > figure.ResponsivePicture_responsive-picture__VWL7l > picture.ResponsivePicture_responsive-picture__picture__jjeBP > img
div.ProductTile_productImage__6tu_j > figure.ResponsivePicture_responsive-picture__VWL7l > picture.ResponsivePicture_responsive-picture__picture__jjeBP > img

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

○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
●Background and foreground colors have a sufficient contrast ratio
●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
●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
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○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.

Send Feedback