Skip to content
https://shopnoble.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
62
GRADE
D
FIX
11
REVIEW
3
PASS
10
INFO
0
Checks
24
10 PASS 3 REVIEW 11 FIX
F
Heading Hierarchy
Action
29 headings, 2 skip(s)
FIX
29 headings, 2 skip(s)
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
9 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H2 We value your privacy
  • H1 Noble
  • H2 BEST SELLERS
  • H2 New Arrivals
  • H2 Knitwear
  • H2 AS SEEN IN:
  • H2 SHOP THE LOOK
  • H2 Account
  • H2 (empty)
  • H2 Sign in to your account
  • 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
  • H1 YOUR 10% OFF duplicate H1

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

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

Why this matters

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

Learn more ▾

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

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

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

Why this matters

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

Learn more ▾

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

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

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
11 of 101 images have issues
FIX
11 of 101 images have issues
Critical::
10 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
7 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Warning::
1 image(s) with generic alt text
Info::
14 decorative image(s) correctly marked
Info::
76 image(s) with good alt text
101 images 76 good alt text 14 decorative 1 generic 10 missing
IssueCount
missing10 image(s)
generic1 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
12/14 eligible field(s) missing autocomplete or inputmode
FIX
12/14 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">, <input type="email" name="contact[email]" id="input--sections--21130390765706__newsletter_yATbng--contactemail">, <input type="email">, <input type="email" name="customer[email]">, <input type="number" id="rivo_transfer_credit_amount">
D
Tabindex Anti-Patterns
Action
0 positive, 18 -1-on-focusable
FIX
0 positive, 18 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <button id="accessiblyAppDialogButton">
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.)
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.)
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
2 icon(s) detected
FIX
2 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
D
Web Manifest
Action
Not found
FIX
Not found
Info::
No web manifest found
No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark ModeNo Dark Mode Detected
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
No print-specific styles detected
When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.
Print Stylesheet No Print Styles
Print stylesheet Not found ✗Inline @media print Not detected ✗
F
Navigation UX
Action
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
2 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 2 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Form Accessibility
Action
8 of 63 controls have issues
REVIEW
8 of 63 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::
55 control(s) properly labeled
63 controls
55 labeled
0 placeholder only
8 unlabeled
ControlTypeLabelMethod
#accessibly-app-language-searchinputSearch languagearia-label
qsearchSearcharia-label
#option-value--template--21130394796170__featured-collections--swatch--template--21130394796170__featured-collections-8847583871114-1-chocolate-plaidradioChocolate Plaidfor/id
#option-value--template--21130394796170__featured-collections--swatch--template--21130394796170__featured-collections-9214994481290-1-paprikaradioPaprikafor/id
#option-value--template--21130394796170__featured-collections--swatch--template--21130394796170__featured-collections-8849198448778-1-chocolate-plaidradioChocolate Plaidfor/id
#option-value--template--21130394796170__featured-collections--swatch--template--21130394796170__featured-collections-8848859758730-1-chocolate-plaidradioChocolate Plaidfor/id
#option-value--template--21130394796170__featured-collections--swatch--template--21130394796170__featured-collections-8868046471306-1-ashradioAshfor/id
#option-value--template--21130394796170__featured-collections--swatch--template--21130394796170__featured-collections-8843602100362-1-chocolate-plaidradioChocolate Plaidfor/id
#option-value--template--21130394796170__featured-collections--swatch--template--21130394796170__featured-collections-8847625748618-1-fawnradioFawnfor/id
#option-value--template--21130394796170__featured-collections--swatch--template--21130394796170__featured-collections-9021033414794-1-ashradioAshfor/id
#option-value--template--21130394796170__featured_collections_nMJYVw--swatch--template--21130394796170__featured_collections_nMJYVw-9133215318154-1-cobaltradioCobaltfor/id
#option-value--template--21130394796170__featured_collections_nMJYVw--swatch--template--21130394796170__featured_collections_nMJYVw-9133205356682-1-ashradioAshfor/id
#option-value--template--21130394796170__featured_collections_nMJYVw--swatch--template--21130394796170__featured_collections_nMJYVw-8923390574730-1-cobaltradioCobaltfor/id
#option-value--template--21130394796170__featured_collections_nMJYVw--swatch--template--21130394796170__featured_collections_nMJYVw-8681789522058-1-chocolateradioChocolatefor/id
#option-value--template--21130394796170__featured_collections_nMJYVw--swatch--template--21130394796170__featured_collections_nMJYVw-8868046471306-1-ashradioAshfor/id
#option-value--template--21130394796170__featured_collections_nMJYVw--swatch--template--21130394796170__featured_collections_nMJYVw-8681761210506-1-oat-milkradioOat Milkfor/id
#option-value--template--21130394796170__shop_the_look_tfjMFp--swatch-mobile-look_ihV7yr-template--21130394796170__shop_the_look_tfjMFp-8645263786122-1-boneradioBonefor/id
#option-value--template--21130394796170__shop_the_look_tfjMFp--swatch-mobile-look_ihV7yr-template--21130394796170__shop_the_look_tfjMFp-9029851611274-1-chocolateradioChocolatefor/id
#option-value--template--21130394796170__shop_the_look_tfjMFp--swatch-mobile-look_aeaMwY-template--21130394796170__shop_the_look_tfjMFp-8357652136074-1-bordeauxradioBordeauxfor/id
#option-value--template--21130394796170__shop_the_look_tfjMFp--swatch-mobile-look_aeaMwY-template--21130394796170__shop_the_look_tfjMFp-9133215318154-1-cobaltradioCobaltfor/id
#option-value--template--21130394796170__shop_the_look_tfjMFp--swatch-mobile-look_pwJMCC-template--21130394796170__shop_the_look_tfjMFp-8848845504650-1-oliveradioOlivefor/id
#option-value--template--21130394796170__shop_the_look_tfjMFp--swatch-mobile-look_pwJMCC-template--21130394796170__shop_the_look_tfjMFp-8306085232778-1-oliveradioOlivefor/id
#option-value--template--21130394796170__shop_the_look_tfjMFp--swatch-mobile-look_pwJMCC-template--21130394796170__shop_the_look_tfjMFp-8868046471306-1-ashradioAshfor/id
#option-value--template--21130394796170__shop_the_look_tfjMFp--swatch-desktop-look_ihV7yr-template--21130394796170__shop_the_look_tfjMFp-8645263786122-1-boneradioBonefor/id
#option-value--template--21130394796170__shop_the_look_tfjMFp--swatch-desktop-look_ihV7yr-template--21130394796170__shop_the_look_tfjMFp-9029851611274-1-chocolateradioChocolatefor/id
#option-value--template--21130394796170__shop_the_look_tfjMFp--swatch-desktop-look_aeaMwY-template--21130394796170__shop_the_look_tfjMFp-8357652136074-1-bordeauxradioBordeauxfor/id
#option-value--template--21130394796170__shop_the_look_tfjMFp--swatch-desktop-look_aeaMwY-template--21130394796170__shop_the_look_tfjMFp-9133215318154-1-cobaltradioCobaltfor/id
#option-value--template--21130394796170__shop_the_look_tfjMFp--swatch-desktop-look_pwJMCC-template--21130394796170__shop_the_look_tfjMFp-8848845504650-1-oliveradioOlivefor/id
#option-value--template--21130394796170__shop_the_look_tfjMFp--swatch-desktop-look_pwJMCC-template--21130394796170__shop_the_look_tfjMFp-8306085232778-1-oliveradioOlivefor/id
#option-value--template--21130394796170__shop_the_look_tfjMFp--swatch-desktop-look_pwJMCC-template--21130394796170__shop_the_look_tfjMFp-8868046471306-1-ashradioAshfor/id
#input--sections--21130390765706__newsletter_yATbng--contactemailemailEnter Your Email Addressfor/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

B
Tap Target Adequacy
3 tap target(s) too small or too close together
REVIEW
3 tap target(s) too small or too close together
Info::
3 tap target(s) too small or too close to neighbors
WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.
C
Mobile-Readable Font Sizes
Action
80% of visible text renders at >= 12 CSS px (3 below threshold)
REVIEW
80% of visible text renders at >= 12 CSS px (3 below threshold)
Warning::
3 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> 9.0px ("Previous"); <span> 11.0px ("FREE SHIPPING ON US ORDERS $200+"); <span> 9.0px ("Next").
A+
Landmark Structure
24 landmarks
PASS
24 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Primary navigation" MAIN ASIDE "Accessibility Tools" CONTENTINFO footer
A+
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
4 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: 4 all-caps heading(s)
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 "accessibly-app-language-search" should use type="search" (currently type="text")
Field name "accessibly-app-language-search" 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 63 form control(s)
PASS
1 input-semantic issue(s) across 63 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
Iframe Accessibility
1/1 iframe(s) missing title; 0 placeholder(s)
PASS
1/1 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.
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 We value your privac…18.27:13.0:1
#000000
#F4EFE0
Pass
h2 BEST SELLERS18.27:13.0:1
#000000
#F4EFE0
Pass
h2 New Arrivals18.27:13.0:1
#000000
#F4EFE0
Pass
h2 Knitwear18.27:13.0:1
#000000
#F4EFE0
Pass
h2 AS SEEN IN:18.27:13.0:1
#000000
#F4EFE0
Pass
h2 SHOP THE LOOK18.27:13.0:1
#000000
#F4EFE0
Pass
h2 Account18.27:13.0:1
#000000
#F4EFE0
Pass
h2 Sign in to your acco…18.27:13.0:1
#000000
#F4EFE0
Pass
h2 Recently viewed18.27:13.0:1
#000000
#F4EFE0
Pass
h2 Favorites18.27:13.0:1
#000000
#F4EFE0
Pass
h2 Popular Today18.27:13.0:1
#000000
#F4EFE0
Pass
h2 Your Orders18.27:13.0:1
#000000
#F4EFE0
Pass
h2 My preferences18.27:13.0:1
#000000
#F4EFE0
Pass
h2 My addresses18.27:13.0:1
#000000
#F4EFE0
Pass
h3 Collections18.27:13.0:1
#000000
#F4EFE0
Pass
h3 All Favorites18.27:13.0:1
#000000
#F4EFE0
Pass
title Noble: Sustainably M…18.27:14.5:1
#000000
#F4EFE0
Pass
span Back18.27:14.5:1
#000000
#F4EFE0
Pass
div Accessibility option…18.27:14.5:1
#000000
#F4EFE0
Pass
p Are you sure you wan…18.27:14.5:1
#000000
#F4EFE0
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 93/100 — 2 failing, 28 passed
PASS
93

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

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
Close 🍪 Cookie policy We use cookies and similar technologies to provide the … body.features--button-transition > aside#shopify-section-sections--21130391847050__privacy-banner > privacy-banner.pop-in

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.

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 item 1 div.container > div.v-stack > carousel-navigation.page-dots > button.tap-area
Go to item 2 div.container > div.v-stack > carousel-navigation.page-dots > button.tap-area
Go to item 3 div.container > div.v-stack > carousel-navigation.page-dots > button.tap-area

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●Form elements have associated labels
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●`button`, `link`, and `menuitem` elements have accessible names
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●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.
●Links have a discernible name
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Uses ARIA roles only on compatible elements
●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
○`[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
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○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.
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback