Skip to content
https://macrumors.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
75
GRADE
C
FIX
3
REVIEW
4
PASS
6
INFO
0
Checks
13
6 PASS 4 REVIEW 3 FIX
F
Form Accessibility
Action
5 of 6 controls have issues
FIX
5 of 6 controls have issues
Critical::
3 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit">; <input type="submit" name="subscribe" id="mc-embedded-subscribe">; <input type="submit" name="subscribe" id="mc-embedded-subscribe">
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="email" name="EMAIL" id="mce-EMAIL">; <input type="email" name="EMAIL" id="mce-EMAIL">
Info::
1 control(s) properly labeled
6 controls
1 labeled
2 placeholder only
3 unlabeled
ControlTypeLabelMethod
#searchformsearchSearch Sitearia-label
#mce-EMAILemail(Enter Email Address)placeholder only
#mce-EMAILemail(Enter Email Address)placeholder only
#mc-embedded-subscribesubmit(none)none
inputsubmit(none)none
#mc-embedded-subscribesubmit(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<input type="submit">; <input type="submit" name="subscribe" id="mc-embedded-subscribe">; <input type="submit" name="subscribe" id="mc-embedded-subscribe">

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

Placeholder text disappears on focus and is not a reliable label.

<input type="email" name="EMAIL" id="mce-EMAIL">; <input type="email" name="EMAIL" id="mce-EMAIL">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
3 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 3 <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
Favicon & Branding
9 icon(s) detected
REVIEW
9 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 Present
✓ Multiple Sizes Present
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
Dark-specific theme-color detected
A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.
Info::
prefers-color-scheme CSS detected in inline styles
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark Mode✓ Dark Mode Supported
color-scheme meta Not set ✗Dark theme-color #152a44 ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 1 fail WCAG AA
REVIEW

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

19 pass 1 fail WCAG AA
title MacRumors: Apple News and Rumors
1.45:1
#000000
on
#152A44
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 MacRumors4.58:13.0:1
#000000
#67778A
Pass
h2 Videos21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Guides21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Upcoming21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Recent Comments21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Other Stories21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Our Staff21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Related Links21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Deals Newsletter21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Wall Chargers21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Wireless Chargers21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Portable Chargers21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Deals Newsletter21.00:13.0:1
#000000
#FFFFFF
Pass
title MacRumors: Apple New…1.45:14.5:1
#000000
#152A44
Fail
a Skip to Content18.14:14.5:1
#000000
#E9EFF6
Pass
div Got a tip for us?21.00:14.5:1
#000000
#FFFFFF
Pass
a Let us know21.00:14.5:1
#000000
#FFFFFF
Pass
a Send us an email21.00:14.5:1
#000000
#FFFFFF
Pass
a Anonymous form21.00:14.5:1
#000000
#FFFFFF
Pass
button close21.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
8 landmarks
PASS
8 landmarks
Info::
<main> landmark present
Info::
3 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Main navigation" MAIN CONTENTINFO footer
A+
Heading Hierarchy
32 headings
PASS
32 headings
Info::
Single H1 present
  • H1 MacRumors
  • H2 🚨 Tim Cook Stepping Down as Apple CEO
  • H2 Apple Pulled Cal AI for Deceptive Billing Design, Not External Payments
  • H2 Apple Teases 'Incredible Road Map Ahead'
  • H2 Tim Cook Says He's 'Healthy,' Plans to Remain at Apple 'for a Long Time'
  • H2 Apple Releases New iOS 26.5, iPadOS 26.5 and macOS Tahoe 26.5 Public Betas
  • H2 AirPods Pro 3 vs. Sony WF-1000XM6: Which Flagship Earbuds Should You Buy?
  • H2 Satechi Launches ChargeView 140W Desktop Charger
  • H2 Get Up to $52 Off the 11th Gen iPad, Available From $299 [Update: Sold Out]
  • H3 Deals Newsletter
  • H2 Yelp's AI Assistant Can Now Book Restaurants, Doctors, and More
  • H2 Beats and JENNIE Debut Special Edition Onyx Black Solo 4 Headphones
  • H2 Beats Introduces 10-Foot USB-C to USB-C Cables
  • H2 Anker Earth Day Sale Features Up to 40% Off Popular Chargers and More
  • H3 Wall Chargers
  • H3 Wireless Chargers
  • H3 Portable Chargers
  • H3 Deals Newsletter
  • H2 Top Leaders React to Apple Announcing Tim Cook Will Step Down as CEO
  • H2 WhatsApp Testing Paid 'Plus' Subscription Tier – Here's What's Included
  • H2 Report: Ternus to Bring Jobs-Era Decisiveness Back to Apple
  • H2 200MP Telephoto iPhone Lens Unlikely to Arrive Before 2028
  • H2 Apple's Tim Cook Shares Community Letter After Announcing Plans to Step Down as CEO
  • H2 Johny Srouji Taking Over as Apple's Chief Hardware Officer as John Ternus Transitions to CEO
  • H2 Apple CEO Tim Cook Stepping Down, John Ternus Taking Over
  • H2 Videos
  • H2 Guides
  • H2 Upcoming
  • H2 Recent Comments
  • H2 Other Stories
  • H2 Our Staff
  • H2 Related Links
A+
Alt Text Quality
All 83 images OK
PASS
All 83 images OK
Info::
10 decorative image(s) correctly marked
Info::
73 image(s) with good alt text
83 images 73 good alt text 10 decorative
All images have appropriate alt text.
A
404 Error Page
HTTP 404, custom page
PASS
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
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Open Sidebar ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
A+
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: MacRumors
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria ✓ Installable
Name MacRumors ✓192×192 icon ✓512×512 icon ✓Start URL /?pwa=1 ✓Display Mode standalone ✓
Name MacRumors Display Mode standalone Theme Color #152a44 Background Color #152a44 Icons 4 icon(s)
A
Lighthouse Accessibility Audits
Score 94/100 — 3 failing, 29 passed
PASS
94

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
Ternus will become Apple's CEO on September 1. div.content--2u3grYDr > div.ugc--2nTu61bm > div.js-contentInner > p
iPhone 18 Pro div.ugc--2nTu61bm > div.js-contentInner > p > a
iPhone Fold div.ugc--2nTu61bm > div.js-contentInner > p > a
Sign up div.js-contentInner > div.no-raptive > p > a
More from Trump: div.content--2u3grYDr > div.ugc--2nTu61bm > div.js-contentInner > p

These are opportunities to improve the legibility of your content.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Share on X article.article--2pJwZBkO > div.footer--2v61-WeP > div.social--159R8SRB > a
Beats and JENNIE Debut Special Edition Onyx Black Solo 4 Headphones article.article--2pJwZBkO > div.titlebar--3N4MCKxL > h2.heading--1cooZo6n > a
Beats Introduces 10-Foot USB-C to USB-C Cables article.article--2pJwZBkO > div.titlebar--3N4MCKxL > h2.heading--1cooZo6n > a
Share on X article.article--2pJwZBkO > div.footer--2v61-WeP > div.social--159R8SRB > a
Share on Facebook article.article--2pJwZBkO > div.footer--2v61-WeP > div.social--159R8SRB > a

These items highlight common accessibility best practices.

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
Featured On/Off div.contentWrap--qVat7btW > div.footerInner--U2z8mpf2 > div.footerBottom--H-xNVWfy > a
Full Articles On/Off div.contentWrap--qVat7btW > div.footerInner--U2z8mpf2 > div.footerBottom--H-xNVWfy > a
Fluid HD div.contentWrap--qVat7btW > div.footerInner--U2z8mpf2 > div.footerBottom--H-xNVWfy > a
○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
●Input buttons have discernible text.
●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.
●ARIA attributes are used as specified for the element's role
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[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 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
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements 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
○ARIA IDs are unique
○No form fields have multiple labels
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○`<input type="image">` elements have `[alt]` text
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○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
○`<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.
○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