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 5 REVIEW 4 FIX

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 ✗

Alt Text Quality

1 of 65 images have issues

REVIEW

1 of 65 images have issues

1 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

5 image(s) with alt text over 125 characters

1 decorative image(s) correctly marked

58 image(s) with good alt text

65 images 58 good alt text 1 decorative 1 missing

Issue	Count
missing	1 image(s)
too long	5 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

Form Accessibility

3 of 7 controls have issues

REVIEW

3 of 7 controls have issues

3 control(s) rely on placeholder only

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

Got: <input type="text" name="s" id="search-input-69e8643831db4">; <input type="text" name="s" id="search-input-69e8643845ba6">; <input type="text" name="s" id="search-input-69e86438af78b">

4 control(s) properly labeled

7 controls

4 labeled

3 placeholder only

0 unlabeled

Control	Type	Label	Method
input	submit	Search	aria-label
input	submit	Search	aria-label
#email-footer	text	Add email address	aria-label
input	submit	Search	aria-label
#search-input-69e8643845ba6	text	(Search)	placeholder only
#search-input-69e86438af78b	text	(Search)	placeholder only
#search-input-69e8643831db4	text	(Search)	placeholder only

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

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

Link & Button Quality

Action

3 issue(s) across 241 links and 5 buttons

REVIEW

3 issue(s) across 241 links and 5 buttons

2 link(s) with no accessible text

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

Got: #; #

12 link(s) open in new tab without warning

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

Got: https://order.familyhandyman.com/servlet/OrdersGateway?cds_mag_code=FHM&cds_p…; https://www.trustedmediabrands.com/ca-privacy-notice/; https://www.trustedmediabrands.com/our-commitment-to-accessibility/; https://order.familyhandyman.com/servlet/OrdersGateway?cds_mag_code=FHM&cds_p…; https://www.google.com/chrome/; https://www.apple.com/safari/; https://www.mozilla.org/en-US/firefox/; https://www.microsoft.com/en-us/edge; https://www.facebook.com/TheFamilyHandyman/; https://www.pinterest.com/family_handyman/ (+2 more)

1 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.search-tap (#153 on page)

227 link(s) with descriptive text

241 links

2 empty

0 generic text

12 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
https://www.familyhandyman.com/list/buil…	14 Essential Tips For Installi…	img no alt	Add alt attribute to the image
https://order.familyhandyman.com/servlet…	Magazine	new tab	Add '(opens in new tab)' to text
https://www.trustedmediabrands.com/ca-pr…	Your CA Privacy Rights	new tab	Add '(opens in new tab)' to text
https://www.trustedmediabrands.com/our-c…	Accessibility Statement	new tab	Add '(opens in new tab)' to text
https://order.familyhandyman.com/servlet…	Subscribe to Family Handyman	new tab	Add '(opens in new tab)' to text
https://www.google.com/chrome/	Google Chrome	new tab	Add '(opens in new tab)' to text
https://www.apple.com/safari/	Apple Safari	new tab	Add '(opens in new tab)' to text
https://www.mozilla.org/en-US/firefox/	Mozilla Firefox	new tab	Add '(opens in new tab)' to text
https://www.microsoft.com/en-us/edge	Microsoft Edge	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/TheFamilyHandym…	Facebook	new tab	Add '(opens in new tab)' to text
https://www.pinterest.com/family_handyma…	Pinterest	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/familyhandyman…	Instagram	new tab	Add '(opens in new tab)' to text
https://twitter.com/Family_Handyman/	Twitter	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label

231 links and buttons have descriptive text

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

#; #

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://order.familyhandyman.com/servlet/OrdersGateway?cds_mag_code=FHM&cds_p…; https://www.trustedmediabrands.com/ca-privacy-notice/; https://www.trustedmediabrands.com/our-commitment-to-accessibility/; https://order.familyhandyman.com/servlet/OrdersGateway?cds_mag_code=FHM&cds_p…; https://www.google.com/chrome/; https://www.apple.com/safari/; https://www.mozilla.org/en-US/firefox/; https://www.microsoft.com/en-us/edge; https://www.facebook.com/TheFamilyHandyman/; https://www.pinterest.com/family_handyman/ (+2 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

Icon-only buttons need an aria-label so screen readers can announce them.

button.search-tap (#153 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

Favicon & Branding

Action

3 icon(s) detected

REVIEW

3 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 10 fail WCAG AA

REVIEW

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

10 pass 10 fail WCAG AA 4 pass AA only

a Watch Free

3.29:1

#000000

#6F5C43

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

a Pro

3.27:1

#000000

#6D5C48

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

a New Homeowners

2.80:1

#000000

#675132

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

a Projects

2.58:1

#000000

#5D4D35

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

a Plywood Challenge

2.92:1

#000000

#65553E

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

a Product Reviews

2.93:1

#000000

#66553B

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

a Subscribe

2.81:1

#000000

#64523C

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

a DIY Diaries

3.45:1

#000000

#6B614E

needs 4.5:1 (normal text)

16px · above the fold

a This DIY Couple “Unflipped” a Modern…

1.87:1

#000000

#4E361E

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

a By Rebecca Wright

1.73:1

#000000

#512D11

needs 4.5:1 (normal text)

16px · mid-page

8 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Explore Family Handy…	6.23:1	3.0:1	#000000	#8B8C8D	Pass
h2 Trending Topics	6.23:1	3.0:1	#000000	#8B8C8D	Pass
h2 Most Popular	6.23:1	3.0:1	#000000	#8B8C8D	Pass
h2 Meet the Team	6.23:1	3.0:1	#000000	#8B8C8D	Pass
h2 Shopping	6.23:1	3.0:1	#000000	#8B8C8D	Pass
h3 Sign Up For Our News…	6.23:1	3.0:1	#000000	#8B8C8D	Pass
title The Family Handyman …	6.92:1	4.5:1	#000000	#949494	Pass
a Skip to main content	6.92:1	4.5:1	#000000	#949494	Pass
span MENU	6.92:1	4.5:1	#000000	#949494	Pass
label Search terms	5.80:1	4.5:1	#000000	#8A867F	Pass
a Watch Free	3.29:1	4.5:1	#000000	#6F5C43	Fail
a Pro	3.27:1	4.5:1	#000000	#6D5C48	Fail
a New Homeowners	2.80:1	4.5:1	#000000	#675132	Fail
a Projects	2.58:1	4.5:1	#000000	#5D4D35	Fail
a Plywood Challenge	2.92:1	4.5:1	#000000	#65553E	Fail
a Product Reviews	2.93:1	4.5:1	#000000	#66553B	Fail
a Subscribe	2.81:1	4.5:1	#000000	#64523C	Fail
a DIY Diaries	3.45:1	4.5:1	#000000	#6B614E	Fail
a This DIY Couple “U…	1.87:1	4.5:1	#000000	#4E361E	Fail
a By Rebecca Wright	1.73:1	4.5:1	#000000	#512D11	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.

A+

Landmark Structure

7 landmarks

PASS

7 landmarks

<main> landmark present

4 <nav> landmark(s) found

All <nav> elements are properly labeled

Skip navigation link present

Page Structure — as a screen reader sees it

Heading Hierarchy

18 headings, 1 skip(s)

PASS

18 headings, 1 skip(s)

Single H1 present

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H1 OSB Makes Cool Plywood Furniture—This Coffee Table’s Proof
H2 Plywood Projects
H2 Explore Family Handyman
H4 What are you searching for today? skipped
H4 Editor's picks
H2 Trending Topics
H2 Terrific Tiling
H2 Backyard Beautificaton
H2 Most Popular
H2 Meet the Team
H2 Shopping
H2 Bills Bills Bills
H2 Pro
H2 Smarter Shopping
H2 Crucial Car Knowledge
H2 Build a Better Bedtime
H2 Recall Central
H3 Sign Up For Our Newsletter

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

404 Error Page

HTTP 404, custom page

PASS

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page not found | Family Handyman ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

Lighthouse Accessibility Audits

Score 94/100 — 2 failing, 28 passed

PASS

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

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
section.nav-wrapper > section.primary-nav > div.magnifying-glass-wrapper > button.search-tap `section.nav-wrapper > section.primary-nav > div.magnifying-glass-wrapper > button.search-tap`

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.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
What are you searching for today? `div.editor-pick > div.editor-pick-wrapper > div.search-module-wrapper > h4`

These are opportunities to improve keyboard navigation in your application.

○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

●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

●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

●Touch targets have sufficient size and spacing.

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

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

○`<frame>` or `<iframe>` elements have a title

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

○Skip links are focusable.

○No element has a `[tabindex]` value greater than 0

○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

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