Skip to content
https://tnuck.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
59
GRADE
D
FIX
12
REVIEW
1
PASS
11
INFO
0
Checks
24
11 PASS 1 REVIEW 12 FIX
F
Heading Hierarchy
Action
169 headings, 2 skip(s)
FIX
169 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.
  • H3 Back New
  • H3 New Arrivals
  • H4 This Just In
  • H4 New From Barbour
  • H4 Best Sellers This Week
  • H3 Back Edits
  • H3 Shops
  • H3 Editorials
  • H4 The Shirting Edit
  • H4 Tuckernuck x Fanatics
  • H4 The Fall Must-Haves
  • H3 Back Best Sellers
  • H3 Most Loved
  • H3 Back In Stock!
  • H3 Today's Top 5
  • H4 Olive Thin Wale Corduroy Tara Shirt Dress
  • H4 Brown Embellished Lana Crewneck
  • H4 Black Pony Hair Laurence Jacket
  • H3 Back Clothing
  • H3 Clothing
  • H3 Occasions
  • H4 Everyday Outerwear
  • H4 Luxe Cashmere
  • H4 Elevated Tops
  • H3 Back Dresses
  • H3 Dresses
  • H3 By Length
  • H3 Trending Now
  • H4 Little Black Dresses
  • H4 Cocktail O'Clock
  • H4 9 to 5
  • H3 Back Sport
  • H3 Tuckernuck x Fanatics
  • H3 Shop All
  • H3 Featured Shops
  • H4 Tuckernuck x Fanatics
  • H4 Ready to Rally
  • H4 To a Tee
  • H3 Back Shoes
  • H3 Shoes
  • H3 Noteworthy Names
  • H4 Seasonal Boots
  • H4 Timeless Flats
  • H4 Happening Heels
  • H3 Back Accessories
  • H3 Accessories
  • H3 Noteworthy Names
  • H4 Carry-All Bags
  • H4 Special Jewels
  • H4 Staple Belts
  • H3 Back Beauty
  • H3 Beauty
  • H3 Noteworthy Names
  • H4 Skin Wins
  • H4 Glow Getters
  • H4 Make-Up Must-Haves
  • H3 Back Designers
  • H3 Designers
  • H3 Our Labels
  • H4 Tuckernuck
  • H4 Tuckernuck Shoes
  • H4 New From Brands We Love
  • H3 Back Home
  • H3 Home
  • H3 Noteworthy Names
  • H4 Shop All Home
  • H4 Tuckernuck Home
  • H4 Home New Arrivals
  • H3 Back Gents & Kids
  • H3 Gents
  • H3 Noteworthy Names
  • H3 Kids
  • H3 Noteworthy Names
  • H4 Shop All Gents
  • H4 Shop All Kids
  • H3 Back Sale
  • H3 Ladies Sale
  • H3 More Sale Shops
  • H4 Dresses on Sale
  • H4 Tops on Sale
  • H4 Designers on Sale
  • H2 The Thanksgiving
Style Guide
  • H2 Dress thePART
  • H3 Golden Rules
  • H3 Happening Heels
  • H2 SweaterWEATHER
  • H2 Good
  • H2 SPORT
  • H2 Welcome
  • H2 HOME
  • H2 Tuckernuck Editorials
  • H3 The Thanksgiving
Style Guide
  • H3 The Shirting Edit
  • H3 Tuckernuck x Fanatics
  • H3 The Fall Must-Haves
  • H3 The Event Edit
  • H3 Back in Play
  • H3 The Denim Edit
  • H3 The Fall 2026
Find the Fun List
  • H3 A Curious Life: Fall Style Guide
  • H3 Back to Cool
  • H3 The Event Edit
  • H3 An Expert’s Guide to Cocktail Attire
  • H3 The Mount Desert Island, Maine Travel Guide
  • H3 Tuscan Escape Lifestyle Guide
  • H3 The Tuscany Travel Guide
  • H3 Roman Holiday Lifestyle Guide
  • H3 The Rome Travel Guide
  • H3 Rome Packing List
  • H3 Tour Our Nantucket Store, A Sailor’s Valentine by Tuckernuck
  • H3 Introducing Julia Berolzheimer’s Travel Capsule Collection
  • H3 The North Fork, Long Island Travel Guide
  • H3 The Fourth of July Lifestyle Guide: Celebrate Summer
  • H3 The Sport Lifestyle Guide: Summer, Served
  • H3 The Entertaining Edit:
Summer Lobster Bake
  • H3 Introducing the Summer Heritage Collection
  • H3 The Summer 2026
Find the Fun List
  • H3 The Summer Lifestyle Guide: Grecian Getaway
  • H3 The Hydra, Greece Travel Guide
  • H3 The May Must-Haves: Bohemian Ease
  • H3 Tuckernuck Tastemaker: Bradley Agather
  • H3 The Summer Accessories Edit
  • H3 The Nantucket, MA Travel Guide
  • H3 Nantucket Packing List
  • H3 The Dress Edit: Golden Hour
  • H3 The Paris, France Travel Guide
  • H3 What to Pack for Paris
  • H3 Tuckernuck Tastemaker: Sara Ruffin Costello
  • H3 The April Must-Haves: Fresh Classics
  • H3 The Best Hostess Gifts, According to a Home Expert
  • H3 The Spring Home Collection
  • H3 The Spring Party Edit: Natural Beauty
  • H3 Tour Our Georgetown Flagship
  • H3 The March Must-Haves: Find the Fun-damentals
  • H3 The Sport Playbook:
Spring in Full Swing
  • H3 The Spring Lifestyle Guide: Buenos Aires in Bloom
  • H3 Buenos Aires Travel Guide
  • H3 The Spring 2026
Find the Fun List
  • H3 The Washington, DC Travel Guide
  • H3 The Washington, DC Packing List
  • H3 The Spring 2026 Trend Report
  • H2 Hi, We're Tuckernuck
  • H2 We Design & Curate
  • H2 For a Fun-Filled Life
  • H2 Customer Service
  • H2 About us
  • H2 Want in on newness, style tips, and more?
  • H2 Free Shipping, Returns & Exchanges
  • H2 Your Shopping Bag is Empty!
  • H2 Account
  • H2 (empty)
  • H2 Join or Sign In to VIP Rewards
  • H4 Transfer History skipped
  • H2 Recently Viewed
  • H2 Make these favorites yours at checkout!
  • 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)

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
66 of 139 images have issues
FIX
66 of 139 images have issues
Critical::
66 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
56 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
3 image(s) with alt text over 125 characters
Info::
2 decorative image(s) correctly marked
Info::
68 image(s) with good alt text
139 images 68 good alt text 2 decorative 66 missing
IssueCount
missing66 image(s)
too long3 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
Mobile Keyboard & Autofill
Action
13/15 eligible field(s) missing autocomplete or inputmode
FIX
13/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::
10 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="HeaderSearchMobile">, <input type="search" name="q" id="HeaderSearchDesktop">, <input type="email" name="contact[email]" id="FooterNewsletterEmail">, <input type="email">, <input type="email" name="customer[email]">
D
Tabindex Anti-Patterns
Action
0 positive, 16 -1-on-focusable
FIX
0 positive, 16 -1-on-focusable
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
15/19 iframe(s) missing title; 0 placeholder(s)
FIX
15/19 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="")
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="")
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://tnuck.com/web-pixels@05c62d7ewbe538af9pdeb4fec1me339d55a/app/web-pixel-…")
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://tnuck.com/web-pixels@05c62d7ewbe538af9pdeb4fec1me339d55a/app/web-pixel-…")
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://tnuck.com/web-pixels@05c62d7ewbe538af9pdeb4fec1me339d55a/app/web-pixel-…")
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://tnuck.com/web-pixels@05c62d7ewbe538af9pdeb4fec1me339d55a/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://tnuck.com/web-pixels@05c62d7ewbe538af9pdeb4fec1me339d55a/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://tnuck.com/web-pixels@05c62d7ewbe538af9pdeb4fec1me339d55a/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://tnuck.com/web-pixels@05c62d7ewbe538af9pdeb4fec1me339d55a/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://tnuck.com/web-pixels@05c62d7ewbe538af9pdeb4fec1me339d55a/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://tnuck.com/web-pixels@05c62d7ewbe538af9pdeb4fec1me339d55a/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://tnuck.com/web-pixels@05c62d7ewbe538af9pdeb4fec1me339d55a/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://tnuck.com/web-pixels@05c62d7ewbe538af9pdeb4fec1me339d55a/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://tnuck.com/web-pixels@05c62d7ewbe538af9pdeb4fec1me339d55a/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=37f6f79d-338d-44c1-95c3-086260beb0cb&u_scsid=a…")
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
4 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 4 <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.
C
Form Accessibility
Action
8 of 43 controls have issues
REVIEW
8 of 43 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">
Info::
35 control(s) properly labeled
43 controls
35 labeled
0 placeholder only
8 unlabeled
ControlTypeLabelMethod
#HeaderSearchMobilesearchSearchfor/id
#CA-hamburger-menuradioCanada($CAD)for/id
#US-hamburger-menuradioUnited States($USD)for/id
#HeaderSearchDesktopsearchSearchfor/id
#CA-headerradioCanada($CAD)for/id
#US-headerradioUnited States($USD)for/id
#menu--CustomerServicecheckboxCustomer Servicefor/id
#menu--AboutuscheckboxAbout usfor/id
#FooterNewsletterEmailemailEmail Addressfor/id
#CA-footerradioCanada($CAD)for/id
#US-footerradioUnited States($USD)for/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
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

A
Landmark Structure
18 landmarks
PASS
18 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.
Info::
Skip navigation link present
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

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 Input Types
43 form control(s) checked, no type mismatches
PASS
43 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A
Form Input Quality
1 input-semantic issue(s) across 43 form control(s)
PASS
1 input-semantic issue(s) across 43 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+
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+
Mobile-Readable Font Sizes
All 19 visible text node(s) render at >= 12 CSS pixels
PASS
All 19 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.
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 The Thanksgiving
S…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 PART21.00:13.0:1
#000000
#FFFFFF
Pass
h2 WEATHER21.00:13.0:1
#000000
#FFFFFF
Pass
h2 SPORT21.00:13.0:1
#000000
#FFFFFF
Pass
h2 HOME21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Tuckernuck Editorial…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Hi, We're Tuckernuck21.00:13.0:1
#000000
#FFFFFF
Pass
h2 We Design & Curate21.00:13.0:1
#000000
#FFFFFF
Pass
h2 For a Fun-Filled Lif…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Want in on newness, …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Free Shipping, Retur…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Your Shopping Bag is…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Account21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Join or Sign In to V…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Recently Viewed21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Make these favorites…21.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

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 91/100 — 3 failing, 26 passed
PASS
91

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
STYLE div.swiper-wrapper > div.swiper-slide > a.no-underline > span.h7--medium
TRAVEL div.swiper-wrapper > div.swiper-slide > a.no-underline > span.h7--medium
WEDDING div.swiper-wrapper > div.swiper-slide > a.no-underline > span.h7--medium
HOME div.swiper-wrapper > div.swiper-slide > a.no-underline > span.h7--medium
GUEST EDITOR div.swiper-wrapper > div.swiper-slide > a.no-underline > span.h7--medium
ENTERTAIN div.swiper-wrapper > div.swiper-slide > a.no-underline > span.h7--medium
FIND THE FUN div.swiper-wrapper > div.swiper-slide > a.no-underline > span.h7--medium

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#Block--ATHBFeW5qQ21adHhyV__full_bleed_image_image_i3XDf9 > picture > img.w-full div.relative > div#Block--ATHBFeW5qQ21adHhyV__full_bleed_image_image_i3XDf9 > picture > img.w-full
div.relative > div#Block--AbWs0dlFYR2dnUmV0Y__full_bleed_image_image_9cQUyf > picture > img.w-full div.relative > div#Block--AbWs0dlFYR2dnUmV0Y__full_bleed_image_image_9cQUyf > picture > img.w-full
div.relative > div#Block--AVklnbXpBamp5UlVGM__full_bleed_image_image_TMNmNB > picture > img.w-full div.relative > div#Block--AVklnbXpBamp5UlVGM__full_bleed_image_image_TMNmNB > picture > img.w-full
div.relative > div#Block--AWVArOGJMZzNRRXQ5R__full_bleed_image_image_cyQqYN > picture > img.w-full div.relative > div#Block--AWVArOGJMZzNRRXQ5R__full_bleed_image_image_cyQqYN > picture > img.w-full
div.relative > div#Block--AZ2lUakJNdGw0eU5FT__full_bleed_image_image_DywXxT > picture > img.w-full div.relative > div#Block--AZ2lUakJNdGw0eU5FT__full_bleed_image_image_DywXxT > picture > img.w-full
div.swiper-slide > a.no-underline > picture > img.w-full div.swiper-slide > a.no-underline > picture > img.w-full
div.swiper-slide > a.no-underline > picture > img.w-full div.swiper-slide > a.no-underline > picture > img.w-full
div.swiper-slide > a.no-underline > picture > img.w-full div.swiper-slide > a.no-underline > picture > img.w-full
div.swiper-slide > a.no-underline > picture > img.w-full div.swiper-slide > a.no-underline > picture > img.w-full
div.swiper-slide > a.no-underline > picture > img.w-full div.swiper-slide > a.no-underline > picture > img.w-full
div.swiper-slide > a.no-underline > picture > img.w-full div.swiper-slide > a.no-underline > picture > img.w-full
div.swiper-slide > a.no-underline > picture > img.w-full div.swiper-slide > a.no-underline > picture > img.w-full
div.swiper-slide > a.no-underline > picture > img.w-full div.swiper-slide > a.no-underline > picture > img.w-full
div.swiper-slide > a.no-underline > picture > img.w-full div.swiper-slide > a.no-underline > picture > 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.

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
Go to my shopping bag 0 div.flex > div.header__right > div.relative > button#miniCartToggle
○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
●Form elements have associated labels
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links have a discernible name
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Image elements do not have `[alt]` attributes that are redundant text.
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○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
○ARIA IDs are unique
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○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
○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