Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

3 PASS 5 REVIEW 5 FIX

Favicon & Branding

Action

3 icon(s) detected

FIX

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

No apple-touch-icon detected

iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

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 ✗

Landmark Structure

2 landmarks

REVIEW

2 landmarks

<main> landmark present

No <nav> landmark found

No banner (header) landmark

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

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

Alt Text Quality

Action

20 of 325 images have issues

REVIEW

20 of 325 images have issues

1 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

19 image(s) with filename as alt text

32 image(s) with alt text over 125 characters

2 decorative image(s) correctly marked

271 image(s) with good alt text

325 images 271 good alt text 2 decorative 19 generic 1 missing

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

Link & Button Quality

Action

16 issue(s) across 1699 links and 24 buttons

REVIEW

16 issue(s) across 1699 links and 24 buttons

20 link(s) open in new tab without warning

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

Got: ; https://www.facebook.com/WonderHowTo; https://www.pinterest.com/WonderHowTo/; https://x.com/WonderHowTo; https://www.facebook.com/WonderHowTo; https://x.com/WonderHowTo; https://www.pinterest.com/WonderHowTo/; https://www.wonderhowto.com/rss.xml; https://technologyadvice.com/contact-us/; https://technologyadvice.com/privacy-policy/ccpa-opt-out-form/ (+10 more)

16 button(s) with no accessible text

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

Got: button.h-full (#805 on page); button.h-full (#809 on page); button.h-full (#1490 on page); button.h-full (#1494 on page); button.h-full (#2159 on page); button.h-full (#2163 on page); button.h-full (#2993 on page); button.h-full (#2997 on page); button.h-full (#3821 on page); button.h-full (#3825 on page) (+6 more)

1679 link(s) with descriptive text

1699 links

0 empty

0 generic text

20 new tab

16 empty buttons

Element	Text	Issue	Suggested Fix
	partners	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/WonderHowTo	Facebook	new tab	Add '(opens in new tab)' to text
https://www.pinterest.com/WonderHowTo/	Pinterest	new tab	Add '(opens in new tab)' to text
https://x.com/WonderHowTo	X	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/WonderHowTo	Facebook	new tab	Add '(opens in new tab)' to text
https://x.com/WonderHowTo	X	new tab	Add '(opens in new tab)' to text
https://www.pinterest.com/WonderHowTo/	Pinterest	new tab	Add '(opens in new tab)' to text
https://www.wonderhowto.com/rss.xml	RSS Feed	new tab	Add '(opens in new tab)' to text
https://technologyadvice.com/contact-us/	Contact Us	new tab	Add '(opens in new tab)' to text
https://technologyadvice.com/privacy-pol…	California – Do Not Sell My …	new tab	Add '(opens in new tab)' to text
https://technologyadvice.com/careers/	Careers We're Hiring	new tab	Add '(opens in new tab)' to text
https://technologyadvice.com/	TechnologyAdvice	new tab	Add '(opens in new tab)' to text
https://www.techrepublic.com/	TechRepublic	new tab	Add '(opens in new tab)' to text
https://www.eweek.com/	eWeek	new tab	Add '(opens in new tab)' to text
https://www.datamation.com/	DataMation	new tab	Add '(opens in new tab)' to text
https://www.channelinsider.com/	Channel Insider	new tab	Add '(opens in new tab)' to text
https://dzone.com/	DZone	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/WonderHowTo	Facebook	new tab	Add '(opens in new tab)' to text
https://www.pinterest.com/WonderHowTo/	Pinterest	new tab	Add '(opens in new tab)' to text
https://x.com/WonderHowTo	X	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

1687 links and buttons have descriptive text

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

; https://www.facebook.com/WonderHowTo; https://www.pinterest.com/WonderHowTo/; https://x.com/WonderHowTo; https://www.facebook.com/WonderHowTo; https://x.com/WonderHowTo; https://www.pinterest.com/WonderHowTo/; https://www.wonderhowto.com/rss.xml; https://technologyadvice.com/contact-us/; https://technologyadvice.com/privacy-policy/ccpa-opt-out-form/ (+10 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.h-full (#805 on page); button.h-full (#809 on page); button.h-full (#1490 on page); button.h-full (#1494 on page); button.h-full (#2159 on page); button.h-full (#2163 on page); button.h-full (#2993 on page); button.h-full (#2997 on page); button.h-full (#3821 on page); button.h-full (#3825 on page) (+6 more)

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

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

404 Page Quality ✓ Custom 404 Page

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

Color Contrast (Screenshot)

Action

20 text elements analyzed, 8 fail WCAG AA

REVIEW

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

12 pass 8 fail WCAG AA

title Wonder How To » Fresh Hacks For a Chang…

1.28:1

#000000

#192029

needs 4.5:1 (normal text)

16px · top of page (header area)

a ___

1.28:1

#000000

#192029

needs 4.5:1 (normal text)

16px · top of page (header area)

span We value your privacy

1.28:1

#000000

#192029

needs 4.5:1 (normal text)

16px · top of page (header area)

div We and our

1.28:1

#000000

#192029

needs 4.5:1 (normal text)

16px · top of page (header area)

a partners

1.39:1

#000000

#20272F

needs 4.5:1 (normal text)

16px · above the fold

div store and/or access information on a dev…

1.36:1

#000000

#1E252D

needs 4.5:1 (normal text)

16px · above the fold

div Please note that this website/app uses o…

1.31:1

#000000

#1C222A

needs 4.5:1 (normal text)

16px · above the fold

span MORE OPTIONS

2.17:1

#000000

#3F454C

needs 4.5:1 (normal text)

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

1 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
h1 WonderHowTo	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Wonder How To » Fre…	1.28:1	4.5:1	#000000	#192029	Fail
a ___	1.28:1	4.5:1	#000000	#192029	Fail
span We value your privac…	1.28:1	4.5:1	#000000	#192029	Fail
div We and our	1.28:1	4.5:1	#000000	#192029	Fail
a partners	1.39:1	4.5:1	#000000	#20272F	Fail
div store and/or access …	1.36:1	4.5:1	#000000	#1E252D	Fail
div Please note that thi…	1.31:1	4.5:1	#000000	#1C222A	Fail
span MORE OPTIONS	2.17:1	4.5:1	#000000	#3F454C	Fail
span AGREE	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div WonderHowTo	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a WonderHowTo	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Gadget Hacks	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Next Reality	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Null Byte	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Gadget Hacks	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Next Reality	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Food Hacks	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Null Byte	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a The Secret Yumiverse	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.

A+

Heading Hierarchy

1 headings

PASS

1 headings

Single H1 present

H1 WonderHowTo

Form Accessibility

1 of 1 controls have issues

PASS

1 of 1 controls have issues

1 control(s) rely on placeholder only

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

Got: <input type="text" id="search-input">

1 controls

0 labeled

1 placeholder only

0 unlabeled

Control	Type	Label	Method
#search-input	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

Lighthouse Accessibility Audits

Score 91/100 — 2 failing, 25 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
div.glide > div.top-0 > div.absolute > button.h-full `div.glide > div.top-0 > div.absolute > button.h-full`
div.glide > div.top-0 > div.absolute > button.h-full `div.glide > div.top-0 > div.absolute > button.h-full`
div.glide > div.top-0 > div.absolute > button.h-full `div.glide > div.top-0 > div.absolute > button.h-full`
div.glide > div.top-0 > div.absolute > button.h-full `div.glide > div.top-0 > div.absolute > button.h-full`
div.glide > div.top-0 > div.absolute > button.h-full `div.glide > div.top-0 > div.absolute > button.h-full`
div.glide > div.top-0 > div.absolute > button.h-full `div.glide > div.top-0 > div.absolute > button.h-full`
div.glide > div.top-0 > div.absolute > button.h-full `div.glide > div.top-0 > div.absolute > button.h-full`
div.glide > div.top-0 > div.absolute > button.h-full `div.glide > div.top-0 > div.absolute > button.h-full`
div.glide > div.top-0 > div.absolute > button.h-full `div.glide > div.top-0 > div.absolute > button.h-full`
div.glide > div.top-0 > div.absolute > button.h-full `div.glide > div.top-0 > div.absolute > button.h-full`
div.glide > div.top-0 > div.absolute > button.h-full `div.glide > div.top-0 > div.absolute > button.h-full`
div.glide > div.top-0 > div.absolute > button.h-full `div.glide > div.top-0 > div.absolute > button.h-full`
div.glide > div.top-0 > div.absolute > button.h-full `div.glide > div.top-0 > div.absolute > button.h-full`
div.glide > div.top-0 > div.absolute > button.h-full `div.glide > div.top-0 > div.absolute > button.h-full`

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.

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
FROM OUR NETWORK: NULL BYTE `astro-carousel.h-[400px] > div.absolute > div > a.inline-block`
HOW TO `article.group > div.bg-white > div.space-y-2 > div.text-[var(--brand-text-color)]`

These are opportunities to improve the legibility of your content.

○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

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

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

●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

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

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

○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

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

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