Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

13 PASS 6 REVIEW 5 FIX

Favicon & Branding

Action

2 icon(s) detected

FIX

2 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

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

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

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: #000

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.

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

25 headings, 1 skip(s)

REVIEW

25 headings, 1 skip(s)

Multiple H1 headings (3 found)

A page should have only one H1. Multiple H1s dilute the document outline.

Heading level skipped: H2 → H4 (missing H3)

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

H2 Our Biggest Ever One Day Sale
H1 1Clickblinds
H2 Search Products
H3 Quick Search:
H1 NO DRILL SHUTTERS THAT FIT PERFECTLY duplicate H1
H1 WE OFFER BLINDS INSTALLATION duplicate H1
H2 PROUDLY SERVING THE USA
H3 THE PERFECT FIT
H3 NEXT DAY DISPATCH AVAILABLE
H3 5 YEAR WARRANTY
H3 4.5/5 STARS
H2 Our One Day Sale
H2 FAQ'S
H4 BLINDS TYPES skipped
H4 INFORMATION
H4 Help
H3 Professional Installation
H3 Good News!
H3 Sorry, Not Available
H4 Get excited - You're all set!
H2 You're Eligible
H3 You're Eligible
H3 How It Works
H4 Your Cart (0)
H3 Opening Direction Options

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

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

Alt Text Quality

Action

5 of 20 images have issues

REVIEW

5 of 20 images have issues

5 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

2 decorative image(s) correctly marked

13 image(s) with good alt text

20 images 13 good alt text 2 decorative 5 missing

Issue	Count
missing	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

Iframe Accessibility

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

REVIEW

2/2 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.

Mobile-Readable Font Sizes

96% of visible text renders at >= 12 CSS px (3 below threshold)

REVIEW

96% of visible text renders at >= 12 CSS px (3 below threshold)

3 text node(s) render below 12 CSS pixels on mobile

Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <div> 8.0px ("HRS"); <div> 8.0px ("MINS"); <div> 8.0px ("SECS").

404 Error Page

Action

HTTP 404, custom page

REVIEW

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 ✓Page Title 404 Not Found– 1Clickblinds ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Color Contrast (Screenshot)

Action

20 text elements analyzed, 20 fail WCAG AA

REVIEW

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

0 pass 20 fail WCAG AA

h1 NO DRILL SHUTTERS THAT

1.94:1

#000000

#4F3739

needs 3.0:1 (large text)

32px · bottom of viewport · over background image/gradient

h1 FIT PERFECTLY

1.94:1

#000000

#4F3739

needs 3.0:1 (large text)

32px · bottom of viewport · over background image/gradient

h1 WE OFFER BLINDS

1.94:1

#000000

#4F3739

needs 3.0:1 (large text)

32px · bottom of viewport · over background image/gradient

h1 INSTALLATION

1.94:1

#000000

#4F3739

needs 3.0:1 (large text)

32px · bottom of viewport · over background image/gradient

h2 Our Biggest Ever One Day Sale

2.88:1

#000000

#00651F

needs 3.0:1 (large text)

24px · top of page (header area)

h2 Search Products

1.94:1

#000000

#4F3739

needs 3.0:1 (large text)

24px · bottom of viewport

h2 PROUDLY SERVING THE USA

1.94:1

#000000

#4F3739

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Our One Day Sale

1.94:1

#000000

#4F3739

needs 3.0:1 (large text)

24px · bottom of viewport

h2 FAQ'S

1.94:1

#000000

#4F3739

needs 3.0:1 (large text)

24px · bottom of viewport

h2 You're Eligible

1.94:1

#000000

#4F3739

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Quick Search:

1.94:1

#000000

#4F3739

needs 3.0:1 (large text)

19px · bottom of viewport

h3 THE PERFECT FIT

1.94:1

#000000

#4F3739

needs 3.0:1 (large text)

19px · bottom of viewport

h3 NEXT DAY DISPATCH AVAILABLE

1.94:1

#000000

#4F3739

needs 3.0:1 (large text)

19px · bottom of viewport

h3 5 YEAR WARRANTY

1.94:1

#000000

#4F3739

needs 3.0:1 (large text)

19px · bottom of viewport

h3 4.5/5 STARS

1.94:1

#000000

#4F3739

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Professional Installation

1.94:1

#000000

#4F3739

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Good News!

1.94:1

#000000

#4F3739

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Sorry, Not Available

1.94:1

#000000

#4F3739

needs 3.0:1 (large text)

19px · bottom of viewport

h3 You're Eligible

1.94:1

#000000

#4F3739

needs 3.0:1 (large text)

19px · bottom of viewport

h3 How It Works

1.94:1

#000000

#4F3739

needs 3.0:1 (large text)

19px · bottom of viewport

4 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 NO DRILL SHUTTERS TH…	1.94:1	3.0:1	#000000	#4F3739	Fail
h1 FIT PERFECTLY	1.94:1	3.0:1	#000000	#4F3739	Fail
h1 WE OFFER BLINDS	1.94:1	3.0:1	#000000	#4F3739	Fail
h1 INSTALLATION	1.94:1	3.0:1	#000000	#4F3739	Fail
h2 Our Biggest Ever One…	2.88:1	3.0:1	#000000	#00651F	Fail
h2 Search Products	1.94:1	3.0:1	#000000	#4F3739	Fail
h2 PROUDLY SERVING THE …	1.94:1	3.0:1	#000000	#4F3739	Fail
h2 Our One Day Sale	1.94:1	3.0:1	#000000	#4F3739	Fail
h2 FAQ'S	1.94:1	3.0:1	#000000	#4F3739	Fail
h2 You're Eligible	1.94:1	3.0:1	#000000	#4F3739	Fail
h3 Quick Search:	1.94:1	3.0:1	#000000	#4F3739	Fail
h3 THE PERFECT FIT	1.94:1	3.0:1	#000000	#4F3739	Fail
h3 NEXT DAY DISPATCH AV…	1.94:1	3.0:1	#000000	#4F3739	Fail
h3 5 YEAR WARRANTY	1.94:1	3.0:1	#000000	#4F3739	Fail
h3 4.5/5 STARS	1.94:1	3.0:1	#000000	#4F3739	Fail
h3 Professional Install…	1.94:1	3.0:1	#000000	#4F3739	Fail
h3 Good News!	1.94:1	3.0:1	#000000	#4F3739	Fail
h3 Sorry, Not Available	1.94:1	3.0:1	#000000	#4F3739	Fail
h3 You're Eligible	1.94:1	3.0:1	#000000	#4F3739	Fail
h3 How It Works	1.94:1	3.0:1	#000000	#4F3739	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

5 landmarks

PASS

5 landmarks

<main> landmark present

2 <nav> landmark(s) found

1 of 2 <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 Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

10 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: 10 all-caps heading(s)

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="search" name="q">

1 controls

0 labeled

1 placeholder only

0 unlabeled

Control	Type	Label	Method
q	search	(Search for items)	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

A+

Link & Button Quality

47 links, 18 buttons — all OK

PASS

47 links, 18 buttons — all OK

47 link(s) with descriptive text

47 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

65 links and buttons have descriptive text

A+

Form Input Types

1 form control(s) checked, no type mismatches

PASS

1 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

1 form control(s) checked, no input-semantic issues

PASS

1 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

No autofill-eligible form controls (no name/email/tel/address fields)

A+

Document Language

Lang attribute set to "en"

PASS

Lang attribute set to "en"

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

Got: en

A+

Tabindex Anti-Patterns

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

PASS

4 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+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

2 mobile-depth signal(s) detected

PASS

2 mobile-depth signal(s) detected

Browser-chrome `theme-color` meta tag present

The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.

iOS auto-link for phone numbers disabled (`format-detection: telephone=no`)

The page sets `<meta name="format-detection" content="telephone=no">`, which prevents iOS Safari from auto-converting phone-number-shaped strings into clickable `tel:` links. Common reason: the auto-detection rewrites mid-paragraph DOM and breaks CSS selectors / JS that depended on the specific text. If you want clickable phone numbers, declare them with explicit `<a href="tel:+1234567890">` and keep auto-detection disabled.

Lighthouse Accessibility Audits

Score 90/100 — 3 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.

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
Limited Stock – Today Only `div#sales-banner-section-template--28480353861978__homepage_sales_banner_w9aNJ9 > div.sales-banner-container > div.sales-panel > p.sales-panel__stock-info`

These are opportunities to improve the legibility of your content.

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
INFORMATION `div.fw-sec > div.grid > div.gitem > h4.h4`

These are opportunities to improve keyboard navigation in your application.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.text > div > div > img `div.text > div > div > img`

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

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

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

●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

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

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○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

○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

○Identical links have the same purpose.

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