Skip to content
https://suzushiiclothing.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
74
GRADE
C
FIX
7
REVIEW
6
PASS
11
INFO
0
Checks
24
11 PASS 6 REVIEW 7 FIX
F
Alt Text Quality
Action
12 of 975 images have issues
FIX
12 of 975 images have issues
Critical::
12 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
12 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
10 decorative image(s) correctly marked
Info::
953 image(s) with good alt text
975 images 953 good alt text 10 decorative 12 missing
IssueCount
missing12 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

F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
D
Web Manifest
Action
Not found
FIX
Not found
Info::
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.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
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.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
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 ✗
F
Navigation UX
Action
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
2 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 2 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Form Accessibility
4 of 121 controls have issues
REVIEW
4 of 121 controls have issues
Warning::
4 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input id="ab-regular-price-input">; <input id="ab-sale-price-input">; <input id="ab-compare-at-price-input">; <input id="ab-save-badge-input">
Info::
117 control(s) properly labeled
121 controls
117 labeled
4 placeholder only
0 unlabeled
ControlTypeLabelMethod
qsearchSearcharia-label
option1radioSnone
option1radioMnone
option1radioLnone
option1radioXLnone
option1radio2XLnone
option1radio3XLnone
option2radionone
option2radionone
option2radionone
option2radionone
option1radioSnone
option1radioMnone
option1radioLnone
option1radioXLnone
option1radio2XLnone
option1radio3XLnone
option2radionone
option2radionone
option2radionone
option1radioSnone
option1radioMnone
option1radioLnone
option1radioXLnone
option1radio2XLnone
option1radio3XLnone
option2radionone
option2radionone
option2radionone
option2radionone
option1radioSnone
option1radioMnone
option1radioLnone
option1radioXLnone
option1radio2XLnone
option1radio3XLnone
option2radionone
option2radionone
option2radionone
option1radioSnone
option1radioMnone
option1radioLnone
option1radioXLnone
option1radio2XLnone
option1radio3XLnone
option2radionone
option2radionone
option2radionone
option1radioSnone
option1radioMnone
option1radioLnone
option1radioXLnone
option1radio2XLnone
option1radio3XLnone
option2radionone
option2radionone
option2radionone
option2radionone
option1radioSnone
option1radioMnone
option1radioLnone
option1radioXLnone
option1radio2XLnone
option1radio3XLnone
option2radionone
option2radionone
option2radionone
option1radioSnone
option1radioMnone
option1radioLnone
option1radioXLnone
option1radio2XLnone
option1radio3XLnone
option2radionone
option2radionone
option2radionone
option1radioSnone
option1radioMnone
option1radioLnone
option1radioXLnone
option1radio2XLnone
option1radio3XLnone
option2radionone
option2radionone
option2radionone
option2radionone
option1radioSnone
option1radioMnone
option1radioLnone
option1radioXLnone
option1radio2XLnone
option1radio3XLnone
option2radionone
option2radionone
option2radionone
option2radionone
option1radioSnone
option1radioMnone
option1radioLnone
option1radioXLnone
option1radio2XLnone
option1radio3XLnone
option2radionone
option2radionone
option2radionone
option2radionone
option1radioSnone
option1radioMnone
option1radioLnone
option1radioXLnone
option1radio2XLnone
option1radio3XLnone
option2radionone
option2radionone
option2radionone
option2radionone
#input--sections--22082557968619__footer--contactemailemailE-mailfor/id
#ab-sale-price-inputinput(.price--sale)placeholder only
#ab-compare-at-price-inputinput(.price--compare)placeholder only
#ab-save-badge-inputinput(.price-badge, .badge--sale)placeholder only
#ab-regular-price-inputinput(.price .money)placeholder only

Placeholder text disappears on focus and is not a reliable label.

<input id="ab-regular-price-input">; <input id="ab-sale-price-input">; <input id="ab-compare-at-price-input">; <input id="ab-save-badge-input">

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

B
Iframe Accessibility
2/3 iframe(s) missing title; 0 placeholder(s)
REVIEW
2/3 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="https://suzushiiclothing.com/web-pixels@05c62d7ewbe538af9pdeb4fec1me339d55a/cus…")
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.
Warning::
<iframe> missing title attribute (src="https://suzushiiclothing.com/web-pixels@05c62d7ewbe538af9pdeb4fec1me339d55a/cus…")
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.
C
Tap Target Adequacy
Action
7 tap target(s) too small or too close together
REVIEW
7 tap target(s) too small or too close together
Warning::
7 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.
C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 Not Found ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
C
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
title Suzushii Clothing: Japanese Inspired Tee…
1.11:1
#000000
on
#111111
needs 4.5:1 (normal text)
16px · top of page (header area)
div Highlight Modifications
1.11:1
#000000
on
#111111
needs 4.5:1 (normal text)
16px · top of page (header area)
button Exit
4.24:1
#000000
on
#707070
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
button Copy
3.08:1
#000000
on
#5F5A56
needs 4.5:1 (normal text)
16px · above the fold
label Compare At
2.44:1
#000000
on
#4D4C48
needs 4.5:1 (normal text)
16px · above the fold
button Copy
1.18:1
#000000
on
#171816
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
label Save Badge
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · above the fold
span 0 matches
3.66:1
#000000
on
#666666
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient

3 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)
ElementRatioRequiredFGBGResult
h2 Best Sellers21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Popular collections21.00:13.0:1
#000000
#FFFFFF
Pass
h2 What people are sayi…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Follow us on social21.00:13.0:1
#000000
#FFFFFF
Pass
title Suzushii Clothing: J…1.11:14.5:1
#000000
#111111
Fail
div Highlight Modificati…1.11:14.5:1
#000000
#111111
Fail
button Exit4.24:14.5:1
#000000
#707070
Fail
label Regular Price21.00:14.5:1
#000000
#FFFFFF
Pass
button Copy21.00:14.5:1
#000000
#FFFFFF
Pass
label Sale Price7.60:14.5:1
#000000
#9E9B99
Pass
button Copy3.08:14.5:1
#000000
#5F5A56
Fail
label Compare At2.44:14.5:1
#000000
#4D4C48
Fail
button Copy1.18:14.5:1
#000000
#171816
Fail
label Save Badge1.00:14.5:1
#000000
#000000
Fail
button Copy21.00:14.5:1
#000000
#FFFFFF
Pass
span 0 matches3.66:14.5:1
#000000
#666666
Fail
span 0 matches21.00:14.5:1
#000000
#FFFFFF
Pass
span 0 matches21.00:14.5:1
#000000
#FFFFFF
Pass
span 0 matches21.00:14.5:1
#000000
#FFFFFF
Pass
button Save21.00:14.5:1
#000000
#FFFFFF
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.

B
Lighthouse Accessibility Audits
Score 89/100 — 3 failing, 26 passed
REVIEW
89

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
product-list.product-list > product-card.product-card > div.product-card__figure > button.pmd-quickview-button product-list.product-list > product-card.product-card > div.product-card__figure > button.pmd-quickview-button
product-list.product-list > product-card.product-card > div.product-card__figure > button.pmd-quickview-button product-list.product-list > product-card.product-card > div.product-card__figure > button.pmd-quickview-button
product-list.product-list > product-card.product-card > div.product-card__figure > button.pmd-quickview-button product-list.product-list > product-card.product-card > div.product-card__figure > button.pmd-quickview-button
product-list.product-list > product-card.product-card > div.product-card__figure > button.pmd-quickview-button product-list.product-list > product-card.product-card > div.product-card__figure > button.pmd-quickview-button
product-list.product-list > product-card.product-card > div.product-card__figure > button.pmd-quickview-button product-list.product-list > product-card.product-card > div.product-card__figure > button.pmd-quickview-button
product-list.product-list > product-card.product-card > div.product-card__figure > button.pmd-quickview-button product-list.product-list > product-card.product-card > div.product-card__figure > button.pmd-quickview-button
product-list.product-list > product-card.product-card > div.product-card__figure > button.pmd-quickview-button product-list.product-list > product-card.product-card > div.product-card__figure > button.pmd-quickview-button
product-list.product-list > product-card.product-card > div.product-card__figure > button.pmd-quickview-button product-list.product-list > product-card.product-card > div.product-card__figure > button.pmd-quickview-button
product-list.product-list > product-card.product-card > div.product-card__figure > button.pmd-quickview-button product-list.product-list > product-card.product-card > div.product-card__figure > button.pmd-quickview-button
product-list.product-list > product-card.product-card > div.product-card__figure > button.pmd-quickview-button product-list.product-list > product-card.product-card > div.product-card__figure > button.pmd-quickview-button
product-list.product-list > product-card.product-card > div.product-card__figure > button.pmd-quickview-button product-list.product-list > product-card.product-card > div.product-card__figure > button.pmd-quickview-button
product-list.product-list > product-card.product-card > div.product-card__figure > button.pmd-quickview-button product-list.product-list > product-card.product-card > div.product-card__figure > button.pmd-quickview-button

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
main#main > section#shopify-section-template--22082558755051__slideshow_CtqFgE > slideshow-carousel#carousel-template--22082558755051__slideshow_CtqFgE > a.slideshow__slide main#main > section#shopify-section-template--22082558755051__slideshow_CtqFgE > slideshow-carousel#carousel-template--22082558755051__slideshow_CtqFgE > a.slideshow__slide
div.footer__inner > div.footer__aside > p.heading > a div.footer__inner > div.footer__aside > p.heading > 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.

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
View collection a.collection-card > div.content-over-media > div.collection-card__content > button.link
View collection a.collection-card > div.content-over-media > div.collection-card__content > button.link
View collection a.collection-card > div.content-over-media > div.collection-card__content > button.link
Go to item 1 div.section-stack > div.testimonial-list > carousel-navigation.page-dots > button.tap-area
Go to item 2 div.section-stack > div.testimonial-list > carousel-navigation.page-dots > button.tap-area
Go to item 3 div.section-stack > div.testimonial-list > carousel-navigation.page-dots > button.tap-area
Go to item 4 div.section-stack > div.testimonial-list > carousel-navigation.page-dots > button.tap-area

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-*]` 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
●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.
●`button`, `link`, and `menuitem` elements have accessible names
●ARIA attributes are used as specified for the element's role
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●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
●Uses ARIA roles only on compatible elements
○`[accesskey]` values are unique
○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
○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.
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○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.
○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.
A+
Landmark Structure
12 landmarks
PASS
12 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Primary navigation" MAIN CONTENTINFO footer
A+
Heading Hierarchy
5 headings
PASS
5 headings
Info::
Single H1 present
  • H1 Suzushii Clothing
  • H2 Best Sellers
  • H2 Popular collections
  • H2 What people are saying
  • H2 Follow us on social
A+
Heading Text Quality
All 5 heading(s) have substantive, well-formed text
PASS
All 5 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Form Input Types
121 form control(s) checked, no type mismatches
PASS
121 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
121 form control(s) checked, no input-semantic issues
PASS
121 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
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"
Info::
<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
Info::
No tabindex anti-patterns detected
A+
Mobile-Readable Font Sizes
All 17 visible text node(s) render at >= 12 CSS pixels
PASS
All 17 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback