Public accessibility assessment

Accessibility issues detected on sourceunknown.com

Evolize inspected 5 public pages on sourceunknown.com and detected 58 automatically identifiable accessibility findings.

58Findings detected
7WCAG criteria affected
5Pages inspected
9 Sep 2026Assessment date

Highest detected severity: High · 8 high-priority findings · 100% inspected-page coverage

Most widespread issueInteractive controls are not keyboard-accessibleDetected on 5 inspected pages
Most affected page/products/knot-top-grey40 findings detected
Most represented WCAG criterionWCAG 1.4.3 — Contrast (Minimum)39 detected findings

Is sourceunknown.com your website?

Keep this assessment current and get notified when new accessibility issues are detected.

https://

Not your website? Scan your own site →

01 · Accessibility summary

Evolize inspected 5 public pages on sourceunknown.com and detected 58 accessibility findings. The most widespread issue was "Interactive controls are not keyboard-accessible", detected on 5 inspected pages. The most affected inspected page was "/products/knot-top-grey", where 40 findings were detected. The assessment identified findings mapped to 7 WCAG success criterions. The sections below prioritize the broadest issues and provide technical evidence for each detected finding.

02 · Start here

These findings combine the highest severity and broadest reach detected during this assessment.

  1. High

    Interactive controls are not keyboard-accessible

    WCAG 2.1.1 (A) · 5 inspected pages · 75 instances
    Why this matters

    A control that responds to clicks (a clickable element or an ARIA widget) cannot receive keyboard focus, so keyboard and switch users cannot operate it.

    Recommended action

    Use a native <button>/<a>, or add tabindex="0" plus keyboard event handlers (Enter/Space) to custom controls.

    View technical evidence →
  2. High

    Hidden elements can still receive keyboard focus

    WCAG 2.4.3 (A) · 5 inspected pages · 20 instances
    Why this matters

    An element is not visible but remains in the tab order, so a sighted keyboard user loses track of focus when it lands there.

    Recommended action

    Keep this element out of the tab order while its containing region is hidden — remove it from focus (for example tabindex="-1"), or apply the inert attribute to the hidden container where supported. Restore normal focusability when the region becomes visible.

    View technical evidence →
  3. High

    Hidden elements can still receive keyboard focus

    WCAG 2.4.3 (A) · 5 inspected pages · 10 instances
    Why this matters

    An element is not visible but remains in the tab order, so a sighted keyboard user loses track of focus when it lands there.

    Recommended action

    Keep this element out of the tab order while its containing region is hidden — remove it from focus (for example tabindex="-1"), or apply the inert attribute to the hidden container where supported. Restore normal focusability when the region becomes visible.

    View technical evidence →
  4. High

    Hidden elements can still receive keyboard focus

    WCAG 2.4.3 (A) · 5 inspected pages · 5 instances
    Why this matters

    An element is not visible but remains in the tab order, so a sighted keyboard user loses track of focus when it lands there.

    Recommended action

    Keep this element out of the tab order while its containing region is hidden — remove it from focus (for example tabindex="-1"), or apply the inert attribute to the hidden container where supported. Restore normal focusability when the region becomes visible.

    View technical evidence →
  5. High

    Hidden elements can still receive keyboard focus

    WCAG 2.4.3 (A) · 5 inspected pages · 5 instances
    Why this matters

    An element is not visible but remains in the tab order, so a sighted keyboard user loses track of focus when it lands there.

    Recommended action

    Keep this element out of the tab order while its containing region is hidden — remove it from focus (for example tabindex="-1"), or apply the inert attribute to the hidden container where supported. Restore normal focusability when the region becomes visible.

    View technical evidence →

03 · WCAG criteria affected

CriterionNameLevelFindingsPagesReach
1.4.3Contrast (Minimum)AA3955 / 5
2.4.3Focus OrderA755 / 5
1.3.1Info and RelationshipsA655 / 5
2.5.8Target Size (Minimum)AA455 / 5
2.1.1KeyboardA155 / 5
3.3.2Labels or InstructionsA111 / 5
4.1.2Name, Role, ValueA155 / 5

Absence of a criterion here does not indicate conformance with it — only that no automatically detectable issue was found for it.

Continuous monitoring

A scan shows today's exposure. Monitoring shows what changes next.

Evolize continuously reassesses public website pages, detects newly introduced or recurring accessibility findings, and tracks remediation over time.

04 · All detected findings

High

Hidden elements can still receive keyboard focus

WCAG 2.4.3 (A)50 instances5 inspected pages

An element is not visible but remains in the tab order, so a sighted keyboard user loses track of focus when it lands there.

Why it matters

An element is not visible but remains in the tab order, so a sighted keyboard user loses track of focus when it lands there.

Recommended correction

Keep this element out of the tab order while its containing region is hidden — remove it from focus (for example tabindex="-1"), or apply the inert attribute to the hidden container where supported. Restore normal focusability when the region becomes visible.

View 50 affected elements
Component · Ref AOIHD9
Affected pagehttps://sourceunknown.com/account/login
Elementbutton#md-form__select__language
Accessible nameLanguage
Rolecombobox
Markup
<button type="button" name="md-form__select__language__button" id="md-form__select__language" class="md-form__select" aria-expanded="false" aria-controls="orbeLanguageList" role="combobox" aria-haspopup="listbox" aria-labelledby="label-md-form__select__language" data-value="en" data-lenis-prevent="" data-lenis-prevent-wheel="" data-lenis-prevent-touch="">
        <div class="md-form__select__language__list-link-wrapper">
            <span class="md-form__select__span">English</span>
        </div>
    </button>
Affected pages/ /account/login /pages/contact /products/knot-top-grey /pages/terms-of-service
Component · Ref 95ODDJ
Affected pagehttps://sourceunknown.com/pages/contact
Elementa#notepad-anchor-title
Accessible nameMy Wishlist
Markup
<a href="#swym-wishlist" class="swym-background-color" id="notepad-anchor-title" aria-label="My Wishlist" data-swym-loaded="true"><i class="swym-icon swym-notepad-white"></i>My Wishlist</a>
Affected pages/ /account/login /pages/contact /products/knot-top-grey /pages/terms-of-service
Component · Ref LEX15O
Affected pagehttps://sourceunknown.com/account/login
Elementdiv#search--search-popup > div > div:nth-of-type(2) > ul > li:nth-of-type(2) > button
Accessible nameLeather
Markup
<button data-search-suggest="Leather" type="button">Leather</button>
Affected pages/ /account/login /pages/contact /products/knot-top-grey /pages/terms-of-service
Component · Ref HHUV8R
Affected pagehttps://sourceunknown.com/account/login
Elementdiv#shopify-section-bag > section > div > div:nth-of-type(1) > button
Accessible nameclose
Markup
<button data-close-bag="" type="button" aria-label="close" class="btn bag-box-head-btn">
        <span>CLOSE</span>
      </button>
Affected pages/ /account/login /pages/contact /products/knot-top-grey /pages/terms-of-service
Component · Ref L8R071
Affected pagehttps://sourceunknown.com/pages/contact
Elementdiv#search--search-popup > div > div:nth-of-type(1) > button
Accessible nameclose
Markup
<button aria-label="close" style="width:auto;" data-close-search="" type="button">
        <span>CLOSE</span>
      </button>
Affected pages/ /account/login /pages/contact /products/knot-top-grey /pages/terms-of-service
Component · Ref HYHV9P
Affected pagehttps://sourceunknown.com/account/login
Elementdiv#shopify-section-header-new > header > div:nth-of-type(2) > div:nth-of-type(1) > button
Accessible nameclose navigation menu
Markup
<button data-button-action="close_mob_menu" type="button" aria-label="close navigation menu">
        <span style="top: 2px;position: relative;">CLOSE</span>
      </button>
Affected pages/ /account/login /pages/contact /products/knot-top-grey /pages/terms-of-service
High

Interactive controls are not keyboard-accessible

WCAG 2.1.1 (A)75 instances5 inspected pages

A control that responds to clicks (a clickable element or an ARIA widget) cannot receive keyboard focus, so keyboard and switch users cannot operate it.

Why it matters

A control that responds to clicks (a clickable element or an ARIA widget) cannot receive keyboard focus, so keyboard and switch users cannot operate it.

Recommended correction

Use a native <button>/<a>, or add tabindex="0" plus keyboard event handlers (Enter/Space) to custom controls.

View 75 affected elements
Component · Ref IHU563
Affected pagehttps://sourceunknown.com/
Elementli#orbe-country-AI
Accessible nameAnguilla
Roleoption
Markup
<li id="orbe-country-AI" tabindex="-1" role="option" data-name="Anguilla" data-country="AI" style="display: list-item;">
                    <span class="md-form__select__country__list-link" data-countryname="Anguilla" data-primarymarket="false" data-currency="XCD" data-symbol="$" data-primary="enabled" data-defaultlocale="en" data-subfoldersuffix="ai" data-domainurl="thesourceunknown.myshopify.com" data-host="sourceunknown.com" data-country="AI" data-value="AI" data-locales="en" data-namelocales="English" aria-current="false">
                        <div class="md-form__select__country__list…
Affected pages/ /account/login /pages/contact /products/knot-top-grey /pages/terms-of-service
High

Modal dialog does not trap keyboard focus

WCAG 2.4.3 (A)5 instances5 inspected pages

An open modal leaves the content behind it keyboard-focusable, so keyboard and screen reader users can tab out of the dialog into hidden page content.

Why it matters

An open modal leaves the content behind it keyboard-focusable, so keyboard and screen reader users can tab out of the dialog into hidden page content.

Recommended correction

While a modal is open, confine focus to the dialog and mark the rest of the page inert (or aria-hidden). Restore focus on close.

View 5 affected elements
Component · Ref PZZ9BS
Affected pagehttps://sourceunknown.com/pages/contact
Elementdiv#md-app-embed__modal > div:nth-of-type(1) > div
Accessible nameSelect your country
Roledialog
Markup
<div class="md-modal__dialog" role="dialog" aria-modal="true" aria-labelledby="label-md-modal__dialog" tabindex="-1">
                <div class="md-modal__content notranslate" data-wg-notranslate=""><form method="post" action="/localization" id="md-modal__form__id" accept-charset="UTF-8" class="" enctype="multipart/form-data"><input type="hidden" name="form_type" value="localization"><input type="hidden" name="utf8" value="✓"><input type="hidden" name="_method" value="put"><input type="hidden" name="return_to" value="/pages/contact">
                    <div class="md-modal__grid">
          …
Affected pages/ /account/login /pages/contact /products/knot-top-grey /pages/terms-of-service
Medium

ARIA attributes have invalid values

WCAG 4.1.2 (A)5 instances5 inspected pages

ARIA attributes reference ids that do not exist or hold invalid values, breaking the accessibility tree.

Why it matters

ARIA attributes reference ids that do not exist or hold invalid values, breaking the accessibility tree.

Recommended correction

Correct ARIA attribute values and ensure referenced ids exist in the DOM.

View 5 affected elements
Component · Ref VGCA1A
Affected pagehttps://sourceunknown.com/pages/terms-of-service
Element#md-form__select__country
Accessible nameCountry
Rolecombobox
Markup
<button type="button" name="md-form__select__cou..." id="md-form__select__cou..." role="combobox" aria-haspopup="listbox" aria-labelledby="label-md-form__count..." class="md-form__select" aria-expanded="false" aria-controls="orbeCountryList" data-value="US" data-lenis-prevent="" ...>
Affected pages/ /account/login /pages/contact /products/knot-top-grey /pages/terms-of-service
Medium

Text has insufficient colour contrast

WCAG 1.4.3 (AA)171 instances5 inspected pages

Text and background colours do not meet the minimum contrast ratio, reducing legibility.

Why it matters

Text and background colours do not meet the minimum contrast ratio, reducing legibility.

Recommended correction

Increase the contrast ratio to at least 4.5:1 for normal text and 3:1 for large text.

View 171 affected elements
Component · Ref HZMYYG
Affected pagehttps://sourceunknown.com/pages/terms-of-service
Element.md-orbe-country-selector-span
Accessible nameUnited States
Markup
<span class="md-orbe-country-selector-span orbe__span-AK2ZOdzcyR1hxRGtNN__orbe_geolocation_app_block_custom_button_KJT3cU">United States</span>
Affected pages/ /account/login /pages/contact /products/knot-top-grey /pages/terms-of-service
Component · Ref VYFVPP
Affected pagehttps://sourceunknown.com/pages/contact
Element.col:nth-child(1) > nav > ul > li:nth-child(3) > a
Accessible nameStockist
Markup
<a href="https://sourceunknown.com/pages/stockist">Stockist</a>
Affected pages/ /account/login /pages/contact /products/knot-top-grey /pages/terms-of-service
Component · Ref HDM3WG
Affected pagehttps://sourceunknown.com/pages/terms-of-service
Element.md-orbe-custom-selector
Accessible nameGeolocation Button: United States shipping to United States
Markup
<button type="button" class="md-orbe-custom-selec..." onclick="mdAppCustomButtonCli...">
Affected pages/ /account/login /pages/contact /products/knot-top-grey /pages/terms-of-service
Component · Ref Q902HR
Affected pagehttps://sourceunknown.com/products/knot-top-grey
Element.has-sub-menu:nth-child(4) > a[href="javascript:void(0)"]
Accessible nameEDIT
Markup
<a href="javascript:void(0)">EDIT</a>
Affected pages/ /account/login /pages/contact /products/knot-top-grey /pages/terms-of-service
Component · Ref ME3HCW
Affected pagehttps://sourceunknown.com/
Element.col:nth-child(3) > nav > ul > li:nth-child(1)
Accessible nameJOIN US
Markup
<li>
                  
                    JOIN US
                  
                </li>
Affected pages/ /account/login /pages/contact /products/knot-top-grey /pages/terms-of-service
Component · Ref ROOL9G
Affected pagehttps://sourceunknown.com/
Elementbutton[data-open-search=""] > span
Accessible nameSearch
Markup
<span>Search</span>
Affected pages/ /account/login /pages/contact /products/knot-top-grey /pages/terms-of-service
Component · Ref F442Y7
Affected pagehttps://sourceunknown.com/
Element.bot > ul > li
Accessible name© SourceUnknown 2026
Markup
<li>
        ©&nbsp;<a href="/" title="" class="current-route">SourceUnknown</a>&nbsp;2026
      </li>
Affected pages/ /account/login /pages/contact /products/knot-top-grey /pages/terms-of-service
Component · Ref TLOHTJ
Affected pagehttps://sourceunknown.com/products/knot-top-grey
Element#md-form__select__country > .md-form__select__country__list-link-wrapper > .md-form__select__span
Accessible nameUnited States
Markup
<span class="md-form__select__span">United States</span>
Affected pages/ /account/login /pages/contact /products/knot-top-grey /pages/terms-of-service
Component · Ref C8C7UO
Affected pagehttps://sourceunknown.com/pages/contact
Element.scroll-trigger--offscreen.rich-text__text.rte > p > span
Accessible name[email removed]
Markup
<span style="text-decoration:underline">[email removed]</span>
Component · Ref PHW91M
Affected pagehttps://sourceunknown.com/pages/contact
Element.scroll-trigger--offscreen.rich-text__heading.inline-richtext
Accessible nameWHOLESALE INQUIRY
Markup
<h2 class="rich-text__heading rte inline-richtext h2 scroll-trigger animate--slide-in scroll-trigger--offscreen" data-cascade="" style="--animation-order: 1;">
                WHOLESALE INQUIRY
              </h2>
Component · Ref DPMU0N
Affected pagehttps://sourceunknown.com/account/login
Element.password-action
Accessible nameShow
Markup
<span class="password-action show-password">Show</span>
Component · Ref 9BQZUQ
Affected pagehttps://sourceunknown.com/pages/contact
Element.scroll-trigger--offscreen.rich-text__text.rte > p
Accessible nameFOR WHOLESALE INQUIRY CONTACT US AT [email removed]
Markup
<p>FOR WHOLESALE INQUIRY CONTACT US AT&nbsp;<span style="text-decoration:underline">[email removed]</span></p>
Component · Ref PVI7BD
Affected pagehttps://sourceunknown.com/pages/terms-of-service
Elementli:nth-child(6) > a[href$="size-guide"]
Accessible nameSize Guide
Markup
<a href="/pages/size-guide">Size Guide</a>
Affected pages/products/knot-top-grey /pages/terms-of-service
Component · Ref ER4YFR
Affected pagehttps://sourceunknown.com/account/login
Elementspan[data-word="in"] > .char[data-char="i"]
Accessible namei
Markup
<span class="char" data-char="i" style="--char-index: 4;">i</span>
Affected pages/account/login /pages/contact
Component · Ref TMD3L
Affected pagehttps://sourceunknown.com/pages/contact
Element#ContactForm-name
Markup
<input class="field__input" autocomplete="name" type="text" id="ContactForm-name" name="contact[Name]" value="" placeholder="Name">
Component · Ref 59QFG7
Affected pagehttps://sourceunknown.com/products/knot-top-grey
Element.content > .content-details > .content-details-description > .p1:nth-child(5)
Accessible nameTie-front panel at waist
Markup
<p class="p1"><meta charset="utf-8">Tie-front panel at waist&nbsp;</p>
Component · Ref KL61QX
Affected pagehttps://sourceunknown.com/pages/contact
Element.char[data-char="t"]:nth-child(7)
Accessible namet
Markup
<span class="char" data-char="t" style="--char-index: 6;">t</span>
Component · Ref UQXLGN
Affected pagehttps://sourceunknown.com/products/knot-top-grey
Elementbutton[data-popup-open="SIZE GUIDE"]
Accessible nameSIZE GUIDE
Markup
<button data-popup-open="SIZE GUIDE" type="button">SIZE GUIDE</button>
Component · Ref 3PQ4UG
Affected pagehttps://sourceunknown.com/products/knot-top-grey
Element.content > .content-details > button[data-show-more-info=""][type="button"]
Accessible nameRead more info
Markup
<button data-show-more-info="" :aria-label="Read more info" type="button">Read more info</button>
Component · Ref DJDGP0
Affected pagehttps://sourceunknown.com/pages/contact
Element#ContactForm-body
Markup
<textarea rows="10" id="ContactForm-body" class="text-area field__input" name="contact[Comment]" placeholder="Comment"></textarea>
Component · Ref UNES47
Affected pagehttps://sourceunknown.com/
Elementa[title=""]
Accessible nameSourceUnknown
Markup
<a href="/" title="" class="current-route">SourceUnknown</a>
Component · Ref V5BDV3
Affected pagehttps://sourceunknown.com/account/login
Element.sub-title > div:nth-child(2)
Accessible nameUPDATES, sales, special offers and more
Markup
<div>UPDATES, sales, special offers and more</div>
Component · Ref 8NSQ3L
Affected pagehttps://sourceunknown.com/products/knot-top-grey
Element.price__container:nth-child(1) > .price__regular > .price-item.price-item--regular
Accessible name115 USD
Markup
<span class="price-item price-item--regular">
            115 USD
          </span>
Component · Ref D9A9UA
Affected pagehttps://sourceunknown.com/products/knot-top-grey
Element.content > .content-details > .content-details-title
Accessible nameDetails
Markup
<div class="content-details-title">Details</div>
Component · Ref NHB0F6
Affected pagehttps://sourceunknown.com/products/knot-top-grey
Element.content > .content-details > .content-details-description > .p1:nth-child(11) > .s1
Accessible name5ft 6" (173cm)
Markup
<span class="s1">5ft 6" (173cm) </span>

Showing 25 representative examples · 14 more affected elements not shown

Medium

Content sits outside any landmark region

WCAG 1.3.1 (A)5 instances5 inspected pages

Meaningful content is not contained in a landmark (header/nav/main/footer/aside), so assistive-technology users cannot reach it via landmark navigation.

Why it matters

Meaningful content is not contained in a landmark (header/nav/main/footer/aside), so assistive-technology users cannot reach it via landmark navigation.

Recommended correction

Wrap primary content in <main> and other regions in appropriate landmark elements.

View 5 affected elements
Component · Ref LTCKT0
Affected pagehttps://sourceunknown.com/pages/contact
Elementdiv#shopify-section-bag > section > div
Accessible nameBag (0) CLOSE Your shopping bag is empty
Markup
<div class="bag-box ">
    <div class="bag-box-head">
      <div class="bag-box-head-name">
        Bag (<span class="bag-box-head-count">0</span>)
      </div>
      <button data-close-bag="" type="button" aria-label="close" class="btn bag-box-head-btn">
        <span>CLOSE</span>
      </button>
    </div>
    
    
      <div class="bag-box-empty">
        Your shopping bag is empty
      </div>
    
  </div>
Affected pages/ /account/login /pages/contact /products/knot-top-grey /pages/terms-of-service
Medium

Navigation regions are not distinguishable

WCAG 1.3.1 (A)27 instances5 inspected pages

The page has multiple navigation landmarks but they lack accessible names, so screen reader users cannot tell them apart.

Why it matters

The page has multiple navigation landmarks but they lack accessible names, so screen reader users cannot tell them apart.

Recommended correction

Give each navigation region a distinct aria-label (e.g. "Primary", "Footer") when more than one is present.

View 27 affected elements
Component · Ref A0Z6DY
Affected pagehttps://sourceunknown.com/
Elementdiv#shopify-section-footer-new > footer > div:nth-of-type(2) > div:nth-of-type(3) > nav
Accessible nameJOIN US Instagram TikTok
Markup
<nav>
              <ul>
                <li>
                  
                    JOIN US
                  
                </li>
                
                  
                    <li>
                      
                        <a href="https://www.instagram.com/sourceunknown_official">Instagram</a>
                      
                    </li>
                  
                    <li>
                      
                        <a href="https://www.tiktok.com/@sourceunknown.official">TikTok</a>
                      
                    </li>
                  
         …
Affected pages/ /account/login /pages/contact /products/knot-top-grey /pages/terms-of-service
Component · Ref TZF82M
Affected pagehttps://sourceunknown.com/pages/terms-of-service
Elementdiv#shopify-section-header-new > header > div:nth-of-type(1) > nav
Accessible nameNew New Arrivals Signature Collection Waitlist Shop CLOTHING Outerwear Knitwear Dresses & Jumpsuits Tops & Shirts Trousers & Shorts Denim Skirts Co-ord Sets Accessories Shoes Bags Gift Cards SALE Final Sale EDIT Looks
Markup
<nav data-lenis-prevent="">
        <ul>
          
            <li class="has-sub-menu">
              
                
                  <a href="javascript:void(0)">New</a>
                
              
              
                <div class="sub-menu">
                  
                    <div class="column ">
                      
                        <a class="h3 " href="/collections/new-in">New Arrivals</a>
                      
                      
                    </div>
                  
                    <div class="column ">
                      
             …
Affected pages/ /account/login /pages/contact /products/knot-top-grey /pages/terms-of-service
Component · Ref W14PV2
Affected pagehttps://sourceunknown.com/account/login
Elementdiv#shopify-section-template--22154908205314__main > div > div:nth-of-type(1) > nav
Accessible nameSign up Sign in Forgot password
Markup
<nav class="customer__nav">
    <ul class="list">
      <li class="">
        <a href="/account/register">
          <span class="regular-subtitle">Sign up</span>
        </a>
      </li>
      <li class="active regular-subtitle">
        <a href="/account/login" class="current-route">
          <span class="regular-subtitle">Sign in</span>
        </a>
      </li>
      <li class="recover regular-subtitle" onclick="clickRecover()">
        <a href="/account/login#recover">
          <span class="regular-subtitle">Forgot password</span>
        </a>
      </li>
    </ul>
  </nav>
Affected pages/account/login /pages/terms-of-service
Medium

Touch targets are too small

WCAG 2.5.8 (AA)30 instances5 inspected pages

Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.

Why it matters

Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.

Recommended correction

Increase this <a>'s rendered area to at least 24 × 24 CSS pixels, or provide sufficient spacing from adjacent targets. Prefer increasing padding on the existing control (for example the button or link) rather than adding a separate non-interactive wrapper.

View 30 affected elements
Component · Ref TEG6WK
Affected pagehttps://sourceunknown.com/pages/contact
Elementa[href$="size-guide"]
Accessible nameSize Guide
Markup
<a href="/pages/size-guide">Size Guide</a>
Affected pages/ /account/login /pages/contact /products/knot-top-grey /pages/terms-of-service
Component · Ref IDFYUE
Affected pagehttps://sourceunknown.com/products/knot-top-grey
Element.col:nth-child(1) > nav > ul > li:nth-child(3) > a
Accessible nameStockist
Markup
<a href="https://sourceunknown.com/pages/stockist">Stockist</a>
Affected pages/ /account/login /pages/contact /products/knot-top-grey /pages/terms-of-service
Component · Ref UEIBC2
Affected pagehttps://sourceunknown.com/pages/terms-of-service
Elementli:nth-child(2) > a[href$="shipping-update"]
Accessible nameShipping
Markup
<a href="/pages/shipping-update">Shipping</a>
Affected pages/products/knot-top-grey /pages/terms-of-service
Component · Ref REKJ51
Affected pagehttps://sourceunknown.com/pages/contact
Element.current-route
Accessible nameContact Us
Markup
<a class="current-route" href="/pages/contact">Contact Us</a>
Medium

Form fields use placeholder text as the only label

WCAG 1.3.1 (A)3 instances1 inspected page

Fields rely on placeholder text instead of a real label. The placeholder disappears once the user types, and it is not exposed as a programmatic label.

Why it matters

Fields rely on placeholder text instead of a real label. The placeholder disappears once the user types, and it is not exposed as a programmatic label.

Recommended correction

Add a persistent <label> associated with each field. Keep the placeholder for example text only, not as the label.

View 3 affected elements
Component · Ref XGOJX9
Affected pagehttps://sourceunknown.com/account/login
Elementinput#RecoverEmail
Markup
<input type="email" value="" name="email" id="RecoverEmail" autocorrect="off" autocapitalize="off" autocomplete="email" placeholder="Email address">
Low

Page has no level-one heading

WCAG 1.3.1 (A)1 instance1 inspected page

The page exposes no <h1>, so its topic is not conveyed in the heading structure.

Why it matters

The page exposes no <h1>, so its topic is not conveyed in the heading structure.

Recommended correction

Add a single descriptive <h1> that names the page's primary purpose.

View 1 affected element
Component · Ref WDZK1F
Affected pagehttps://sourceunknown.com/
Elementhtml > body
Accessible nameDuties & taxes included. T&C apply My Wishlist 0 Select your country Please confirm and change store preferences below Country United States Albania Algérie Andorra Angola Anguilla Antigua and Barbuda Argentina Armenia Aruba Australia Austria / Österreich Azerbaijan Bahamas Bahrain Bangladesh Barbados Belgium Belize Benin Bermuda Bhutan Bolivia …[truncated by Evolize: exceeded D1 value limit]
Markup
<body class="gradient wrapper orbe-country-code--US orbe-language-code--en-US orbe--opened scrollLock init hasWebp klaviyo-prevent-body-scrolling swym-ready swym-buttons-loaded" style="padding-bottom: 23px; overflow: hidden; padding-right: 0px;" data-preloaderend="true" ge-active="true"><div id="FreeShippingBanner" style="background-color: #333333;color: #FFFFFF;text-align: center;font-family: arial;padding: 4px;font-size: 12px;line-height: 30px;direction:ltr;" data-gem-ignore="">Duties &amp; taxes included. T&amp;C apply</div><div id="swym-plugin" class="swym-inject swym-ready">
             …

05 · Most affected inspected pages

06 · About this assessment

Evolize inspects publicly accessible website pages using automated browser-based testing and deterministic accessibility rules. Automated testing can identify many reproducible technical issues but cannot determine complete WCAG or legal compliance.

  • Publicly accessible surfaces only — no credentials, private systems, or source-code access.
  • Findings apply to the pages and states successfully inspected; automated analysis may not detect every issue.
  • Results reflect the site at the scan date and may have changed since.

Evolize provides digital risk intelligence and does not provide legal advice, certify compliance, or guarantee that litigation will not occur. Methodology · Security · Example assessment

07 · Continuous monitoring

This public report captures one assessment. Evolize monitoring rescans the website, detects new and recurring findings, tracks changes over time and verifies corrections.

Is information in this report inaccurate or outdated? Request a correction or removal.