EVOLIZEDIGITAL RISK INTELLIGENCE
RUN FREE ASSESSMENT
RUN FREE ASSESSMENT
Public accessibility assessment

Accessibility issues detected on tkees.com

Evolize inspected 5 public pages on tkees.com and detected 30 automatically identifiable accessibility findings.

30Findings detected
10WCAG criteria affected
5Pages inspected
7 Sep 2026Assessment date

Highest detected severity: Critical · 7 high-priority findings · 100% inspected-page coverage

Most widespread issueHidden elements can still receive keyboard focusDetected on 5 inspected pages
Most affected page/16 findings detected
Most represented WCAG criterionWCAG 1.4.3 — Contrast (Minimum)12 detected findings

Is tkees.com your website?

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

ACTIVATE MONITORINGRUN A FREE ASSESSMENT
https://

Not your website? Scan your own site →

01 · Accessibility summary

Evolize inspected 5 public pages on tkees.com and detected 30 accessibility findings. The most widespread issue was "Hidden elements can still receive keyboard focus", detected on 5 inspected pages. The most affected inspected page was "/", where 16 findings were detected. The assessment identified findings mapped to 10 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. Critical

    Links lack accessible text

    WCAG 2.4.4 (A) · 1 inspected page · 1 instance
    Why this matters

    Links expose no accessible name, so screen-reader users cannot determine their destination.

    Recommended action

    Add text to the link that describes its purpose, such as 'View Sale Items'. Alternatively, use the 'aria-label' attribute to provide a text description of the link's purpose.

    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

    To fix this issue, ensure that the element is either removed from the tab order or made visible when it receives keyboard focus. This can be achieved by adding a `tabindex=-1` attribute to the element when it is not visible, or by making sure that the element is displayed when it is focused.

    View technical evidence →
  3. 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

    To fix this issue, ensure that the element is removed from the tab order when it is not visible. This can be achieved by setting the 'tabindex' attribute to '-1' or by using JavaScript to remove the element from the DOM when it is not visible. Additionally, consider using the 'display: none' or 'visibility: hidden' CSS properties to hide the element when it is not intended to be interacted with.

    View technical evidence →
  4. High

    Modal dialog does not trap keyboard focus

    WCAG 2.4.3 (A) · 5 inspected pages · 5 instances
    Why this 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 action

    To fix this issue, ensure that the modal dialog traps keyboard focus by setting the `tabindex` attribute to `-1` on the dialog container and handling the `keydown` event to prevent focus from escaping the dialog. Additionally, consider using the `inert` attribute on the content behind the modal to prevent it from receiving keyboard focus.

    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

    To fix this issue, ensure that the element is either removed from the tab order or made visible when it receives focus. You can achieve this by adding a 'display: none;' or 'visibility: hidden;' style to the element when it's not visible, or by using JavaScript to dynamically update the element's 'tabindex' attribute to '-1' when it's not visible.

    View technical evidence →

03 · WCAG criteria affected

CriterionNameLevelFindingsPagesReach
1.4.3Contrast (Minimum)AA1222 / 5
2.4.3Focus OrderA855 / 5
2.1.1KeyboardA322 / 5
2.5.8Target Size (Minimum)AA311 / 5
1.1.1Non-text ContentA155 / 5
1.3.1Info and RelationshipsA111 / 5
2.2.2Pause, Stop, HideA111 / 5
2.4.4Link Purpose (In Context)A111 / 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.

ACTIVATE MONITORINGSEE PRICING

04 · All detected findings

High

Hidden elements can still receive keyboard focus

WCAG 2.4.3 (A)46 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

To fix this issue, ensure that the element is either removed from the tab order or made visible when it receives focus. You can achieve this by adding a 'display: none;' or 'visibility: hidden;' style to the element when it's not visible, or by using JavaScript to dynamically update the element's 'tabindex' attribute to '-1' when it's not visible.

View 46 affected elements
Component · Ref K6K0Q8
Affected pagehttps://tkees.com/products/gift-card
Elementdiv#shopify-section-header > div > a
Accessible namegeneral.navigation_menu.toggle_aria_label
Markup
<a href="#" class="header-shade mobile-nav-toggle" aria-label="general.navigation_menu.toggle_aria_label"></a>
Affected pages/ /pages/contact /products/gift-card /pages/wholesale-account-manager /cart
Component · Ref IAMS3P
Affected pagehttps://tkees.com/pages/contact
Elementdiv:nth-of-type(3) > div:nth-of-type(1) > div > ul > li:nth-of-type(2) > a:nth-of-type(1)
Accessible nameFOOTWEAR
Markup
<a href="/collections/all-footwear" class="navigation__link" aria-haspopup="true" aria-expanded="false" aria-controls="NavigationTier2-2-mob">FOOTWEAR</a>
Affected pages/ /pages/contact /products/gift-card /pages/wholesale-account-manager /cart
Component · Ref 1ECM5O
Affected pagehttps://tkees.com/cart
Elementbody > div:nth-of-type(3) > div:nth-of-type(1) > div > div:nth-of-type(1) > a:nth-of-type(2)
Accessible nameClose
Markup
<a href="#" class="mobile-nav-toggle" aria-label="Close"><svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="1.3" stroke-linecap="round" stroke-linejoin="round" class="feather feather-x" aria-hidden="true"><line x1="18" y1="6" x2="6" y2="18"></line><line x1="6" y1="6" x2="18" y2="18"></line></svg></a>
Affected pages/ /pages/contact /products/gift-card /pages/wholesale-account-manager /cart
Component · Ref 1I224Q
Affected pagehttps://tkees.com/pages/wholesale-account-manager
Elementhtml > body > a:nth-of-type(2)
Accessible nameToggle menu
Markup
<a href="#" class="page-shade" aria-label="Toggle menu"></a>
Affected pages/pages/contact /pages/wholesale-account-manager
Component · Ref JW7WVV
Affected pagehttps://tkees.com/pages/contact
Elementdiv#slidecarthq > div:nth-of-type(4) > header > button
Accessible nameClose cart
Markup
<button type="button" aria-label="Close cart"><svg aria-hidden="true" focusable="false" width="10" viewBox="0 0 10 10"><path d="M9.677 8.118a1.102 1.102 0 11-1.559 1.56L5 6.558 1.882 9.677a1.102 1.102 0 11-1.56-1.559L3.442 5 .323 1.882A1.102 1.102 0 111.882.322L5 3.442 8.118.323a1.102 1.102 0 111.56 1.559L6.558 5l3.118 3.118z" fill="#A1A1A1" fill-rule="nonzero"></path></svg></button>
Affected pages/pages/contact /pages/wholesale-account-manager
Component · Ref 7T7FQO
Affected pagehttps://tkees.com/
Elementdiv > div > div > div > div:nth-of-type(3) > a
Accessible namePout
Markup
<a href="/products/lily-nudes-pout" class=" cstm_colors metafieldProductsTitle" data-current-title=" Pout" title=" Pout" data-product-link-position="4" data-impression-id="d3722327-d75c-481c-ade5-3225c49b7069" data-product-click-tracked="true">
                                  <span class="product-block-options__item  lazyload--manual" data-option-item="Pout" data-media="" data-swatch="pout">
                                  </span>
                                </a>
Affected pages/ /cart
Component · Ref IULW65
Affected pagehttps://tkees.com/products/gift-card
Elementinput#template--19655101907119__main-9245461649-card-value-selector-opt-3
Markup
<input class="opt-btn js-option" type="radio" name="template--19655101907119__main-9245461649-card-value-selector" id="template--19655101907119__main-9245461649-card-value-selector-opt-3" value="175 USD">
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

To fix this issue, ensure that the modal dialog traps keyboard focus by setting the `tabindex` attribute to `-1` on the dialog container and handling the `keydown` event to prevent focus from escaping the dialog. Additionally, consider using the `inert` attribute on the content behind the modal to prevent it from receiving keyboard focus.

View 5 affected elements
Component · Ref CK0AAJ
Affected pagehttps://tkees.com/pages/contact
Elementhtml > body > div:nth-of-type(12) > div > div:nth-of-type(2)
Accessible namePOPUP Form
Roledialog
Markup
<div role="dialog" aria-modal="true" aria-label="POPUP Form" class="needsclick  kl-private-reset-css-Xuajs1" style="display: flex; z-index: 90000; opacity: 0; position: fixed; left: 0px; top: 0px; width: 100%; height: 100%; justify-content: center; align-items: center; overflow: clip auto; background-color: rgba(248, 248, 248, 0.6); animation-timing-function: ease; animation-play-state: running; animation-iteration-count: 1; animation-fill-mode: both; animation-delay: 0.25s; animation-duration: 0.35s; animation-name: klaviyo-fadein;" data-kl-scroll-locking-modal="true"><div class="needsclick  …
Affected pages/ /pages/contact /products/gift-card /pages/wholesale-account-manager /cart
High

Interactive controls are not keyboard-accessible

WCAG 2.1.1 (A)2 instances2 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

To make this control accessible, ensure it can receive keyboard focus by adding a positive tabindex value or using a native HTML element that can receive focus, such as a button or anchor tag.

View 2 affected elements
Component · Ref 4TWRD1
Affected pagehttps://tkees.com/pages/contact
Elementli#contact_custom-dropdown-opt-0
Accessible nameSizing Test — Notify Me
Roleoption
Markup
<li class=" cc-select__option js-option" id="contact_custom-dropdown-opt-0" role="option" data-value="Sizing Test" aria-selected="true">
        <!-- this change is for add the inventory quantity side by side with the size /  START -->
        <span class="displaysizemessage">
          <div class="sizename">Sizing Test</div>
          <div class="sizemessage">
            
              <font color="#982F36">
                <label style="display:none;"> — </label>
                
                  Notify Me</font></div>
          <!-- this change is for add the inventory quantity side by si…
Component · Ref 7GWFV3
Affected pagehttps://tkees.com/products/gift-card
Elementdiv#bis-overlay
Accessible name× JOIN THE WAITLIST Digital Gift Card Please enter your email and select your size. We will let you know when your item becomes available. Select Size 60 USD 75 USD 100 USD 175 USD 250 USD Subscribe to our newsletter. GET NOTIFIED You're in! We'll let you know when it's back. Something went wrong. Please try again.
Markup
<div class="bis-overlay" id="bis-overlay" onclick="if(event.target===this)bisClose()">
  <div class="bis-modal">
    <button class="bis-modal__close" type="button" onclick="bisClose()">×</button>
    <h3 class="bis-modal__headline">JOIN THE WAITLIST</h3>
    <p class="bis-modal__product-name">Digital Gift Card</p>
    <p class="bis-modal__body">Please enter your email and select your size. We will let you know when your item becomes available.</p>

    <label class="bis-modal__label" for="bis-variant">Select Size</label>
    <select class="bis-modal__select" id="bis-variant"><option value="120…
Medium

ARIA attributes have invalid values

WCAG 4.1.2 (A)15 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

Verify that the aria-controls attribute references an existing element in the DOM and that the referenced element is a valid descendant of the element with the aria-haspopup attribute. Update the aria-controls value to match the id of the corresponding element, ensuring it exists and is properly nested.

View 15 affected elements
Component · Ref HNSK6X
Affected pagehttps://tkees.com/
Element.navigation--left > .navigation__tier-1-container > .navigation__tier-1 > .navigation__item--with-mega-menu.navigation__item--with-children.navigation__item:nth-child(3) > a[aria-controls="NavigationTier2-3"][href$="tk-clothing"][aria-haspopup="true"]
Accessible nameCLOTHING
Markup
<a href="/collections/tk-clothing" class="navigation__link" aria-haspopup="true" aria-expanded="false" aria-controls="NavigationTier2-3">CLOTHING</a>
Affected pages/ /pages/contact /products/gift-card /pages/wholesale-account-manager /cart
Medium

Text has insufficient colour contrast

WCAG 1.4.3 (AA)19 instances2 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

To improve readability, consider adjusting the text or background color to meet the minimum contrast ratio of 4.5:1 for normal text. You can use online tools to calculate the contrast ratio and select colors that meet the accessibility guidelines.

View 19 affected elements
Component · Ref 1C9UJX
Affected pagehttps://tkees.com/products/gift-card
Element.cc-accordion-item__content.rte.cf > p:nth-child(2)
Accessible nameInstructions on how to redeem at the checkout are included with every purchase.
Markup
<p>Instructions on how to redeem at the checkout are included with every purchase.&nbsp;<br></p>
Component · Ref NFUV6I
Affected pagehttps://tkees.com/products/gift-card
Elementp:nth-child(1) > span:nth-child(3)
Accessible nameLet them decide with a digital gift card sent to your email! Print it off and put it in a card or forward it to them directly.
Markup
<span style="font-weight: 400;">Let them decide with a digital gift card sent to your email! Print it off and put it in a card or forward it to them directly. </span>
Component · Ref OXBG3Z
Affected pagehttps://tkees.com/products/gift-card
Element.cc-accordion-item__content.rte.cf > p:nth-child(1) > span:nth-child(1)
Accessible nameTake the guesswork out of gifting!
Markup
<span style="font-weight: 400;">Take the guesswork out of gifting!<br></span>
Component · Ref ALKSQH
Affected pagehttps://tkees.com/
Element.image-overlay-link[href$="aqua-collection"] > .height--fixed.image-overlay.image-overlay--bg-shadow > .overlay-text--align-center.overlay-text.overlay-text--for-banner > .overlay-content-box > .overlay-content-box__button-row > .overlay-text__button.altcolour.button
Accessible nameDIVE IN
Markup
<span class="overlay-text__button button altcolour ">
                      DIVE IN
                    </span>
Component · Ref XVNTUR
Affected pagehttps://tkees.com/
Element.image-overlay-link[href$="aqua-collection"] > .height--fixed.image-overlay.image-overlay--bg-shadow > .overlay-text--align-center.overlay-text.overlay-text--for-banner > .overlay-content-box > .overlay-content-box__heading.h1-style > .overlay-content-box__heading-line-two
Accessible nameFULLY WATERPROOF
Markup
<span class="overlay-content-box__heading-line-two">FULLY WATERPROOF</span>
Component · Ref 2HDAEP
Affected pagehttps://tkees.com/
Element.product-link[href$="flip-flop"] > .product-info > .product-block__title
Accessible nameFlip Flops
Markup
<div class="product-block__title">
          
          
          Flip Flops
        </div>
Component · Ref CYP5XS
Affected pagehttps://tkees.com/
Element.overlay-text__button-row > .overlay-text__button.altcolour.button
Accessible nameSHOP NOW
Markup
<span class="overlay-text__button button altcolour">SHOP NOW</span>
Component · Ref 01B3RU
Affected pagehttps://tkees.com/
Element.desktop-heading
Accessible nameSimply Nude
Markup
<h2 class="overlay-text__title h1-style title-font desktop-heading">
                  Simply Nude

                </h2>
Component · Ref PZ13AR
Affected pagehttps://tkees.com/
Element.overlay-content-box__heading-line-one
Accessible nameReese
Markup
<span class="overlay-content-box__heading-line-one">Reese</span>
Component · Ref 5JWTP3
Affected pagehttps://tkees.com/
Elementa[href$="new-in"] > .height--fixed.image-overlay.image-overlay--bg-shadow > .overlay-text--align-center.overlay-text.overlay-text--for-banner > .overlay-content-box > .overlay-content-box__button-row > .overlay-text__button.altcolour.button
Accessible nameSHOP NEW IN
Markup
<span class="overlay-text__button button altcolour ">
                      SHOP NEW IN
                    </span>
Component · Ref UZL1E2
Affected pagehttps://tkees.com/
Elementa[href$="best-sellers"] > .product-info > .product-block__title
Accessible nameBest Sellers
Markup
<div class="product-block__title">
          
          
          Best Sellers
        </div>
Component · Ref 4ARONW
Affected pagehttps://tkees.com/
Elementa[href$="new-in"] > .height--fixed.image-overlay.image-overlay--bg-shadow > .overlay-text--align-center.overlay-text.overlay-text--for-banner > .overlay-content-box > .overlay-content-box__heading.h1-style > .overlay-content-box__heading-line-two
Accessible nameMeet Phoenix
Markup
<span class="overlay-content-box__heading-line-two">Meet Phoenix</span>
Medium

Form fields use placeholder text as the only label

WCAG 1.3.1 (A)2 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 visible label to the form field, and ensure it is exposed as a programmatic label for screen readers. This can be achieved by adding a label element with a for attribute matching the input id, or by using the aria-label attribute on the input element.

View 2 affected elements
Component · Ref 4Y1ZT0
Affected pagehttps://tkees.com/products/gift-card
Elementinput#bis-phone
Markup
<input type="tel" class="bis-modal__input" id="bis-phone" placeholder="Phone (For SMS alerts)" inputmode="tel" autocomplete="tel" onkeydown="if(event.key==='Enter')bisSubmit()">
Low

Low-quality alternative text

WCAG 1.1.1 (A)20 instances5 inspected pages

Alt text looks like a filename, a generic word ("image", "photo"), or is duplicated across unrelated images — it likely does not describe the content.

Why it matters

Alt text looks like a filename, a generic word ("image", "photo"), or is duplicated across unrelated images — it likely does not describe the content.

Recommended correction

Update the alt text to describe the content of the image, such as 'Nude shoe model' or 'Product image of nude-colored shoes'.

View 20 affected elements
Component · Ref VM7HVE
Affected pagehttps://tkees.com/
Elementdiv:nth-of-type(2) > a > div:nth-of-type(1) > div > div > img
Markup
<img class="rimage__image lazyload--manual fade-in " data-src="//tkees.com/cdn/shop/files/Square_toe_for_mega_2_{width}x.jpg?v=1749598936" data-widths="[180, 220, 300, 360, 460, 540, 720, 900, 1080, 1296, 1512, 1728, 2048]" data-aspectratio="1.3316062176165804" data-sizes="auto" alt="Image">
Affected pages/ /pages/contact /products/gift-card /pages/wholesale-account-manager /cart
Low

Touch targets are too small

WCAG 2.5.8 (AA)15 instances1 inspected page

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

To improve accessibility, ensure that all interactive elements, such as buttons and links, have a minimum size of 24x24 pixels to make them easier to tap for users with disabilities. Consider increasing the size of the affected elements or adding sufficient padding around them to meet this requirement.

View 15 affected elements
Component · Ref J91FB8
Affected pagehttps://tkees.com/cart
Elementdiv[data-product-id="8304628498607"] > .block-inner > .block-inner-inner > .product-info > .inner > .innerer > .product-block-options.product-block-options--swatch[data-option-name="Color"] > .product-block-options__inner > .meta-rel.custom_colors_block > .custom-color-swatch.product-block-snippet:nth-child(2) > .cstm_colors[data-current-title=" Carob"][title=" Carob"]
Accessible nameCarob
Markup
<a href="/products/square-toe-lily-croc-carob" class=" cstm_colors metafieldProductsTitle" data-current-title=" Carob" title=" Carob">
Component · Ref N023TT
Affected pagehttps://tkees.com/cart
Element.custom_selected_product[data-current-title=" Emerald"][title=" Emerald"]
Accessible nameEmerald
Markup
<a href="/products/square-toe-lily-croc-emerald" class="custom_selected_product cstm_colors metafieldProductsTitle" data-current-title=" Emerald" title=" Emerald">
Component · Ref MFYMHN
Affected pagehttps://tkees.com/cart
Element.custom-color-swatch.product-block-snippet:nth-child(1) > .custom_selected_product[data-current-title=" Sable"][title=" Sable"]
Accessible nameSable
Markup
<a href="/products/square-toe-lily-croc-sable" class="custom_selected_product cstm_colors metafieldProductsTitle" data-current-title=" Sable" title=" Sable">

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.

ACTIVATE MONITORINGSEE PRICING

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