Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

17 PASS 1 REVIEW 6 FIX

Tap Target Adequacy

Action

11 tap target(s) too small or too close together

FIX

11 tap target(s) too small or too close together

11 tap target(s) too small or too close to neighbors

WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.

Favicon & Branding

Action

1 icon(s) detected

FIX

1 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'>.

✗ favicon.ico Missing

✓ PNG Icons Present

✗ Apple Touch Missing

✗ 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: #1e0c0c

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 ✗

Color Contrast (Screenshot)

Action

20 text elements analyzed, 3 fail WCAG AA

REVIEW

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

17 pass 3 fail WCAG AA 1 pass AA only

title Main Street Home | Vintage, Antique, New…

2.82:1

#000000

#555555

needs 4.5:1 (normal text)

16px · top of page (header area)

a Skip to content

2.82:1

#000000

#555555

needs 4.5:1 (normal text)

16px · top of page (header area)

span Submit

3.45:1

#000000

#5D6368

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Just added to your c…	7.16:1	3.0:1	#000000	#94979B	Pass
h2 GET TO KNOW US	19.77:1	3.0:1	#000000	#F8F8F8	Pass
h2 Newest Arrivals	19.77:1	3.0:1	#000000	#F8F8F8	Pass
h2 Testimonials	19.77:1	3.0:1	#000000	#F8F8F8	Pass
title Main Street Home \| V…	2.82:1	4.5:1	#000000	#555555	Fail
a Skip to content	2.82:1	4.5:1	#000000	#555555	Fail
span Qty:	15.93:1	4.5:1	#000000	#DCE1E4	Pass
a View cart (	17.31:1	4.5:1	#000000	#E3EAF1	Pass
button Continue shopping	12.51:1	4.5:1	#000000	#C0C9D0	Pass
span Submit	3.45:1	4.5:1	#000000	#5D6368	Fail
span Close search	9.21:1	4.5:1	#000000	#9DAEBB	Pass
p Tuesday-Friday 9-5, …	6.14:1	4.5:1	#000000	#7B8D9D	Pass
span Search	11.05:1	4.5:1	#000000	#B0BEC8	Pass
span Log in	14.18:1	4.5:1	#000000	#D0D5D7	Pass
span Cart	15.84:1	4.5:1	#000000	#DEE0E0	Pass
span items	19.77:1	4.5:1	#000000	#F8F8F8	Pass
span Shop Online	19.77:1	4.5:1	#000000	#F8F8F8	Pass
span Consign	19.77:1	4.5:1	#000000	#F8F8F8	Pass
span Visit Our Showroom	19.77:1	4.5:1	#000000	#F8F8F8	Pass
span Estate Jewerly & Coi…	19.77:1	4.5:1	#000000	#F8F8F8	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.

Landmark Structure

6 landmarks

PASS

6 landmarks

<main> landmark present

2 <nav> landmark(s) found

2 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 Hierarchy

10 headings

PASS

10 headings

Single H1 present

1 empty heading(s)

Empty headings appear in the document outline but provide no information.

H2 Just added to your cart
H3 (empty)
H1 .item-1{ display:true; white-space: nowrap; } @media(max-width:1600px){ .item-1{ display:none; }
H2 GET TO KNOW US
H2 About
H2 Contact
H2 Consign
H2 Shop
H2 Newest Arrivals
H2 Testimonials

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

Heading Text Quality

2 heading-text-quality issue(s) detected

PASS

2 heading-text-quality issue(s) detected

1 heading(s) are over 120 characters -- likely a misformatted paragraph

Headings beyond 120 characters are almost always full sentences or paragraphs that received heading semantics by mistake (e.g., a CMS editor selected the wrong block type, or a template wrapped a body paragraph in `<h2>`). Screen readers will announce these as "heading" and read the entire paragraph at heading prosody. Affected: - H1: 190 chars

Got: 1 >120-char heading(s)

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

A+

Alt Text Quality

All 10 images OK

PASS

All 10 images OK

9 decorative image(s) correctly marked

1 image(s) with good alt text

10 images 1 good alt text 9 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 2 controls labeled

PASS

All 2 controls labeled

2 control(s) properly labeled

2 controls

2 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
q	text	Search	aria-label
#ContactFooter-email	email	Email address	aria-label

A+

Link & Button Quality

44 links, 18 buttons — all OK

PASS

44 links, 18 buttons — all OK

1 link(s) open in new tab without warning

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

Got: https://www.shopify.com?utm_campaign=poweredby&utm_medium=shopify&utm_source=…

43 link(s) with descriptive text

44 links

0 empty

0 generic text

1 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.shopify.com?utm_campaign=pow…	Powered by Shopify	new tab	Add '(opens in new tab)' to text

61 links and buttons have descriptive text

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

https://www.shopify.com?utm_campaign=poweredby&utm_medium=shopify&utm_source=…

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+

Form Input Types

1 input(s) using type=text where a specific type would help

PASS

1 input(s) using type=text where a specific type would help

Input "q" should use type="search" (currently type="text")

Field name "q" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.

A+

Form Input Quality

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

PASS

2 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

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

PASS

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

No tabindex anti-patterns detected

Iframe Accessibility

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

PASS

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

A+

Mobile-Readable Font Sizes

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

PASS

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

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

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 404 Not Found – Main Street Estate Sales ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

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

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.

Lighthouse Accessibility Audits

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

ARIA

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Load slide 1 `div.slideshow__text-wrap > div.slideshow__arrows > ul.slick-dots > li.slick-active`
Load slide 1 `div.page-width > div.quotes-wrapper > ul.slick-dots > li.slick-active`

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.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Load slide 1 `div.slideshow__arrows > ul.slick-dots > li.slick-active > a`
Load slide 2 `div.slideshow__arrows > ul.slick-dots > li > a`
Load slide 3 `div.slideshow__arrows > ul.slick-dots > li > a`
Load slide 4 `div.slideshow__arrows > ul.slick-dots > li > a`
Load slide 1 `div.quotes-wrapper > ul.slick-dots > li.slick-active > button#slickDot16039045871ee288f2-0`
Load slide 2 `div.quotes-wrapper > ul.slick-dots > li > button#slickDotd8e829d2-b372-482b-84c5-5fa2666ac041`
Load slide 3 `div.quotes-wrapper > ul.slick-dots > li > button#slickDot4d75e921-e705-4f6d-a87c-ec733cb2a088`
Load slide 4 `div.quotes-wrapper > ul.slick-dots > li > button#slickDotaf208cb5-4008-40d9-932d-ee5c9f0b9fc0`
Load slide 5 `div.quotes-wrapper > ul.slick-dots > li > button#slickDotcf8a1084-dcc7-439b-a193-170f7a69137a`
Load slide 6 `div.quotes-wrapper > ul.slick-dots > li > button#slickDot4cd73d8e-1d92-452a-af8f-dc439eb28547`
Load slide 7 `div.quotes-wrapper > ul.slick-dots > li > button#slickDotf650a637-8159-4e9a-828c-b09edcb6f7b1`

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

●Background and foreground colors have a sufficient contrast ratio

●`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

●Definition list items are wrapped in `<dl>` elements

●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

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

●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

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

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