Skip to content
https://www.kiyonna.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
65
GRADE
D
FIX
9
REVIEW
6
PASS
9
INFO
0
Checks
24
9 PASS 6 REVIEW 9 FIX
F
Heading Hierarchy
Action
103 headings, 5 skip(s)
FIX
103 headings, 5 skip(s)
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H5 PROUDLY MADE WITH LOVE IN THE USA!
  • H5 NEED HELP? CALL US: 888-549-6662
  • H5 NEED HELP? CALL US: 888-549-6662
  • H5 PROUDLY MADE WITH LOVE IN THE USA!
  • H5 NEED HELP? CALL US: 888-549-6662
  • H5 PROUDLY MADE WITH LOVE IN THE USA!
  • H1 window.addEventListener("load", () => { const items = document.getElementsByClassName('animation--product-media '); const visibleElement = Array.prototype.filter.call(items , function(item){
  • H2 Currency
  • H4 Shop New Arrivals skipped
  • H4 The Fall Edit
  • H4 The Color Edit: All Eyes on Blue
  • H4 In Full Bloom: Floral Dresses & Tops
  • H4 The Color Edit: Green Goddess Dressing
  • H4 Vacation Dresses & Tops
  • H4 Wedding Guest
  • H4 Jumpsuits
  • H4 Embroidered Dresses
  • H4 Styles With Pockets
  • H4 Styles With Long Sleeves
  • H4 Office Chic
  • H4 Gift Shop 🎁
  • H4 Shop Fall Styles
  • H4 Fall Wedding
  • H4 Winter Wedding
  • H4 Fall in Love: Velvet
  • H4 Styles with Long Sleeves
  • H4 Holiday Styles
  • H4 Shop All Wedding Guest Dresses
  • H4 Fall Wedding
  • H4 Black Tie Wedding
  • H4 Cocktail Wedding
  • H4 Mother of the Bride/Groom
  • H4 Casual Wedding
  • H4 Floral Dresses
  • H4 Semi-Formal Wedding
  • H4 Garden Wedding
  • H4 Spring Wedding
  • H4 Summer Wedding
  • H4 Winter Wedding
  • H4 Shop All Dresses
  • H4 Wedding Guest Dresses
  • H4 Evening Gowns
  • H4 Mother of the Bride/Groom
  • H4 Maxi Dresses
  • H4 Floral Dresses
  • H4 Party Perfect
  • H4 Wrap Dresses
  • H4 Lace Dresses
  • H4 Cocktail Dresses
  • H4 Embroidered Dresses
  • H4 Dresses Under $150
  • H4 Black Dresses
  • H4 White Dresses & More
  • H4 Casual & Everyday Dresses
  • H4 Vacation Dresses & Tops
  • H4 Dresses with Pockets
  • H4 All Tops
  • H4 All Bottoms
  • H4 Jumpsuits
  • H4 Coats, Cardigans & Sweaters
  • H4 Vacation Dresses & Tops
  • H4 All Wedding Dresses
  • H4 Wedding Guest
  • H4 Mother of the Bride or Groom
  • H4 Black Wedding Dresses
  • H4 Real Brides: Wedding Tips and Stories
  • H4 All SALE Items
  • H4 SALE Tops & Bottoms
  • H4 SALE Dresses
  • H4 SALE Maxis & Jumpsuits
  • H4 SALE Gowns & Bridal
  • H4 Mystery Styles
  • H4 Final Sale Items
  • H1 window.addEventListener("load", () => { const items = document.getElementsByClassName('animation--product-media '); const visibleElement = Array.prototype.filter.call(items , function(item){ duplicate H1
  • H2 Currency
  • H2 Your Cart
  • H3 Your Cart is Empty
  • H3 Let's Keep in Touch...
  • H3 Sign Up for Our Newsletter
  • H3 Sign Up for Mobile Alerts
  • H2 Trending Now
  • H4 Our customers are currently shopping for... skipped
  • H2 Maxi Dresses
  • H2 Wedding Guest Outfits
  • H2 Formal Gowns
  • H2 the Style Scene
  • H5 Our exclusive range of chic plus size clothing is designed for the modern woman with curves. skipped
  • H2 Sign Up For Our Newsletter
  • H6 EXCLUSIVE BIRTHDAY AND ORDERVERSARY CODES: Exclusive birthday and orderversary coupons expire at 11:59pm PT on 10/31/26. Not valid on Skinnytees, Spanx, Kinsley Keyhole Wrap, gift cards, jewelry, Myst skipped
  • H6 EXCLSIVE 10% CODES:  Offer expires 10/31/26 at 11:59pm PT. Not valid on Skinnytees, Spanx, Kinsley Keyhole Wrap, gift cards, jewelry, fashion tape, Mystery styles, Final Sale styles  and wholesale o
  • H6 EXCLUSIVE 15% CODES:  Offer expires 10/31/26 at 11:59pm PT. Not valid on Skinnytees, Spanx, Kinsley Keyhole Wrap, gift cards, jewelry, fashion tape, Mystery styles, Final Sale styles  and wholesale
  • H4 Contact Us
  • H5 Chat Now
  • H5 Email Us
  • H5 Customer Care: 888-549-6662
  • H5 International: +1-714-956-5588
  • H4 Customer Service
  • H4 About us
  • H4 SHOP
  • H4 More
  • H2 Currency
  • H4 Availability skipped
  • H3 (empty)

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

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

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

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

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

D
Tabindex Anti-Patterns
Action
0 positive, 11 -1-on-focusable
FIX
0 positive, 11 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
D
Iframe Accessibility
Action
5/5 iframe(s) missing title; 0 placeholder(s)
FIX
5/5 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="https://www.kiyonna.com/web-pixels@264bf420w2e1681cap8d55857fm7d879f9c/custom/w…")
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://www.kiyonna.com/web-pixels@264bf420w2e1681cap8d55857fm7d879f9c/custom/w…")
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://www.kiyonna.com/web-pixels@264bf420w2e1681cap8d55857fm7d879f9c/custom/w…")
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://www.kiyonna.com/web-pixels@264bf420w2e1681cap8d55857fm7d879f9c/custom/w…")
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://www.kiyonna.com/web-pixels@264bf420w2e1681cap8d55857fm7d879f9c/custom/w…")
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.
F
404 Error Page
Action
HTTP 429, custom page
FIX
HTTP 429, custom page
Warning::
Unexpected status code: HTTP 429
Expected HTTP 404 but received 429. This may confuse search engine crawlers.
Got: HTTP 429
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 429 ✗Page Title Verifying your connection... ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 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::
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
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
No navigation patterns
FIX
No navigation patterns
Info::
4 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 4 <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
Landmark Structure
8 landmarks
REVIEW
8 landmarks
Info::
<main> landmark present
Info::
4 <nav> landmark(s) found
Warning::
4 of 4 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Warning::
Skip navigation link is missing (WCAG 2.4.1)
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
Page Structure — as a screen reader sees it
BANNER header NAV MAIN CONTENTINFO footer

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

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more ▾

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

C
Form Accessibility
Action
4 of 5 controls have issues
REVIEW
4 of 5 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="checkbox">
Warning::
3 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="q" id="search">; <input type="text" name="q" id="search">; <input type="text" name="q" id="search">
Info::
1 control(s) properly labeled
5 controls
1 labeled
3 placeholder only
1 unlabeled
ControlTypeLabelMethod
#newsletter-subscribe-emailemailYour emailfor/id
#searchtext(What can we help you find?)placeholder only
#searchtext(What are you looking for?)placeholder only
#searchtext(What can we help you find?)placeholder only
inputcheckbox(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<input type="checkbox">

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

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

<input type="text" name="q" id="search">; <input type="text" name="q" id="search">; <input type="text" name="q" id="search">

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
Tap Target Adequacy
1 tap target(s) too small or too close together
REVIEW
1 tap target(s) too small or too close together
Info::
1 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
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
title Plus Size Clothing for Women | Kiyonna C…
1.99:1
#000000
on
#682D21
needs 4.5:1 (normal text)
16px · top of page (header area)
a My Wishlist
1.99:1
#000000
on
#682D21
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Currency21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Currency21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Your Cart21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Trending Now21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Maxi Dresses21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Wedding Guest Outfit…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Formal Gowns21.00:13.0:1
#000000
#FFFFFF
Pass
h2 the Style Scene21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Sign Up For Our News…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Currency21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Your Cart is Empty21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Let's Keep in Touch.…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Sign Up for Our News…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Sign Up for Mobile A…21.00:13.0:1
#000000
#FFFFFF
Pass
title Plus Size Clothing f…1.99:14.5:1
#000000
#682D21
Fail
a My Wishlist1.99:14.5:1
#000000
#682D21
Fail
div We use essential coo…21.00:14.5:1
#000000
#FFFFFF
Pass
span Cookie Policy21.00:14.5:1
#000000
#FFFFFF
Pass
div and21.00:14.5:1
#000000
#FFFFFF
Pass
span Privacy Policy21.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 87/100 — 5 failing, 22 passed
REVIEW
87

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
EXCLUSIVE BIRTHDAY AND ORDERVERSARY CODES: Exclusive birthday and orderversary … div.footer__group > div.footer__group-content > div.fs-body-100 > h6
EXCLUSIVE BIRTHDAY AND ORDERVERSARY CODES div.footer__group-content > div.fs-body-100 > h6 > strong
EXCLSIVE 10% CODES:  Offer expires 10/31/26 at 11:59pm PT. Not valid on Skinnyt… div.footer__group > div.footer__group-content > div.fs-body-100 > h6
EXCLSIVE 10% CODES:   div.footer__group-content > div.fs-body-100 > h6 > strong
EXCLUSIVE 15% CODES:  Offer expires 10/31/26 at 11:59pm PT. Not valid on Skinny… div.footer__group > div.footer__group-content > div.fs-body-100 > h6
EXCLUSIVE 15% CODES:   div.footer__group-content > div.fs-body-100 > h6 > strong
EXCLUSIVE 20% OFF CODES:   div.footer__group-content > div.fs-body-100 > h6 > strong
EXCLUSIVE 50% OFF CODES:   div.footer__group-content > div.fs-body-100 > h6 > strong
EXCLUSIVE EMAIL SIGN UP AND TEXT MESSAGE CODES div.footer__group-content > div.fs-body-100 > h6 > strong
FREE2DAY div.footer__group-content > div.fs-body-100 > h6 > strong
FRIENDS & FAMILY SALE div.footer__group-content > div.fs-body-100 > h6 > strong
Copyright © 2026, Kiyonna Clothing, Inc. KIYONNA® is a registered trademark. Al… div.footer__bottom > div.footer__bottom-left > div.footer__credits > p
Kiyonna div.footer__bottom-left > div.footer__credits > p > a
Powered by Shopify div.footer__bottom-left > div.footer__credits > p > a

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 customers are currently shopping for... div.grid__header > div.grid__text-block > div.grid__subheading > h4
Our exclusive range of chic plus size clothing is designed for the modern woman… div.multi-column__inner > div.multi-column__introduction > div.multi-column__subheading > h5
EXCLUSIVE BIRTHDAY AND ORDERVERSARY CODES: Exclusive birthday and orderversary … div.footer__group > div.footer__group-content > div.fs-body-100 > h6

These are opportunities to improve keyboard navigation in your application.

Names and labels

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.multi-column__grid-item > div.multi-column__grid-item-inner > figure.multi-column__grid-item-image-figure > a.multi-column__grid-item-image-wrapper div.multi-column__grid-item > div.multi-column__grid-item-inner > figure.multi-column__grid-item-image-figure > a.multi-column__grid-item-image-wrapper
div.multi-column__grid-item > div.multi-column__grid-item-inner > figure.multi-column__grid-item-image-figure > a.multi-column__grid-item-image-wrapper div.multi-column__grid-item > div.multi-column__grid-item-inner > figure.multi-column__grid-item-image-figure > a.multi-column__grid-item-image-wrapper
div.multi-column__grid-item > div.multi-column__grid-item-inner > figure.multi-column__grid-item-image-figure > a.multi-column__grid-item-image-wrapper div.multi-column__grid-item > div.multi-column__grid-item-inner > figure.multi-column__grid-item-image-figure > a.multi-column__grid-item-image-wrapper
div.multi-column__grid-item > div.multi-column__grid-item-inner > figure.multi-column__grid-item-image-figure > a.multi-column__grid-item-image-wrapper div.multi-column__grid-item > div.multi-column__grid-item-inner > figure.multi-column__grid-item-image-figure > a.multi-column__grid-item-image-wrapper
div.multi-column__grid-item > div.multi-column__grid-item-inner > figure.multi-column__grid-item-image-figure > a.multi-column__grid-item-image-wrapper div.multi-column__grid-item > div.multi-column__grid-item-inner > figure.multi-column__grid-item-image-figure > a.multi-column__grid-item-image-wrapper
div.multi-column__grid-item > div.multi-column__grid-item-inner > figure.multi-column__grid-item-image-figure > a.multi-column__grid-item-image-wrapper div.multi-column__grid-item > div.multi-column__grid-item-inner > figure.multi-column__grid-item-image-figure > a.multi-column__grid-item-image-wrapper
div.multi-column__grid-item > div.multi-column__grid-item-inner > figure.multi-column__grid-item-image-figure > a.multi-column__grid-item-image-wrapper div.multi-column__grid-item > div.multi-column__grid-item-inner > figure.multi-column__grid-item-image-figure > a.multi-column__grid-item-image-wrapper
div.multi-column__grid-item > div.multi-column__grid-item-inner > figure.multi-column__grid-item-image-figure > a.multi-column__grid-item-image-wrapper div.multi-column__grid-item > div.multi-column__grid-item-inner > figure.multi-column__grid-item-image-figure > a.multi-column__grid-item-image-wrapper

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
Search div.quick-search__bar > div.quick-search__bar-inner > div.quick-search__actions > button.quick-search__submit

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
0 div.sqs > div.scv > div.mn > a.header__icon-touch
○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
●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
●`[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 are distinguishable without relying on color.
●No element has a `[tabindex]` value greater than 0
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
○`[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
○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
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
○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.
○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.
A
Heading Text Quality
2 heading-text-quality issue(s) detected
PASS
2 heading-text-quality issue(s) detected
Warning::
3 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: 198 chars - H1: 198 chars - H6: 200 chars
Got: 3 >120-char heading(s)
Info::
7 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: 7 all-caps heading(s)
A
Alt Text Quality
1 of 41 images have issues
PASS
1 of 41 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
40 decorative image(s) correctly marked
41 images 40 decorative 1 missing
IssueCount
missing1 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

A
Form Input Types
3 input(s) using type=text where a specific type would help
PASS
3 input(s) using type=text where a specific type would help
Info::
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">.
Info::
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">.
Info::
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
5 form control(s) checked, no input-semantic issues
PASS
5 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+
Mobile-Readable Font Sizes
All 13 visible text node(s) render at >= 12 CSS pixels
PASS
All 13 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