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 3 REVIEW 7 FIX

Mobile Keyboard & Autofill

Action

3/4 eligible field(s) missing autocomplete or inputmode

FIX

3/4 eligible field(s) missing autocomplete or inputmode

3 field(s) would benefit from inputmode attribute

Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: search, email.

Got: <input type="search" name="q" id="Search-In-Modal-1">, <input type="search" name="q" id="Search-In-Modal">, <input type="email" name="email" id="NewsletterForm--footer">

404 Error Page

Action

HTTP 403, custom page

FIX

HTTP 403, custom page

Unexpected status code: HTTP 403

Expected HTTP 404 but received 403. This may confuse search engine crawlers.

Got: HTTP 403

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 403 ✗Page Title Verifying your connection... ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

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.

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

72 headings, 1 skip(s)

REVIEW

72 headings, 1 skip(s)

Single H1 present

Heading level skipped: H2 → H6 (missing H3)

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

1 empty heading(s)

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

H2 Your cart is empty
H2 Your cart
H2 Subtotal
H1 (empty)
H2 Fashion In. Cash Out.
H2 Top Departments
H3 Handbags
H3 Handbags
H3 Sandals
H3 Sandals
H3 Dresses
H3 Dresses
H3 Tops
H3 Tops
H3 Plus
H3 Plus
H3 Accessories
H3 Accessories
H3 Athletic Wear
H3 Athletic Wear
H3 Bottoms
H3 Bottoms
H3 Outerwear
H3 Outerwear
H3 Designer Handbags
H3 Designer Handbags
H2 Blog posts
H3 10.10 | 20% Off Handbags
H3 10.10 | 20% Off Handbags
H3 9.26 | Girl's Night Out
H3 9.26 | Girl's Night Out
H2 New Arrivals Daily
H3 Top Long Sleeve By Talbots In Cream, Size: S
H3 Top Long Sleeve By Talbots In Cream, Size: S
H3 Sweater Cashmere By Charter Club In Purple, Size: S
H3 Sweater Cashmere By Charter Club In Purple, Size: S
H3 Jacket Leather By Walter Baker In Black, Size: M
H3 Jacket Leather By Walter Baker In Black, Size: M
H3 Jacket Leather By Walter Baker In Black, Size: M
H3 Jacket Leather By Walter Baker In Black, Size: M
H3 Sweater By Ralph Lauren In Green, Size: M
H3 Sweater By Ralph Lauren In Green, Size: M
H3 Sweater By Ralph Lauren In Yellow, Size: M
H3 Sweater By Ralph Lauren In Yellow, Size: M
H3 Sweater By Ralph Lauren In Pink, Size: M
H3 Sweater By Ralph Lauren In Pink, Size: M
H3 Jacket Windbreaker By Columbia In Green, Size: M
H3 Jacket Windbreaker By Columbia In Green, Size: M
H2 SELL TO US
H2 Designer Handbags
H3 Coin Purse Designer By Kate Spade, Size: Small
H3 Coin Purse Designer By Kate Spade, Size: Small
H3 Wallet Designer By Spartina, Size: Small
H3 Wallet Designer By Spartina, Size: Small
H3 Wristlet Luxury Designer By Louis Vuitton, Size: Large
H3 Wristlet Luxury Designer By Louis Vuitton, Size: Large
H3 Handbag Designer By Coach, Size: Large
H3 Handbag Designer By Coach, Size: Large
H2 Tops
H3 Top Long Sleeve By Talbots In Cream, Size: S
H3 Top Long Sleeve By Talbots In Cream, Size: S
H3 Sweater Cashmere By Charter Club In Purple, Size: S
H3 Sweater Cashmere By Charter Club In Purple, Size: S
H3 Sweater By Ralph Lauren In Green, Size: M
H3 Sweater By Ralph Lauren In Green, Size: M
H3 Sweater By Ralph Lauren In Yellow, Size: M
H3 Sweater By Ralph Lauren In Yellow, Size: M
H2 SHOP WITH US
H2 Brands we love
H2 VISIT US IN SYLVANIA
H6 Our products are available online and at our local, independently owned Clothes Mentor stores. Our store teams do their best to accurately photograph, describe, and account for the unique inventory sh skipped
H2 Quick links

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

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

Mobile-Readable Font Sizes

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

REVIEW

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

1 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: <time> 10.0px ("October 5, 2026").

Color Contrast (Screenshot)

Action

20 text elements analyzed, 2 fail WCAG AA

REVIEW

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

18 pass 2 fail WCAG AA 1 pass AA only

title Clothes Mentor Online Shopping - Sylvani…

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

a Skip to content

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Your cart is empty	5.61:1	3.0:1	#000000	#00929F	Pass
h2 Your cart	4.20:1	3.0:1	#000000	#836B55	Pass
h2 Subtotal	14.50:1	3.0:1	#000000	#D9D6D2	Pass
h2 Fashion In. Cash Out…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Top Departments	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Blog posts	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 New Arrivals Daily	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 SELL TO US	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Designer Handbags	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Tops	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 SHOP WITH US	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Brands we love	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Quick links	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Clothes Mentor Onlin…	1.00:1	4.5:1	#000000	#000000	Fail
a Skip to content	1.00:1	4.5:1	#000000	#000000	Fail
a Continue shopping	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p Have an account?	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Log in	11.93:1	4.5:1	#000000	#D4C0AC	Pass
p to check out faster.	8.48:1	4.5:1	#000000	#BCA080	Pass
p Log in to check for …	7.88:1	4.5:1	#000000	#AC9C8B	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

8 landmarks

PASS

8 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

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: - H6: 200 chars

Got: 1 >120-char heading(s)

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

Alt Text Quality

All 42 images OK

PASS

All 42 images OK

4 image(s) with alt text over 125 characters

18 decorative image(s) correctly marked

20 image(s) with good alt text

42 images 20 good alt text 18 decorative

Issue	Count
too long	4 image(s)

A+

Form Accessibility

All 4 controls labeled

PASS

All 4 controls labeled

4 control(s) properly labeled

4 controls

4 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#agree	checkbox	I have read and understand the store return policy.	for/id
#Search-In-Modal-1	search	Search	for/id
#Search-In-Modal	search	Search	for/id
#NewsletterForm--footer	email	Email	for/id

Link & Button Quality

217 links, 35 buttons — all OK

PASS

217 links, 35 buttons — all OK

2 link(s) open in new tab without warning

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

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

215 link(s) with descriptive text

217 links

0 empty

0 generic text

2 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://onelink.to/cjhbkr	Download Clothes Mentor App	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

250 links and buttons have descriptive text

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

https://onelink.to/cjhbkr; 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

4 form control(s) checked, no type mismatches

PASS

4 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

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

All form input semantics look correct

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

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

PASS

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

A+

Lighthouse Accessibility Audits

Score 95/100 — 2 failing, 27 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
WE'RE HIRING! APPLY TODAY! `div#shopify-section-announcement-bar > div.announcement-bar > a.announcement-bar__link > p.announcement-bar__message`

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
Our products are available online and at our local, independently owned Clothes… `div.rich-text__wrapper > div.rich-text__blocks > div.rich-text__text > h6`

These are opportunities to improve keyboard navigation in your application.

○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

●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

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

●Elements with the `role=text` attribute do not have focusable descendents.

●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

●Touch targets have sufficient size and spacing.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

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

○`[role]`s are contained by their required parent element

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

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

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