Skip to content
https://macworld.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
63
GRADE
D
FIX
4
REVIEW
5
PASS
4
INFO
0
Checks
13
4 PASS 5 REVIEW 4 FIX
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 ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
1 navigation landmark(s) detected
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 1 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Heading Hierarchy
24 headings
REVIEW
24 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H3 John Ternus is not inheriting your father's Apple
  • H3 We might have to wait a little longer for the first touchscreen MacBook
  • H3 RIP Cosmic Orange. You were too fun for this world
  • H3 LATEST STORIES
  • H3 Don't worry, Tim Cook is fine, and he's not leaving Apple
  • H3 Our favorite Apple-beating USB-C cables are now longer and faster
  • H3 This awesome made-for-iPhone Anker 45W charger is 30% off
  • H3 Best iPad & iPhone VPN: Our picks for private, secure browsing from anywhere
  • H3 Tim Cook's reward for exemplary service? The worst job in the world
  • H3 Best Apple Find My Bluetooth trackers: AirTag alternatives that'll fit anywhere
  • H3 John Ternus is not inheriting your father's Apple
  • H3 The very best iPad stands for every occasion
  • H3 Tim Cook stepping down as CEO in shock announcement
  • H3 iOS 26.5 beta 3 is here, but don't expect many new features
  • H3 iPhone 18 Pro & Pro Max: All the biggest rumors so far
  • H3 iOS 27 may not support iPhone 11, 2nd-gen iPhone SE
  • H3 We might have to wait a little longer for the first touchscreen MacBook
  • H3 Apple smart glasses: Everything you need to know
  • H3 iPhone 18 Pro colors revealed: Exclusive look at 2026 models
  • H3 10 iPad milestones that changed the tablet computer forever
  • H3 RIP Cosmic Orange. You were too fun for this world
  • H3 Touchscreen MacBook Pro M6 rumors: What we know about Apple's MacBook redesign
  • H3 Best iPhone 17 cases for iPhone 17, 17 Pro & 17 Pro Max, 17e and Air
  • H3 iVanky FusionDock Ultra review: New 26-port Mac docking station has it all

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

B
Alt Text Quality
2 of 25 images have issues
REVIEW
2 of 25 images have issues
Critical::
2 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
1 decorative image(s) correctly marked
Info::
22 image(s) with good alt text
25 images 22 good alt text 1 decorative 2 missing
IssueCount
missing2 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

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
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title g ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
B
Favicon & Branding
4 icon(s) detected
REVIEW
4 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
B
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
REVIEW

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

20 pass 3 pass AA only
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h3 John Ternus is not i…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 We might have to wai…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 RIP Cosmic Orange. Y…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 LATEST STORIES21.00:13.0:1
#000000
#FFFFFF
Pass
title Macworld - News, Tip…6.57:14.5:1
#000000
#3399CC
Pass
span Sign up for Macworld…6.57:14.5:1
#000000
#3399CC
Pass
span Receive the latest n…5.18:14.5:1
#6C6D6E
#FFFFFF
Pass
p DON'T MISS OUT18.26:14.5:1
#000000
#EFEFEF
Pass
p No, Thanks21.00:14.5:1
#000000
#FFFFFF
Pass
span English US Edition21.00:14.5:1
#000000
#FFFFFF
Pass
li Edition21.00:14.5:1
#000000
#FFFFFF
Pass
a English UK21.00:14.5:1
#000000
#FFFFFF
Pass
a English US21.00:14.5:1
#000000
#FFFFFF
Pass
a Mac21.00:14.5:1
#000000
#FFFFFF
Pass
a iPhone21.00:14.5:1
#000000
#FFFFFF
Pass
a iPad21.00:14.5:1
#000000
#FFFFFF
Pass
a Apple Watch21.00:14.5:1
#000000
#FFFFFF
Pass
a AirPods21.00:14.5:1
#000000
#FFFFFF
Pass
a Vision Pro21.00:14.5:1
#000000
#FFFFFF
Pass
span More21.00:14.5: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
Landmark Structure
4 landmarks
PASS
4 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
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.
Page Structure — as a screen reader sees it
BANNER header NAV MAIN 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

A+
Form Accessibility
All 3 controls labeled
PASS
All 3 controls labeled
Info::
3 control(s) properly labeled
3 controls
3 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#sideNavEditorCheckboxcheckboxg English US Editionfor/id
inputtextAsk us a questionaria-label
#footerSelectselectSelect Foundry Networkaria-label
A+
Lighthouse Accessibility Audits
Score 97/100 — 2 failing, 29 passed
PASS
97

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
HOT TOPICS header#masthead > div#secondaryNav > div.secondaryNav-wrap > span.secondaryNav-title

These are opportunities to improve the legibility of your content.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
MORE STORIES div.articleFeed > div.articleFeed-inner > div.articleFeed-button > a.btn
POLICIES Expand POLICIES div.primaryFooter-menu-wrap > ul#menu-footer-primary-menu-en-us > li#menu-item-100000714 > button.menu-toggle-button
ABOUT Expand ABOUT div.primaryFooter-menu-wrap > ul#menu-secondary-footer-menu-en-us > li#menu-item-100000716 > button.menu-toggle-button
MORE FROM MACWORLD Expand submenu for More from Macworld div.primaryFooter-menu-wrap > ul#third-column-footer-menu > li#third-column-footer-menu-item-one > button.menu-toggle-button
SUBSCRIBE Expand submenu for Subscribe div.primaryFooter-menu-wrap > ul#forth-column-footer-menu > li#third-column-footer-menu-item > button.menu-toggle-button
○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]` 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
●Form elements have associated labels
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●Select elements have associated label elements.
●`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
●`<frame>` or `<iframe>` elements have a title
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●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.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
○`[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 an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○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
○`<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
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○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.
○`[lang]` attributes have a valid value
○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