Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

14 PASS 6 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 ✗

Heading Hierarchy

14 headings

REVIEW

14 headings

No H1 heading found

Every page should have one H1 that describes the page content.

H2 Smart Home Security Made Simple
H2 HOME SECURITY
H2 Smart Home AI
H2 Home Appliances
H2 Best Smart Security Cameras for Your Home in 2026
H2 HOME DECOR
H2 PRODUCT REVIEWS
H3 BUYING GUIDES & COMPARISON
H2 LATEST ARTICLES
H3 Ninja Air Fryer Pro 5-Quart Review: Is It Worth Buying?
H3 SUMRY 4000W 24V Hybrid Solar Inverter Review: Features, Compatibility, and What to Know Before Buying
H3 How to Make Your Living Room Look Cozy and Expensive on a Budget
H3 Best Smart Water Leak Detectors to Protect Your Home in 2026
H3 Best Smart Lighting Systems for Convenience and Energy Savings in 2026

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

Link & Button Quality

4 issue(s) across 47 links and 3 buttons

REVIEW

4 issue(s) across 47 links and 3 buttons

4 link(s) with no accessible text

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

Got: https://homesentryusa.com/; https://homesentryusa.com/; https://link.amazon/B0cThrpKL; https://www.aliexpress.us/?spm=a2g0o.tm1000022257.logo.1.493c5706LFvorW&_gl=1…

43 link(s) with descriptive text

47 links

4 empty

0 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://homesentryusa.com/	(empty)	empty	Add link text or aria-label
https://homesentryusa.com/	(empty)	empty	Add link text or aria-label
https://link.amazon/B0cThrpKL	(empty)	empty	Add link text or aria-label
https://www.aliexpress.us/?spm=a2g0o.tm1…	(empty)	empty	Add link text or aria-label

46 links and buttons have descriptive text

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

https://homesentryusa.com/; https://homesentryusa.com/; https://link.amazon/B0cThrpKL; https://www.aliexpress.us/?spm=a2g0o.tm1000022257.logo.1.493c5706LFvorW&_gl=1…

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

Iframe Accessibility

2/3 iframe(s) missing title; 0 placeholder(s)

REVIEW

2/3 iframe(s) missing title; 0 placeholder(s)

WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.

WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.

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

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

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

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, 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 2 pass AA only

h2 Smart Home Security Made Simple

1.67:1

#000000

#403118

needs 3.0:1 (large text)

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

button Explore Smart Security

2.61:1

#000000

#744518

needs 4.5:1 (normal text)

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

strong HOME SECURITY

1.05:1

#000000

#140400

needs 3.0:1 (large text)

16px · above the fold

strong Smart Home AI

1.02:1

#000000

#0D0000

needs 3.0:1 (large text)

16px · mid-page

strong Home Appliances

1.93:1

#000000

#53362A

needs 3.0:1 (large text)

16px · mid-page · over background image/gradient

p "Choosing the right security camera is e…

3.13:1

#000000

#655A4E

needs 4.5:1 (normal text)

16px · mid-page · over background image/gradient

a Read Full Review

3.67:1

#000000

#7B6151

needs 4.5:1 (normal text)

16px · mid-page · over background image/gradient

a HOME DECOR

3.77:1

#000000

#7A6543

needs 4.5:1 (normal text)

16px · mid-page · over background image/gradient

6 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 Smart Home Security …	1.67:1	3.0:1	#000000	#403118	Fail
h2 Best Smart Security …	3.36:1	3.0:1	#000000	#6B5E55	Pass
h2 LATEST ARTICLES	17.21:1	3.0:1	#000000	#EEE8DC	Pass
title HOME -	16.13:1	4.5:1	#000000	#F4DEC8	Pass
a Skip to content	16.87:1	4.5:1	#000000	#F4E4D2	Pass
a Home	17.42:1	4.5:1	#000000	#F4E8DC	Pass
a Home Security	15.58:1	4.5:1	#000000	#EBDBD0	Pass
a Smart Home AI	13.50:1	4.5:1	#000000	#D8CCD3	Pass
a Home Appliances	12.42:1	4.5:1	#000000	#DAC1C5	Pass
a Home decor	14.68:1	4.5:1	#000000	#EDD2CB	Pass
a Product Reviews	14.74:1	4.5:1	#000000	#ECD3CA	Pass
a Buying Guides & Comp…	14.34:1	4.5:1	#000000	#F2CEBD	Pass
p Protect your home an…	6.81:1	4.5:1	#000000	#A78D88	Pass
button Explore Smart Securi…	2.61:1	4.5:1	#000000	#744518	Fail
strong HOME SECURITY	1.05:1	3.0:1	#000000	#140400	Fail
strong Smart Home AI	1.02:1	3.0:1	#000000	#0D0000	Fail
strong Home Appliances	1.93:1	3.0:1	#000000	#53362A	Fail
p "Choosing the right …	3.13:1	4.5:1	#000000	#655A4E	Fail
a Read Full Review	3.67:1	4.5:1	#000000	#7B6151	Fail
a HOME DECOR	3.77:1	4.5:1	#000000	#7A6543	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.

Landmark Structure

6 landmarks

PASS

6 landmarks

<main> landmark present

3 <nav> landmark(s) found

All <nav> elements are properly labeled

Skip navigation link present

Skip link target(s) don't exist on page: #main

The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.

Page Structure — as a screen reader sees it

Why this matters

Skip link points at an ID that doesn't exist on the page. The link looks fine visually but does nothing when activated -- silent WCAG 2.4.1 failure.

Learn more ▾

Find the target landmark (typically <main> or the first <h1>) and add `id="..."` matching the skip link's href fragment. Test by tabbing to the skip link and pressing Enter -- focus should jump to the target.

Source: WCAG 2.1 SC 2.4.1

A+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

5 heading(s) are all-uppercase (excluding short acronyms)

Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.

Got: 5 all-caps heading(s)

A+

Alt Text Quality

All 17 images OK

PASS

All 17 images OK

6 decorative image(s) correctly marked

11 image(s) with good alt text

17 images 11 good alt text 6 decorative

All images have appropriate alt text.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

A+

Form Input Types

No form controls on this page

PASS

No form controls on this page

A+

Form Input Quality

No form controls on this page

PASS

No form controls on this page

A+

Mobile Keyboard & Autofill

No form controls -- mobile keyboard check is N/A

PASS

No form controls -- mobile keyboard check is N/A

No form controls on this page

A+

Document Language

Lang attribute set to "en-US"

PASS

Lang attribute set to "en-US"

<html lang="en-US"> is set and valid

Got: en-US

A+

Tabindex Anti-Patterns

1 explicit tabindex attribute(s) checked, no anti-patterns

PASS

1 explicit tabindex attribute(s) checked, no anti-patterns

No tabindex anti-patterns detected

A+

Tap Target Adequacy

All tap targets meet WCAG 2.5.5/2.5.8 sizing

PASS

All tap targets meet WCAG 2.5.5/2.5.8 sizing

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

Mobile-Readable Font Sizes

All 25 visible text node(s) render at >= 12 CSS pixels

PASS

All 25 visible text node(s) render at >= 12 CSS pixels

All text uses legible mobile font sizes (>= 12 CSS px)

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

No `<meta name="theme-color">` -- browser chrome falls back to default

Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.

Lighthouse Accessibility Audits

Score 92/100 — 2 failing, 22 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.

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
Read Full Review `div.elementor > div.elementor-element > div.elementor-element > a.e-602168b-379c659`
Cookie Policy `div.footer-menu-container > ul#footer-menu > li#menu-item-35 > a`
Terms & Conditions `div.footer-menu-container > ul#footer-menu > li#menu-item-36 > a`
Privacy Policy `div.footer-menu-container > ul#footer-menu > li#menu-item-37 > a`
Disclaimer & Affiliate Disclosure `div.footer-menu-container > ul#footer-menu > li#menu-item-34 > a`
Contact Us `div.footer-menu-container > ul#footer-menu > li#menu-item-38 > a`
About Us `div.footer-menu-container > ul#footer-menu > li#menu-item-39 > a`

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.site-header-main-section-left > div.site-header-item > div.site-branding > a.brand `div.site-header-main-section-left > div.site-header-item > div.site-branding > a.brand`
div.footer-widget-area-inner > section#block-11 > figure.wp-block-image > a `div.footer-widget-area-inner > section#block-11 > figure.wp-block-image > a`
div.footer-widget-area-inner > section#block-12 > figure.wp-block-image > a `div.footer-widget-area-inner > section#block-12 > figure.wp-block-image > a`

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.

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

●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

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

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

○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

○Links are distinguishable without relying on color.

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○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

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

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