Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 4 REVIEW 4 FIX

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

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-acyj8p

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.

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://ifixit.com/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://ifixit.com/manifest.json

Manifest contains invalid JSON.

Dark Mode Support

Action

Theme color only

FIX

Theme color only

Theme-color present but no dark variant

A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.

Got: #ffffff

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 ModePartial Dark Mode

color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

Landmark Structure

Action

38 landmarks

REVIEW

38 landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

No <nav> landmark found

No banner (header) landmark

Skip navigation link present

Page Structure — as a screen reader sees it

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

Favicon & Branding

14 icon(s) detected

REVIEW

14 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, 2 fail WCAG AA

REVIEW

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

18 pass 2 fail WCAG AA

title iFixit: The Free Repair Manual

1.15:1

#000000

#11161A

needs 4.5:1 (normal text)

16px · top of page (header area)

a Skip to main content

1.15:1

#000000

#11161A

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 The Free Repair Guid…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 for everything writt…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Never take broken fo…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Repair guides for ev…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 The Repair Pulse	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Our Allies	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Step-by-step Repair …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Quality Parts and Pr…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 A Community of Frien…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 What Every Renter Sh…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 AirPods Max 2 Teardo…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Small Appliances Are…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 What Every Renter Sh…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Your Dishwasher Filt…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Sign up for our news…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Repair Business Tool…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Pro Tech Toolkit	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Spring Cleaning!	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title iFixit: The Free Rep…	1.15:1	4.5:1	#000000	#11161A	Fail
a Skip to main content	1.15:1	4.5:1	#000000	#11161A	Fail

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.

Lighthouse Accessibility Audits

Score 86/100 — 4 failing, 23 passed

REVIEW

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.

ARIA

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Download the app `div.css-1oxagfj > div.css-kzvh2p > div.css-k9csqw > ul.css-1cq2g21`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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
Apr 16, 2026 `a.group > article.flex > div.flex > p.m-0`
Apr 6, 2026 `a.group > article.flex > div.flex > p.m-0`
Apr 14, 2026 `a.group > article.flex > div.flex > p.m-0`
Apr 13, 2026 `a.group > article.flex > div.flex > p.m-0`
Apr 6, 2026 `a.group > article.flex > div.flex > p.m-0`
Let me read it first! `section.container-content-home > div.grid > div.newsletter-sub > a.mt-3`

These are opportunities to improve the legibility of your content.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.wp > article.post-114682 > div.entry-content > a.block-link `div.wp > article.post-114682 > div.entry-content > a.block-link`

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.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

These items highlight common accessibility best practices.

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

●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

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

●Deprecated ARIA roles were not used

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

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○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

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

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

○Links are distinguishable without relying on color.

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

○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

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

A+

Heading Hierarchy

18 headings

PASS

18 headings

Single H1 present

H1 The Free Repair Guide
H2 for everything written by everyone
H2 Never take broken for an answer
H3 Step-by-step Repair Guides
H3 Quality Parts and Precision Tools
H3 A Community of Friendly Fixers
H2 Repair guides for every thing, written by everyone.
H2 The Repair Pulse
H3 What Every Renter Should Know About Plumbing Repairs
H3 AirPods Max 2 Teardown: Same Design, No Fixes
H3 Small Appliances Are Flunking Right to Repair, PIRG Report Finds
H3 What Every Renter Should Know About Electrical Repairs
H3 Your Dishwasher Filter Is Disgusting: Here’s How to Clean It
H3 Sign up for our newsletter
H3 Repair Business Toolkit
H3 Pro Tech Toolkit
H2 Our Allies
H3 Spring Cleaning!

A+

Alt Text Quality

All 31 images OK

PASS

All 31 images OK

2 decorative image(s) correctly marked

29 image(s) with good alt text

31 images 29 good alt text 2 decorative

All images have appropriate alt text.

Form Accessibility

1 of 5 controls have issues

PASS

1 of 5 controls have issues

1 control(s) without accessible label

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

Got: <input>

4 control(s) properly labeled

5 controls

4 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
input	input	search	aria-label
input	input	search	aria-label
#homepage-newsletter-email	email	Enter your email	for/id
input	email	Stay in the loop	aria-label
input	input	(none)	none

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

<input>

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

108 links, 11 buttons — all OK

PASS

108 links, 11 buttons — all OK

1 image-only link(s) without alt text

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

Got: a[href="https://www.ifixit.com/Guide/How+to+Clean+Corroded+Battery+Terminals/164164"]

1 link(s) open in new tab without warning

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

Got: https://www.youtube.com/watch?v=WTeqEs28CgU

106 link(s) with descriptive text

108 links

0 empty

0 generic text

1 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.youtube.com/watch?v=WTeqEs28…	Teardowns …	new tab	Add '(opens in new tab)' to text
https://www.ifixit.com/Guide/How+to+Clea…	How to Clean Corroded Battery …	img no alt	Add alt attribute to the image

117 links and buttons have descriptive text

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

a[href="https://www.ifixit.com/Guide/How+to+Clean+Corroded+Battery+Terminals/164164"]

Why this matters

Image-only links with no alt are unidentifiable to screen-reader users — link's destination is invisible.

Source: WCAG 2.1 SC 2.4.4

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

https://www.youtube.com/watch?v=WTeqEs28CgU

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

A+

Print Stylesheet

Print styles detected

PASS

Print styles detected

External print stylesheet detected

Got: https://assets.cdn.ifixit.com/Assets/Admin/ifixit/Shared-print-4vKZnU54L24ZnG6tuvAwTw.css

Print Stylesheet ✓ Print Optimized

Print stylesheet https://assets.cdn.ifixit.com/Assets/Admin/ifixit/Shared-print-4vKZnU54L24ZnG6tuvAwTw.css ✓Inline @media print Not detected ✗

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.