Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

4 PASS 4 REVIEW 5 FIX

404 Error Page

Action

HTTP 404, custom page

FIX

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

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 ✗

Form Accessibility

2 of 4 controls have issues

REVIEW

2 of 4 controls have issues

2 control(s) without accessible label

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

Got: <input type="radio" name="burgerbar-expand" id="burgerbar-none">; <input type="radio" name="burgerbar-expand" id="burgerbar">

2 control(s) properly labeled

4 controls

2 labeled

0 placeholder only

2 unlabeled

Control	Type	Label	Method
#search-checkbox	checkbox	Search	for/id
#search-input	search	Search iMore	for/id
#burgerbar-none	radio	(none)	none
#burgerbar	radio	(none)	none

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

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

Link & Button Quality

Action

4 issue(s) across 157 links and 10 buttons

REVIEW

4 issue(s) across 157 links and 10 buttons

4 link(s) with no accessible text

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

Got: https://www.imore.com; a.meganav-item__link (#367 on page); a.meganav-item__link (#369 on page); a.meganav-item__link (#371 on page)

13 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://futureplc.com/; https://futureplc.com/terms-conditions/; https://futureplc.com/contact/; https://futureplc.com/privacy-policy/; https://futureplc.com/cookies-policy/; https://futureplc.com/careers/; https://futureplc.com/licensing/; https://www.futureplc.com/terms-conditions/?utm_source=ac&utm_medium=footer&u…; https://www.imore.com/about; https://www.imore.com/newsletter (+3 more)

140 link(s) with descriptive text

157 links

4 empty

0 generic text

13 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.imore.com	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
https://futureplc.com/	Visit our corporate site	new tab	Add '(opens in new tab)' to text
https://futureplc.com/terms-conditions/	Terms and conditions	new tab	Add '(opens in new tab)' to text
https://futureplc.com/contact/	Contact Future's experts	new tab	Add '(opens in new tab)' to text
https://futureplc.com/privacy-policy/	Privacy policy	new tab	Add '(opens in new tab)' to text
https://futureplc.com/cookies-policy/	Cookies policy	new tab	Add '(opens in new tab)' to text
https://futureplc.com/careers/	Careers	new tab	Add '(opens in new tab)' to text
https://futureplc.com/licensing/	Licensing	new tab	Add '(opens in new tab)' to text
https://www.futureplc.com/terms-conditio…	External links disclosure	new tab	Add '(opens in new tab)' to text
https://www.imore.com/about	About us	new tab	Add '(opens in new tab)' to text
https://www.imore.com/newsletter	Newsletter	new tab	Add '(opens in new tab)' to text
https://go.future-advertising.com/iMore-…	Advertise with us	new tab	Add '(opens in new tab)' to text
https://www.androidcentral.com/	Android Central	new tab	Add '(opens in new tab)' to text
https://www.windowscentral.com/	Windows Central	new tab	Add '(opens in new tab)' to text

150 links and buttons have descriptive text

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

https://www.imore.com; a.meganav-item__link (#367 on page); a.meganav-item__link (#369 on page); a.meganav-item__link (#371 on page)

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

Add '(opens in new tab)' to link text or aria-label.

https://futureplc.com/; https://futureplc.com/terms-conditions/; https://futureplc.com/contact/; https://futureplc.com/privacy-policy/; https://futureplc.com/cookies-policy/; https://futureplc.com/careers/; https://futureplc.com/licensing/; https://www.futureplc.com/terms-conditions/?utm_source=ac&utm_medium=footer&u…; https://www.imore.com/about; https://www.imore.com/newsletter (+3 more)

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

Favicon & Branding

7 icon(s) detected

REVIEW

7 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 3 fail WCAG AA

REVIEW

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

17 pass 3 fail WCAG AA 12 pass AA only

title iMore - Apple News, Reviews, Deals, & He…

3.00:1

#000000

#595959

needs 4.5:1 (normal text)

16px · top of page (header area)

a Skip to main content

3.00:1

#000000

#595959

needs 4.5:1 (normal text)

16px · top of page (header area)

span Open menu

3.00:1

#000000

#595959

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 iMore	7.56:1	3.0:1	#000000	#9B9B9B	Pass
h2 One more thing… Go…	3.00:1	3.0:1	#000000	#595959	Pass
h2 Best iPad for studen…	3.00:1	3.0:1	#000000	#595959	Pass
h2 Which iPad storage s…	3.00:1	3.0:1	#000000	#595959	Pass
h2 Is your iPhone not r…	3.00:1	3.0:1	#000000	#595959	Pass
h2 Apple Watch Cellular…	3.00:1	3.0:1	#000000	#595959	Pass
h2 Aluminum vs. Stainle…	3.00:1	3.0:1	#000000	#595959	Pass
h2 Apple Watch 40mm vs.…	3.00:1	3.0:1	#000000	#595959	Pass
h2 How to switch Apple …	3.00:1	3.0:1	#000000	#595959	Pass
h2 Best HomeKit video d…	3.00:1	3.0:1	#000000	#595959	Pass
h2 Best HomeKit cameras…	3.00:1	3.0:1	#000000	#595959	Pass
h2 Every security camer…	3.00:1	3.0:1	#000000	#595959	Pass
h2 Best HomeKit door lo…	3.00:1	3.0:1	#000000	#595959	Pass
title iMore - Apple News, …	3.00:1	4.5:1	#000000	#595959	Fail
a Skip to main content	3.00:1	4.5:1	#000000	#595959	Fail
span Open menu	3.00:1	4.5:1	#000000	#595959	Fail
span US Edition	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Australia	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Canada	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span India	21.00:1	4.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.

Landmark Structure

10 landmarks

PASS

10 landmarks

<main> landmark present

5 <nav> landmark(s) found

1 of 5 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

Skip navigation link present

Page Structure — as a screen reader sees it

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

A+

Heading Hierarchy

13 headings

PASS

13 headings

Single H1 present

H1 iMore
H2 One more thing… Goodbye from iMore
H2 Best iPad for students in 2026: Get more done at school with a brand new Apple tablet
H2 Which iPad storage size should you get in 2026?
H2 Is your iPhone not receiving pictures? Here's the fix!
H2 Apple Watch Cellular vs GPS: What's the difference?
H2 Aluminum vs. Stainless Steel Apple Watch: Which should you buy?
H2 Apple Watch 40mm vs. 44mm: Which Apple Watch size should you get?
H2 How to switch Apple ID
H2 Best HomeKit video doorbells for the Home app
H2 Best HomeKit cameras 2026
H2 Every security camera with HomeKit Secure Video support in 2026
H2 Best HomeKit door locks for the Home app in 2026

A+

Alt Text Quality

All 20 images OK

PASS

All 20 images OK

20 image(s) with good alt text

20 images 20 good alt text

All images have appropriate alt text.

A+

Lighthouse Accessibility Audits

Score 100/100 — 0 failing, 31 passed

PASS

100

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.

○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

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

●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

●Background and foreground colors have a sufficient contrast ratio

●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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Uses ARIA roles only on compatible elements

●Image elements do not have `[alt]` attributes that are redundant text.

○`[accesskey]` values are unique

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

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

○Identical links have the same purpose.

○Elements with visible text labels have matching accessible names.

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