Skip to content
https://boody.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
58
GRADE
D
FIX
13
REVIEW
1
PASS
10
INFO
0
Checks
24
10 PASS 1 REVIEW 13 FIX
F
Heading Hierarchy
Action
40 headings, 2 skip(s)
FIX
40 headings, 2 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
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::
9 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H2 Introducing UltraLyte™
  • H2 Better basics, powered by bamboo
  • H2 Polka Dots With A Purpose
  • H2 Featured In
  • H2 UltraLyte™
  • H2 Meet UltraLyte™
  • H2 The Lounge
  • H2 Shop by category
  • H2 What Our Customers Are Saying
  • H2 What You'll Notice
  • H2 Join Our Comfy Community
  • H3 You’re on Boody US.
  • H2 Account
  • H2 (empty)
  • H2 Earn points, track orders, and save your shopping history
  • H4 Transfer History skipped
  • H2 Recently Viewed
  • H2 Favorites
  • H2 Popular Today
  • H2 Your Orders
  • H4 (empty)
  • H4 (empty)
  • H4 (empty)
  • H4 (empty)
  • H4 (empty)
  • H4 (empty)
  • H2 My Preferences
  • H2 My Addresses
  • H3 Collections
  • H3 All Favorites
  • H4 (empty)
  • H4 (empty)
  • H5 Unlock free returns for
  • H2 Privacy Preference Center
  • H3 Manage Consent Preferences
  • H4 Strictly Necessary Cookies
  • H4 Targeting Cookies
  • H4 Functional Cookies
  • H4 Performance Cookies
  • H3 Cookie List

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

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

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

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

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

F
Alt Text Quality
Action
27 of 160 images have issues
FIX
27 of 160 images have issues
Critical::
27 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
18 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
79 decorative image(s) correctly marked
Info::
54 image(s) with good alt text
160 images 54 good alt text 79 decorative 27 missing
IssueCount
missing27 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

D
Form Accessibility
Action
9 of 45 controls have issues
FIX
9 of 45 controls have issues
Critical::
8 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="email">; <input type="submit">; <input type="submit">; <select name="variant_id">; <input type="text" id="rivo_profile_first_name">; <input type="text" id="rivo_profile_last_name">; <input type="email" id="rivo_profile_email">; <input type="tel">
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" id="searchbar">
Info::
36 control(s) properly labeled
45 controls
36 labeled
1 placeholder only
8 unlabeled
ControlTypeLabelMethod
#SearchSuggestionsearchnone
#first_name_01KG69Z6C67YYXCYYVNQDHHN7QtextFirst namefor/id
#email_01KG69Z6CD2EQ04C1FWB9PEZ44emailEmailfor/id
#select-input-countryselectCountry/Regionfor/id
accepts_marketingcheckboxnone
#customer_loyalty_accepts_marketingcheckboxnone
customer[email]emailEmailaria-label
accepts_marketingcheckboxnone
#customer_loyalty_accepts_marketingcheckboxnone
inputtextVerification code inputaria-label
inputtextVerification code inputaria-label
inputtextVerification code inputaria-label
inputtextVerification code inputaria-label
inputtextGift card codearia-label
inputtextReferral URLaria-label
#rivo_transfer_credit_amountnumberAmountfor/id
#rivo_transfer_credit_messagetextareaMessage (optional)for/id
inputtextGift URLaria-label
#rivo_claim_transfer_emailemailEmail addressaria-label
#show_gift_card_recipient_fieldscheckboxnone
#rivo_gift_card_variant_idselectGift Card Valuearia-label
#rivo_gift_card_recipient_nametextRecipient Namefor/id
#rivo_gift_card_recipient_emailemailRecipient Emailfor/id
#rivo_gift_card_delivery_datedateDelivery Datefor/id
#rivo_gift_card_messagetextareaMessagefor/id
inputtextReferral URLaria-label
#customer_accepts_marketingcheckboxnone
#customer_sms_accepts_marketingcheckboxnone
#ot-group-id-C0004checkboxTargeting Cookiesfor/id
#ot-group-id-C0003checkboxFunctional Cookiesfor/id
#ot-group-id-C0002checkboxPerformance Cookiesfor/id
#vendor-search-handlertextCookie list searcharia-label
#chkbox-idcheckboxcheckbox labelfor/id
#select-all-hosts-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-leg-handlercheckboxcheckbox labelfor/id
#searchbartext(Search Products)placeholder only
variant_idselect(none)none
inputemail(none)none
#rivo_profile_first_nametext(none)none
#rivo_profile_last_nametext(none)none
#rivo_profile_emailemail(none)none
inputsubmit(none)none
inputtel(none)none
inputsubmit(none)none

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

<input type="email">; <input type="submit">; <input type="submit">; <select name="variant_id">; <input type="text" id="rivo_profile_first_name">; <input type="text" id="rivo_profile_last_name">; <input type="email" id="rivo_profile_email">; <input type="tel">

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" id="searchbar">

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

D
Mobile Keyboard & Autofill
Action
12/15 eligible field(s) missing autocomplete or inputmode
FIX
12/15 eligible field(s) missing autocomplete or inputmode
Warning::
3 field(s) missing recommended autocomplete attribute
WCAG 1.3.5 (Level AA): inputs whose purpose maps to a Common Input Purpose value should declare it via `autocomplete=`. Required for password managers, browser autofill, and assistive tech that customizes inputs (e.g., simplified keyboards). Mobile autofill in particular cuts form-completion time by 30-50% when these are present. Affected purposes: email.
Got: <input type="email" id="rivo_claim_transfer_email">, <input type="email" id="rivo_gift_card_recipient_email">, <input type="email" id="rivo_profile_email">
Warning::
9 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, numeric, tel.
Got: <input type="search" name="q" id="SearchSuggestion">, <input type="email" name="email" id="email_01KG69Z6CD2EQ04C1FWB9PEZ44">, <input type="email">, <input type="email" name="customer[email]">, <input type="number" id="rivo_transfer_credit_amount">
D
Tabindex Anti-Patterns
Action
0 positive, 21 -1-on-focusable
FIX
0 positive, 21 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <button id="nosto-carousel-tab-template--27819778572424__nosto_product_carousel_b8EqFP-1">
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 <button id="nosto-carousel-tab-template--27819778572424__nosto_product_carousel_b8EqFP-2">
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 <button id="template--27819778572424__module_shop_by_category_HDXK6q-ARG1RNFJwU0h3RTk4Y__module_audience_tab_fwdY7W-tab">
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 <button id="template--27819778572424__module_shop_by_category_HDXK6q-AbWJIdlA3SDhad0EyK__module_audience_tab_Xe7ncp-tab">
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.)
Info::
tabindex="-1" on naturally-focusable <button>
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 <button>
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 <button>
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 <button>
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 <button>
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 <button>
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 <button>
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 <button>
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 <button>
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 <button>
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 <button>
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 <button>
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 id="rivo-tab-rivo">
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 id="rivo-tab-rivo-orders">
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 id="rivo-tab-rivo-profile">
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 id="rivo-tab-rivo-community">
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/15 iframe(s) missing title; 0 placeholder(s)
FIX
5/15 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="https://boody.com/web-pixels@49d3b31aw169a7c20pfc9cb2c9m68241e55/custom/web-pix…")
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://boody.com/web-pixels@49d3b31aw169a7c20pfc9cb2c9m68241e55/custom/web-pix…")
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://boody.com/web-pixels@49d3b31aw169a7c20pfc9cb2c9m68241e55/custom/web-pix…")
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://boody.com/web-pixels@49d3b31aw169a7c20pfc9cb2c9m68241e55/custom/web-pix…")
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=3403031d-44e0-418e-9d6b-fa5693970e4d&u_scsid=9…")
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 403, custom page
FIX
HTTP 403, custom page
Warning::
Unexpected status code: HTTP 403
Expected HTTP 404 but received 403. This may confuse search engine crawlers.
Got: HTTP 403
Info::
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 ✗
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
1 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 1 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
B
Tap Target Adequacy
2 tap target(s) too small or too close together
REVIEW
2 tap target(s) too small or too close together
Info::
2 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.
A
Landmark Structure
21 landmarks
PASS
21 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Info::
Skip navigation link present
Warning::
Skip link target(s) don't exist on page: #main
The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.
Page Structure — as a screen reader sees it
BANNER header NAV "Header navigation" MAIN CONTENTINFO footer

The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.

Why this matters

Skip link points at an ID that doesn't exist on the page. The link looks fine visually but does nothing when activated -- silent WCAG 2.4.1 failure.

Learn more ▾

Find the target landmark (typically <main> or the first <h1>) and add `id="..."` matching the skip link's href fragment. Test by tabbing to the skip link and pressing Enter -- focus should jump to the target.

Source: WCAG 2.1 SC 2.4.1

A+
Heading Text Quality
All 40 heading(s) have substantive, well-formed text
PASS
All 40 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Form Input Types
1 input(s) using type=text where a specific type would help
PASS
1 input(s) using type=text where a specific type would help
Info::
Input "vendor-search-handler" should use type="search" (currently type="text")
Field name "vendor-search-handler" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
A
Form Input Quality
1 input-semantic issue(s) across 45 form control(s)
PASS
1 input-semantic issue(s) across 45 form control(s)
Info::
1 credit-card-shaped field(s) missing `autocomplete=cc-*`
Credit-card fields (`cc-number`, `cc-name`, `cc-exp`, `cc-exp-month`, `cc-exp-year`, `cc-csc`) trigger native browser autofill at checkout -- one of the highest-impact conversion levers. Without the cc-* autocomplete value, autofill is disabled even for fields that look obviously credit-card-shaped. Sample: <input type="text">.
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 8 visible text node(s) render at >= 12 CSS pixels
PASS
All 8 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
2 mobile-depth signal(s) detected
PASS
2 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.
Info::
Viewport `viewport-fit=cover` -- supports notched / dynamic-island devices
The viewport meta declares `viewport-fit=cover`, which lets the page draw into the safe-area edges (notch, dynamic island, home indicator) on iPhone X+ devices. Pair with `env(safe-area-inset-*)` CSS to keep critical UI inside the inset rectangle while letting backgrounds extend edge-to-edge.
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Introducing21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Better basics,21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Polka Dots With A Pu…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Meet21.00:13.0:1
#000000
#FFFFFF
Pass
h2 The Lounge21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Shop by21.00:13.0:1
#000000
#FFFFFF
Pass
h2 What You'll21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Account21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Earn points, track o…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Recently Viewed21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Favorites21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Popular Today21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Your Orders21.00:13.0:1
#000000
#FFFFFF
Pass
h2 My Preferences21.00:13.0:1
#000000
#FFFFFF
Pass
h2 My Addresses21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Privacy Preference C…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 You’re on Boody US…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Collections21.00:13.0:1
#000000
#FFFFFF
Pass
h3 All Favorites21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Manage Consent Prefe…21.00:13.0: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.

A
Lighthouse Accessibility Audits
Score 90/100 — 4 failing, 30 passed
PASS
90

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
(3501) div.flex > div.flex > div.flex > span.text-[#A5A399]
Bamboo Seamfree swiper-slide.w-[320px] > div.flex > div.flex > div.text-[11.5px]
(1831) div.flex > div.flex > div.flex > span.text-[#A5A399]
Bamboo Seamfree swiper-slide.w-[320px] > div.flex > div.flex > div.text-[11.5px]

These are opportunities to improve the legibility of your content.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.relative > div.flex > a.truncate > img.w-full div.relative > div.flex > a.truncate > img.w-full
div.w-4/12 > div.flex > a.truncate > img.w-full div.w-4/12 > div.flex > a.truncate > img.w-full
div.flex > div.flex > a.truncate > img.w-full div.flex > div.flex > a.truncate > img.w-full
div.flex > div.flex > a.block > img.w-auto div.flex > div.flex > a.block > img.w-auto
div.flex > div.flex > a.block > img.w-auto div.flex > div.flex > a.block > img.w-auto
div.flex > div.flex > div.h-[30px] > img.w-full div.flex > div.flex > div.h-[30px] > img.w-full
div.flex > div.flex > div.h-[30px] > img.w-full div.flex > div.flex > div.h-[30px] > img.w-full
div.flex > div.flex > div.h-[30px] > img.w-full div.flex > div.flex > div.h-[30px] > img.w-full
div.flex > div.flex > div.h-[30px] > img.w-full div.flex > div.flex > div.h-[30px] > img.w-full
div.flex > div.flex > div.h-[30px] > img.w-full div.flex > div.flex > div.h-[30px] > img.w-full
div.flex > div.flex > div.h-[30px] > img.w-full div.flex > div.flex > div.h-[30px] > img.w-full

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
Go to slide 2 module-hero-slider.module-hero-slider__root > carousel-swiper.swiper > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 3 module-hero-slider.module-hero-slider__root > carousel-swiper.swiper > div.swiper-pagination > span.swiper-pagination-bullet

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
Ribbed Boat Neck Bodysuit - Black $62 div.relative > div.overflow-hidden > div.flex > a.flex
Seamfree Undershorts 6" - Black $26 div.relative > div.overflow-hidden > div.flex > a.flex
○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]`s are contained by their required parent element
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Form elements have associated labels
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●Select elements have associated label elements.
●`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
●Document has a `<title>` element
●`<frame>` or `<iframe>` elements have a title
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●Links have a discernible name
●No element has a `[tabindex]` value greater than 0
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Image elements do not have `[alt]` attributes that are redundant text.
●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 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
○`<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
○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
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○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.

Send Feedback