Skip to content
https://aliava.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
71
GRADE
C
FIX
8
REVIEW
6
PASS
10
INFO
0
Checks
24
10 PASS 6 REVIEW 8 FIX
D
Mobile Keyboard & Autofill
Action
3/4 eligible field(s) missing autocomplete or inputmode
FIX
3/4 eligible field(s) missing autocomplete or inputmode
Warning::
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">, <input type="email" name="contact[email]" id="Email-1494292487693">, <input type="email" name="email" id="email_01M00W4514B6EH5AA4RQRE8XPS">
D
Tabindex Anti-Patterns
Action
0 positive, 15 -1-on-focusable
FIX
0 positive, 15 -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.)
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 <input>
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
404 Error Page
Action
HTTP 404, custom page
FIX
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 ✓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
Theme color only
FIX
Theme color only
Info::
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: #000000
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 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.

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
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Alt Text Quality
3 of 57 images have issues
REVIEW
3 of 57 images have issues
Critical::
3 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
37 decorative image(s) correctly marked
Info::
17 image(s) with good alt text
57 images 17 good alt text 37 decorative 3 missing
IssueCount
missing3 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

B
Iframe Accessibility
2/2 iframe(s) missing title; 0 placeholder(s)
REVIEW
2/2 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="about:blank")
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://tr.snapchat.com/cm/i?pid=1c109637-d712-464f-bae7-3a260ee5dbf9&u_scsid=1…")
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.
B
Mobile-Readable Font Sizes
94% of visible text renders at >= 12 CSS px (4 below threshold)
REVIEW
94% of visible text renders at >= 12 CSS px (4 below threshold)
Info::
4 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: <span> 11.6px ("Next-Day Delivery Available"); <span> 11.6px ("FREE SHIPPING ON ALL ORDERS"); <span> 11.6px ("Next-Day Delivery Available"); <span> 11.6px ("FREE SHIPPING ON ALL ORDERS").
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 11 fail WCAG AA
REVIEW

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

9 pass 11 fail WCAG AA
title Aliava Official Online Store
1.11:1
#000000
on
#111111
needs 4.5:1 (normal text)
16px · top of page (header area)
p We use cookies and other technologies to…
1.15:1
#000000
on
#1C130C
needs 4.5:1 (normal text)
16px · top of page (header area)
a Privacy Policy.
1.19:1
#000000
on
#221612
needs 4.5:1 (normal text)
16px · above the fold
span Manage preferences
1.28:1
#000000
on
#2E1B14
needs 4.5:1 (normal text)
16px · above the fold
button Accept
2.18:1
#000000
on
#574032
needs 4.5:1 (normal text)
16px · above the fold
button Decline
1.75:1
#000000
on
#4A3122
needs 4.5:1 (normal text)
16px · above the fold
a Skip to content
1.86:1
#000000
on
#4B3627
needs 4.5:1 (normal text)
16px · above the fold
span Close menu
2.52:1
#000000
on
#564C48
needs 4.5:1 (normal text)
16px · above the fold
span NEW
2.34:1
#000000
on
#59453D
needs 4.5:1 (normal text)
16px · above the fold
span SHOP
3.17:1
#000000
on
#645B54
needs 4.5:1 (normal text)
16px · above the fold
span Shop
1.90:1
#000000
on
#4C3829
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 We value your privac…7.01:13.0:1
#000000
#959595
Pass
h2 NEW ARRIVALS7.01:13.0:1
#000000
#959595
Pass
h2 All Dresses7.01:13.0:1
#000000
#959595
Pass
h2 Best Sellers7.01:13.0:1
#000000
#959595
Pass
h2 STYLED BY YOU7.01:13.0:1
#000000
#959595
Pass
h2 Recently Viewed Prod…7.01:13.0:1
#000000
#959595
Pass
h2 Currency7.01:13.0:1
#000000
#959595
Pass
h2 Your Cart7.01:13.0:1
#000000
#959595
Pass
title Aliava Official Onli…1.11:14.5:1
#000000
#111111
Fail
title Aliava Official Onli…7.01:14.5:1
#000000
#959595
Pass
p We use cookies and o…1.15:14.5:1
#000000
#1C130C
Fail
a Privacy Policy.1.19:14.5:1
#000000
#221612
Fail
span Manage preferences1.28:14.5:1
#000000
#2E1B14
Fail
button Accept2.18:14.5:1
#000000
#574032
Fail
button Decline1.75:14.5:1
#000000
#4A3122
Fail
a Skip to content1.86:14.5:1
#000000
#4B3627
Fail
span Close menu2.52:14.5:1
#000000
#564C48
Fail
span NEW2.34:14.5:1
#000000
#59453D
Fail
span SHOP3.17:14.5:1
#000000
#645B54
Fail
span Shop1.90:14.5:1
#000000
#4C3829
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.

B
Lighthouse Accessibility Audits
Score 88/100 — 3 failing, 28 passed
REVIEW
88

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

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
NEXT-DAY DELIVERY AVAILABLE div#AnnouncementSlider > div.slick-list > div.slick-track > div#AnnouncementSlide-49437af7-a76a-4f37-b58b-edc9baffb0a9
SUMMER 2026 Golden Muse Collection SHOP COLLECTION div#Slideshow-f6cbac3c-b4a4-460b-a667-274f37d91a59 > div.slick-list > div.slick-track > div.slideshow__slide

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
CART div.header-item > div.site-nav > div.site-nav__icons > a.site-nav__link

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.

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.custom__item > div.custom__item-inner > div.aos-animate > a div.custom__item > div.custom__item-inner > div.aos-animate > a
div.custom__item > div.custom__item-inner > div.aos-animate > a div.custom__item > div.custom__item-inner > div.aos-animate > a
div.custom__item > div.custom__item-inner > div.aos-animate > a div.custom__item > div.custom__item-inner > div.aos-animate > 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.

○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 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
●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
●ARIA toggle fields have accessible names
●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
●Links are distinguishable without relying on color.
●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
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○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.
○Elements with the `role=text` attribute do not have focusable descendents.
○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
○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.
○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
3 landmarks
PASS
3 landmarks
Info::
<main> landmark present
Warning::
No <nav> landmark found
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header MAIN CONTENTINFO footer
A
Heading Hierarchy
25 headings, 1 skip(s)
PASS
25 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 We value your privacy
  • H1 Aliava
  • H2 Golden Muse Collection
  • H2 Golden Muse Collection
  • H2 Golden Muse Collection
  • H2 Golden Muse Collection
  • H2 NEW ARRIVALS
  • H2 All Dresses
  • H2 Best Sellers
  • H2 STYLED BY YOU
  • H2 Recently Viewed Products
  • H2 Currency
  • H2 Your Cart
  • H4 Your cart is empty! skipped
  • H4 You may also like
  • H5 Evita Ruched Mesh Corset Maxi Dress (Garden Muse)
  • H5 Dasha Modern Midi Dress (Black)
  • H5 Candice Ruffle Mesh Maxi Dress (Garden Muse)
  • H5 Victoria Rose Velvet Maxi Dress (Rose Print)
  • H5 Lianna Deep Slit Neckline Dress (Red)
  • H5 Tula Sheer Panel Wide-Leg Jeans (Antique Wash)
  • H5 Hayley Off Shoulder Midi Dress (Floral Print)
  • H5 Abigail One Sleeve Maxi Dress (Black)
  • H5 Dolly Elegant Bodycon Dress (Black)
  • H5 Fatima Lace Ruched Midi Dress (Brown)

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

A+
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
2 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: 2 all-caps heading(s)
A+
Form Accessibility
All 73 controls labeled
PASS
All 73 controls labeled
Info::
73 control(s) properly labeled
73 controls
73 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
qsearchSearch our storearia-label
#Email-1494292487693emailEnter your emailfor/id
#275185-select-0selectvariant of Evita Ruched Mesh Corset Maxi Dress (Garden Muse)aria-label
#275185-Size-0-XSradioXSfor/id
#275185-Size-0-SradioSfor/id
#275185-Size-0-MradioMfor/id
#275185-Size-0-LradioLfor/id
#275185-Size-0-XLradioXLfor/id
#275185-Size-0-XXLradioXXLfor/id
#275185-select-1selectvariant of Dasha Modern Midi Dress (Black)aria-label
#275185-Size-1-XSradioXSfor/id
#275185-Size-1-SradioSfor/id
#275185-Size-1-MradioMfor/id
#275185-Size-1-LradioLfor/id
#275185-Size-1-XLradioXLfor/id
#275185-Size-1-XXLradioXXLfor/id
#275185-select-2selectvariant of Candice Ruffle Mesh Maxi Dress (Garden Muse)aria-label
#275185-Size-2-XSradioXSfor/id
#275185-Size-2-SradioSfor/id
#275185-Size-2-MradioMfor/id
#275185-Size-2-LradioLfor/id
#275185-Size-2-XLradioXLfor/id
#275185-Size-2-XXLradioXXLfor/id
#275185-select-3selectvariant of Victoria Rose Velvet Maxi Dress (Rose Print)aria-label
#275185-Size-3-XSradioXSfor/id
#275185-Size-3-SradioSfor/id
#275185-Size-3-MradioMfor/id
#275185-Size-3-LradioLfor/id
#275185-Size-3-XLradioXLfor/id
#275185-Size-3-XXLradioXXLfor/id
#275185-select-4selectvariant of Lianna Deep Slit Neckline Dress (Red)aria-label
#275185-Size-4-XSradioXSfor/id
#275185-Size-4-SradioSfor/id
#275185-Size-4-MradioMfor/id
#275185-Size-4-LradioLfor/id
#275185-Size-4-XLradioXLfor/id
#275185-Size-4-XXLradioXXLfor/id
#275185-select-5selectvariant of Tula Sheer Panel Wide-Leg Jeans (Antique Wash)aria-label
#275185-Size-5-2radio2for/id
#275185-Size-5-4radio4for/id
#275185-Size-5-6radio6for/id
#275185-Size-5-8radio8for/id
#275185-Size-5-10radio10for/id
#275185-Size-5-12radio12for/id
#275185-select-6selectvariant of Hayley Off Shoulder Midi Dress (Floral Print)aria-label
#275185-Size-6-XSradioXSfor/id
#275185-Size-6-SradioSfor/id
#275185-Size-6-MradioMfor/id
#275185-Size-6-LradioLfor/id
#275185-Size-6-XLradioXLfor/id
#275185-Size-6-XXLradioXXLfor/id
#275185-select-7selectvariant of Abigail One Sleeve Maxi Dress (Black)aria-label
#275185-Size-7-XSradioXSfor/id
#275185-Size-7-SradioSfor/id
#275185-Size-7-MradioMfor/id
#275185-Size-7-LradioLfor/id
#275185-Size-7-XLradioXLfor/id
#275185-Size-7-XXLradioXXLfor/id
#275185-select-8selectvariant of Dolly Elegant Bodycon Dress (Black)aria-label
#275185-Size-8-XSradioXSfor/id
#275185-Size-8-SradioSfor/id
#275185-Size-8-MradioMfor/id
#275185-Size-8-LradioLfor/id
#275185-Size-8-XLradioXLfor/id
#275185-Size-8-XXLradioXXLfor/id
#275185-select-9selectvariant of Fatima Lace Ruched Midi Dress (Brown)aria-label
#275185-Size-9-XSradioXSfor/id
#275185-Size-9-SradioSfor/id
#275185-Size-9-MradioMfor/id
#275185-Size-9-LradioLfor/id
#275185-Size-9-XLradioXLfor/id
#275185-Size-9-XXLradioXXLfor/id
#email_01M00W4514B6EH5AA4RQRE8XPSemailWhat is your email?aria-label
A+
Form Input Types
73 form control(s) checked, no type mismatches
PASS
73 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
73 form control(s) checked, no input-semantic issues
PASS
73 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
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+
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
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
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::
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.

Send Feedback