Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

12 PASS 5 REVIEW 7 FIX

Alt Text Quality

Action

14 of 573 images have issues

FIX

14 of 573 images have issues

14 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

3 image-in-link without alt text

An image inside a link with no alt creates an empty link.

559 image(s) with good alt text

573 images 559 good alt text 14 missing

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

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

Link & Button Quality

Action

7 issue(s) across 699 links and 56 buttons

FIX

7 issue(s) across 699 links and 56 buttons

1 link(s) with no accessible text

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

Got: a.swatch__link (#4774 on page)

1 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: /pages/about-us-1 ("Learn more")

4 link(s) open in new tab without warning

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

Got: https://instagram.com/essethelabel; https://facebook.com/essethelabel; https://tiktok.com/essethelabel; https://www.shopify.com?utm_campaign=poweredby&utm_medium=shopify&utm_source=…

5 button(s) with no accessible text

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

Got: button.search-popdown__close__button (#199 on page); button.search-popdown__close__button (#417 on page); button.search-popdown__close__button (#839 on page); button.close (#2167 on page); button.pswp__button (#4787 on page)

693 link(s) with descriptive text

699 links

1 empty

1 generic text

4 new tab

5 empty buttons

Element	Text	Issue	Suggested Fix
/collections/honed	@media (min-width: 750px) { …	img no alt	Add alt attribute to the image
/collections/new-colours-edit	@media (min-width: 750px) { …	img no alt	Add alt attribute to the image
/collections/knitwear-essentials	@media (min-width: 750px) { …	img no alt	Add alt attribute to the image
/pages/about-us-1	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: About Us 1
https://instagram.com/essethelabel	Instagram	new tab	Add '(opens in new tab)' to text
https://facebook.com/essethelabel	Facebook	new tab	Add '(opens in new tab)' to text
https://tiktok.com/essethelabel	TikTok	new tab	Add '(opens in new tab)' to text
https://www.shopify.com?utm_campaign=pow…	Powered by Shopify	new tab	Add '(opens in new tab)' to text
	(empty)	empty	Add link 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

744 links and buttons have descriptive text

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

a.swatch__link (#4774 on page)

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

Generic link text like 'click here' doesn't describe the destination.

/pages/about-us-1 ("Learn more")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

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

https://instagram.com/essethelabel; https://facebook.com/essethelabel; https://tiktok.com/essethelabel; 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

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

button.search-popdown__close__button (#199 on page); button.search-popdown__close__button (#417 on page); button.search-popdown__close__button (#839 on page); button.close (#2167 on page); button.pswp__button (#4787 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

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

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

Action

29 headings, 1 skip(s)

REVIEW

29 headings, 1 skip(s)

No H1 heading found

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

Heading level skipped: H3 → H5 (missing H4)

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

H2 Shop our best-sellers
H2 Shop our best-sellers
H2 Currency
H3 Cart 0
H5 Sorry, looks like we don't have enough of this product. skipped
H2 Get 10% off your first order
H2 Honed
H2 Becoming
H2 Refreshed and refined
H2 A signature: now in Japanese Cotton Seersucker
H2 Your Steadiest Layers
H2 For all of life's moments: enduring essentials, made only from natural and plant-based fibres.
H3 Everyday Ease
H3 Work Friendly
H3 Travel Ready
H3 Day to Night Ready
H3 Bump to Baby
H2 Best Sellers
H2 Made for the modern woman, by women.
H2 Our commitment to you and our planet
H2 Sustainable fibres only
H2 Ethically-made, high quality craftsmanship
H2 Designed for longevity
H2 B-Corp Certified
H2 100% Natural
H2 Hand-crafted with love
H2 Lifetime Repairs
H2 Sign up for 10% off your first purchase.
H2 Currency

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

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

Mobile-Readable Font Sizes

Action

77% of visible text renders at >= 12 CSS px (5 below threshold)

REVIEW

77% of visible text renders at >= 12 CSS px (5 below threshold)

5 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: <p> 10.6px ("The Esse archive is open."); <strong> 10.6px ("Shop now→"); <p> 10.6px ("Our new capsule, Honed, has arrived. Rec..."); <p> 10.6px ("Enjoy free local shipping when you spend..."); <span> 0.0px ("Cart").

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 – Esse ✓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

h2 Shop our best-sellers

1.91:1

#000000

#3A3D3D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Shop our best-sellers

1.91:1

#000000

#3A3D3D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Currency

1.91:1

#000000

#3A3D3D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Get 10% off your first order

1.91:1

#000000

#3A3D3D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Honed

1.91:1

#000000

#3A3D3D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Becoming

1.91:1

#000000

#3A3D3D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Refreshed and refined

1.91:1

#000000

#3A3D3D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 A signature: now in Japanese Cotton Seer…

1.91:1

#000000

#3A3D3D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Your Steadiest Layers

1.91:1

#000000

#3A3D3D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 For all of life's moments: enduring esse…

1.91:1

#000000

#3A3D3D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Best Sellers

1.91:1

#000000

#3A3D3D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Made for the modern woman, by women.

1.91:1

#000000

#3A3D3D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Our commitment to you and our planet

1.91:1

#000000

#3A3D3D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Sustainable fibres only

1.91:1

#000000

#3A3D3D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Ethically-made, high quality craftsmansh…

1.91:1

#000000

#3A3D3D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Designed for longevity

1.91:1

#000000

#3A3D3D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 B-Corp Certified

1.91:1

#000000

#3A3D3D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 100% Natural

1.91:1

#000000

#3A3D3D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Hand-crafted with love

1.91:1

#000000

#3A3D3D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Lifetime Repairs

1.91:1

#000000

#3A3D3D

needs 3.0:1 (large text)

24px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Shop our best-seller…	1.91:1	3.0:1	#000000	#3A3D3D	Fail
h2 Shop our best-seller…	1.91:1	3.0:1	#000000	#3A3D3D	Fail
h2 Currency	1.91:1	3.0:1	#000000	#3A3D3D	Fail
h2 Get 10% off your fir…	1.91:1	3.0:1	#000000	#3A3D3D	Fail
h2 Honed	1.91:1	3.0:1	#000000	#3A3D3D	Fail
h2 Becoming	1.91:1	3.0:1	#000000	#3A3D3D	Fail
h2 Refreshed and refine…	1.91:1	3.0:1	#000000	#3A3D3D	Fail
h2 A signature: now in …	1.91:1	3.0:1	#000000	#3A3D3D	Fail
h2 Your Steadiest Layer…	1.91:1	3.0:1	#000000	#3A3D3D	Fail
h2 For all of life's mo…	1.91:1	3.0:1	#000000	#3A3D3D	Fail
h2 Best Sellers	1.91:1	3.0:1	#000000	#3A3D3D	Fail
h2 Made for the modern …	1.91:1	3.0:1	#000000	#3A3D3D	Fail
h2 Our commitment to yo…	1.91:1	3.0:1	#000000	#3A3D3D	Fail
h2 Sustainable fibres o…	1.91:1	3.0:1	#000000	#3A3D3D	Fail
h2 Ethically-made, high…	1.91:1	3.0:1	#000000	#3A3D3D	Fail
h2 Designed for longevi…	1.91:1	3.0:1	#000000	#3A3D3D	Fail
h2 B-Corp Certified	1.91:1	3.0:1	#000000	#3A3D3D	Fail
h2 100% Natural	1.91:1	3.0:1	#000000	#3A3D3D	Fail
h2 Hand-crafted with lo…	1.91:1	3.0:1	#000000	#3A3D3D	Fail
h2 Lifetime Repairs	1.91:1	3.0:1	#000000	#3A3D3D	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.

Lighthouse Accessibility Audits

Score 84/100 — 4 failing, 24 passed

REVIEW

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

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Menu `div.header-sections > div#shopify-section-sections--19732063518895__header > header-component.header__wrapper > header-drawer#header-menu`
Menu `div.header-sections > div#shopify-section-sections--19732063518895__mobile-menu > mobile-menu.mobile-menu > header-drawer#mobile-menu-sections--19732063518895__mobile-menu`

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.

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
Best-selling silhouette 8 years in a row `div.product-item__info > a.product-link > div.product-item__price__holder > span.product-item__cutline`
€170,95 `div.product-item__price__holder > div.product-item__price > span.price > span.new-price`

These are opportunities to improve the legibility of your content.

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.image__hero__pane > div.image__hero__scale > picture#Picture-0d22e8444dc014f46ae19f6441768158 > img.is-loading `div.image__hero__pane > div.image__hero__scale > picture#Picture-0d22e8444dc014f46ae19f6441768158 > img.is-loading`
div.image__hero__pane > div.image__hero__scale > picture#Picture-cf0355a29524f935939451f6a425c1ad > img.is-loading `div.image__hero__pane > div.image__hero__scale > picture#Picture-cf0355a29524f935939451f6a425c1ad > img.is-loading`
div.image__hero__pane > div.image__hero__scale > picture#Picture-d312fa79cdc99604573939fc8b307845 > img.is-loading `div.image__hero__pane > div.image__hero__scale > picture#Picture-d312fa79cdc99604573939fc8b307845 > img.is-loading`
div.image__hero__pane > div.image__hero__scale > picture#Picture-8c893d71a644e77d6fb09908502391e4 > img.is-loading `div.image__hero__pane > div.image__hero__scale > picture#Picture-8c893d71a644e77d6fb09908502391e4 > img.is-loading`
div.image__hero__pane > div.image__hero__scale > picture#Picture-529bac130e9c87b95e2338a9fd3a83bf > img.is-loading `div.image__hero__pane > div.image__hero__scale > picture#Picture-529bac130e9c87b95e2338a9fd3a83bf > img.is-loading`
div.review > div.review__image > figure.image-wrapper > img.fit-cover `div.review > div.review__image > figure.image-wrapper > img.fit-cover`
div.review > div.review__image > figure.image-wrapper > img.fit-cover `div.review > div.review__image > figure.image-wrapper > img.fit-cover`
div.review > div.review__image > figure.image-wrapper > img.fit-cover `div.review > div.review__image > figure.image-wrapper > img.fit-cover`
div.timeline__image > div.timeline__image-inner > figure.timeline__image-figure > img.is-loading `div.timeline__image > div.timeline__image-inner > figure.timeline__image-figure > img.is-loading`
div.timeline__image > div.timeline__image-inner > figure.timeline__image-figure > img.is-loading `div.timeline__image > div.timeline__image-inner > figure.timeline__image-figure > img.is-loading`
div.timeline__image > div.timeline__image-inner > figure.timeline__image-figure > img.is-loading `div.timeline__image > div.timeline__image-inner > figure.timeline__image-figure > img.is-loading`

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.wrapper--full > slider-component#template--19732071809199__slideshow-nested > div.slideshow__slide > a.hero__image `div.wrapper--full > slider-component#template--19732071809199__slideshow-nested > div.slideshow__slide > a.hero__image`
div.wrapper--full > slider-component#template--19732071809199__slideshow-nested > div.slideshow__slide > a.hero__image `div.wrapper--full > slider-component#template--19732071809199__slideshow-nested > div.slideshow__slide > a.hero__image`
div.wrapper--full > slider-component#template--19732071809199__slideshow-nested > div.slideshow__slide > a.hero__image `div.wrapper--full > slider-component#template--19732071809199__slideshow-nested > div.slideshow__slide > a.hero__image`

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.

●ARIA attributes are used as specified for the element's role

●`[aria-hidden="true"]` elements do not contain focusable descendents

●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

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

●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

●ARIA IDs are unique

●Identical links have the same purpose.

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

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

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

Landmark Structure

10 landmarks

PASS

10 landmarks

<main> landmark present

4 <nav> landmark(s) found

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

All 29 heading(s) have substantive, well-formed text

PASS

All 29 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A+

Form Accessibility

All 7 controls labeled

PASS

All 7 controls labeled

7 control(s) properly labeled

7 controls

7 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#SearchInput--mobile	search	Search our store	aria-label
#SearchInput--desktop	search	Search our store	aria-label
#SearchInput--mobile--sections--19732063518895__mobile-menu	search	Search our store	aria-label
#note	textarea	Leave a note about your order	aria-label
#email-input-large_newsletter_yKbcTJ	email	Email	aria-label
contact[first_name]	text	Name	aria-label
#email-input-footer-0	email	Email	aria-label

A+

Form Input Types

7 form control(s) checked, no type mismatches

PASS

7 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

7 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

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

PASS

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

No tabindex anti-patterns detected

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

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

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.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.