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

Accessibility issues detected on sandyliang.info

Evolize inspected 4 public pages on sandyliang.info and detected 21 automatically identifiable accessibility findings.

21Findings detected
9WCAG criteria affected
4Pages inspected
9 Sep 2026Assessment date

Highest detected severity: Critical · 11 high-priority findings · 80% inspected-page coverage

Most widespread issueHidden elements can still receive keyboard focusDetected on 4 inspected pages
Most affected page/cart18 findings detected
Most represented WCAG criterionWCAG 4.1.2 — Name, Role, Value7 detected findings

Is sandyliang.info 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 4 public pages on sandyliang.info and detected 21 accessibility findings. The most widespread issue was "Hidden elements can still receive keyboard focus", detected on 4 inspected pages. The most affected inspected page was "/cart", where 18 findings were detected. The assessment identified findings mapped to 9 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

    This link exposes no accessible text. Add visible text that identifies its destination, or remove the link if it serves no purpose. For an icon-only link, provide an aria-label describing where it goes. The link points to /collections/new-arrivals.

    View technical evidence →
  2. High

    Hidden elements can still receive keyboard focus

    WCAG 2.4.3 (A) · 4 inspected pages · 28 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) · 4 inspected pages · 8 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

    IDs used in ARIA and labels must be unique

    WCAG 4.1.2 (A) · 4 inspected pages · 8 instances
    Why this matters

    IDs used in ARIA and labels must be unique

    Recommended action

    Review the affected element and correct the reported accessibility issue.

    View technical evidence →
  5. High

    IDs used in ARIA and labels must be unique

    WCAG 4.1.2 (A) · 4 inspected pages · 8 instances
    Why this matters

    IDs used in ARIA and labels must be unique

    Recommended action

    Review the affected element and correct the reported accessibility issue.

    View technical evidence →

03 · WCAG criteria affected

CriterionNameLevelFindingsPagesReach
4.1.2Name, Role, ValueA744 / 4
2.5.8Target Size (Minimum)AA444 / 4
2.4.3Focus OrderA344 / 4
1.3.1Info and RelationshipsA244 / 4
2.1.1KeyboardA222 / 4
1.4.3Contrast (Minimum)AA111 / 4
2.4.1Bypass BlocksA144 / 4
2.4.4Link Purpose (In Context)A111 / 4
3.3.2Labels or InstructionsA144 / 4

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

IDs used in ARIA and labels must be unique

WCAG 4.1.2 (A)24 instances4 inspected pages

IDs used in ARIA and labels must be unique

Why it matters

IDs used in ARIA and labels must be unique

Recommended correction

Review the affected element and correct the reported accessibility issue.

View 24 affected elements
Component · Ref QMBWTU
Affected pagehttps://www.sandyliang.info/account/login?return_url=%2Faccount
Element.aside__title > a[href$="#menu-info-mobile"][aria-controls="menu-menu-info-mobile"][data-toggle=".aside--submenu-info-mobile"]
Accessible nameINFO
Markup
<a class="aside__link  aside__..." href="#menu-info-mobile" data-toggle=".aside--submenu-info..." id="menu-toggle-info-mob..." aria-haspopup="true" aria-expanded="false" aria-controls="menu-menu-info-mobil..." data-toggle-callback...="document.querySelect..." ...>
Affected pages/ /account /products/gift-card /cart
Component · Ref 7TFPQ9
Affected pagehttps://www.sandyliang.info/account/login?return_url=%2Faccount
Element.aside__section--inactive.aside__section[data-aside-section="/collections/all"] > .collapse.aside__item:nth-child(6) > .collapse__body[aria-labelledby="menu-collapse-toggle-5"][role="tree"]
Accessible nameJEWELRY
Roletree
Markup
<li class="aside__childs collapse__body" id="menu-collapse-5" role="tree" aria-labelledby="menu-collapse-toggle-5" style="display: none; max-height: 0px;">
Affected pages/ /account /products/gift-card /cart
Component · Ref QD69AO
Affected pagehttps://www.sandyliang.info/
Element#search > .search__form[role="search"][action="/search"] > .search__label[for="search__input"] > .search__input[type="search"][name="q"]
Markup
<input id="search__input" class="search__input" type="search" name="q" value="" required="">
Affected pages/ /account /products/gift-card /cart
Component · Ref U071PJ
Affected pagehttps://www.sandyliang.info/account/login?return_url=%2Faccount
Element.aside__section--inactive.aside__section[data-aside-section="/collections/all"] > .collapse.aside__item:nth-child(5) > .aside__title > .collapse__toggle.collapse__toggle--no-icon[aria-controls="menu-collapse-4"]
Accessible nameBAGS
Markup
<a id="menu-collapse-toggle-4" href="#:dropdown" class="aside__link collapse__toggle collapse__toggle--no-icon " aria-haspopup="true" aria-expanded="false" aria-controls="menu-collapse-4" style="pointer-events: auto">
                
                BAGS
              </a>
Affected pages/ /account /products/gift-card /cart
High

Hidden elements can still receive keyboard focus

WCAG 2.4.3 (A)40 instances4 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 40 affected elements
Component · Ref E63F69
Affected pagehttps://www.sandyliang.info/account/login?return_url=%2Faccount
Elementli#menu-collapse-2 > ul > li:nth-of-type(1) > a
Accessible nameDRESSES
Markup
<a class="aside__link " href="/collections/dresses">DRESSES</a>
Affected pages/ /account /products/gift-card /cart
Component · Ref DKZDXD
Affected pagehttps://www.sandyliang.info/products/gift-card
Elementa#menu-collapse-toggle-2
Accessible nameCLOTHING
Markup
<a id="menu-collapse-toggle-2" href="#:dropdown" class="aside__link collapse__toggle collapse__toggle--no-icon " aria-haspopup="true" aria-expanded="false" aria-controls="menu-collapse-2" style="pointer-events: auto">
                
                CLOTHING
              </a>
Affected pages/ /account /products/gift-card /cart
Component · Ref PY0EZU
Affected pagehttps://www.sandyliang.info/account/login?return_url=%2Faccount
Elementaside > div:nth-of-type(1) > div > ul:nth-of-type(1) > li > a
Accessible nameNEW
Markup
<a class="aside__link  " href="/collections/new-arrivals">
                NEW

                
              </a>
Affected pages/ /account /products/gift-card /cart
High

Form fields use placeholder text as the only label

WCAG 1.3.1 (A)4 instances4 inspected pages

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 4 affected elements
Component · Ref SB85D2
Affected pagehttps://www.sandyliang.info/account/login?return_url=%2Faccount
Elementform#localization_form > div > div > div > div > input
Markup
<input type="text" class="nice-select-search" placeholder="Search...">
Affected pages/ /account /products/gift-card /cart
High

Interactive controls are not keyboard-accessible

WCAG 2.1.1 (A)2 instances1 inspected page

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 2 affected elements
Component · Ref BL7AC3
Affected pagehttps://www.sandyliang.info/cart
Elementa#menu-toggle-cart
Accessible nameCart: 0
Rolebutton
Markup
<a role="button" id="menu-toggle-cart" class="header__item">
          Cart<span class="hidden" data-cart-amount="" data-hide="1" data-cart-amount-template=": {amount}" style="pointer-events: none;">: 0</span>
        </a>
High

Scrollable region must have keyboard access

WCAG 2.1.1 (A)1 instance1 inspected page

Scrollable region must have keyboard access

Why it matters

Scrollable region must have keyboard access

Recommended correction

Review the affected element and correct the reported accessibility issue.

View 1 affected element
Component · Ref PUQORO
Affected pagehttps://www.sandyliang.info/products/gift-card
Element.product__option:nth-child(2) > .nice-select > .nice-select-dropdown > .list
Accessible nameSize $50 Size $100 Size $200 Size $300 Size $500 Size $1000
Markup
<ul class="list">
Medium

ARIA attributes have invalid values

WCAG 4.1.2 (A)15 instances4 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 15 affected elements
Component · Ref GGRI2O
Affected pagehttps://www.sandyliang.info/account/login?return_url=%2Faccount
Element#search-toggle
Accessible nameSEARCH
Rolebutton
Markup
<a role="button" id="search-toggle" class="header__item" aria-haspopup="true" aria-expanded="false" aria-controls="search" href="/search" data-toggle="#search" data-toggle-callback...="document.querySelect..." data-toggle-callback...="document.querySelect..." onclick="setTimeout(() => doc...">
Affected pages/ /account /products/gift-card /cart
Component · Ref L2QUZK
Affected pagehttps://www.sandyliang.info/products/gift-card
Element#localization-toggle
Accessible nameUnited States / USD
Markup
<button id="localization-toggle" aria-haspopup="true" aria-expanded="false" aria-controls="modal-localization" class="footer__column footer__column--localization" data-toggle=".modal--localization">
Affected pages/ /account /products/gift-card /cart
Component · Ref S76H32
Affected pagehttps://www.sandyliang.info/cart
Element#form-toggle-footer
Accessible nameNewsletter
Markup
<button class="form__toggle" id="form-toggle-footer" aria-haspopup="true" aria-expanded="false" aria-controls="form-footer" data-toggle="#form-footer" data-toggle-callback...="document.querySelect..." data-toggle-callback...="document.querySelect..." onclick="setTimeout(() => doc...">
Affected pages/ /account /products/gift-card /cart
Medium

Touch targets are too small

WCAG 2.5.8 (AA)52 instances4 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 52 affected elements
Component · Ref YQBZ10
Affected pagehttps://www.sandyliang.info/products/gift-card
Elementli:nth-child(3) > a[href$="shipping-returns"]
Accessible nameShipping and returns
Markup
<a href="/pages/shipping-returns">Shipping and returns</a>
Affected pages/ /account /products/gift-card /cart
Component · Ref YFTU9U
Affected pagehttps://www.sandyliang.info/
Elementa[href$="terms-of-use"]
Accessible nameTerms of Use
Markup
<a href="/pages/terms-of-use">Terms of Use</a>
Affected pages/ /account /products/gift-card /cart
Component · Ref AKZO8L
Affected pagehttps://www.sandyliang.info/products/gift-card
Elementnav[aria-label="Footer navigation 1"] > ul > li:nth-child(1) > a[href$="contact"]
Accessible nameContact
Markup
<a href="/pages/contact">Contact</a>
Affected pages/ /account /products/gift-card /cart
Component · Ref BC0DNO
Affected pagehttps://www.sandyliang.info/products/gift-card
Element#form-toggle-footer
Accessible nameNewsletter
Markup
<button class="form__toggle" id="form-toggle-footer" aria-haspopup="true" aria-expanded="false" aria-controls="form-footer" data-toggle="#form-footer" data-toggle-callback...="document.querySelect..." data-toggle-callback...="document.querySelect..." onclick="setTimeout(() => doc...">
Affected pages/ /account /products/gift-card /cart
Low

Text has insufficient colour contrast

WCAG 1.4.3 (AA)1 instance1 inspected page

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 1 affected element
Component · Ref VIV5SB
Affected pagehttps://www.sandyliang.info/cart
Element.cart__text--empty
Accessible nameYour cart is currently empty
Markup
<div class="cart__text cart__text--empty " data-empty="">Your cart is currently empty</div>
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 037Y6D
Affected pagehttps://www.sandyliang.info/account/login?return_url=%2Faccount
Elementbody#account
Accessible nameSHOP NEW BEST SELLERS CLOTHING DRESSES TOPS SKIRTS PANTS KNITS OUTERWEAR ALL CLOTHING SHOES FLATS LOW HEELS HIGH HEELS BOOTS ALL SHOES BAGS HANDHELD SHOULDER CROSSBODY TOTE ALL BAGS JEWELRY EARRINGS NECKLACES BRACELETS RINGS ALL JEWELRY ACCESSORIES HAIR SOCKS CARD HOLDER ALL ACCESSORIES BRIDAL BRIDAL SHOP VEILS WEDDING GUEST MADE TO ORDER CUSTOM DRESSING UP: SANDY LIANG EDITS UNIFORM UNISEX PARTY SETS SHOP ALL SEARCH Search GO …[truncated by Evolize: exceeded D1 value limit]
Markup
<body id="account" class="page page--login ">

  <div id="shopify-section-announcement" class="shopify-section announcement">

</div>

  <header role="banner" class="header">
    <div id="shopify-section-header" class="shopify-section header__wrapper"><div class="header__content">
  <nav class="header__nav" role="navigation" aria-label="Main navigation left" id="menu">
    <ul>
      
        
          <li>
            <a id="menu-toggle-collections-all" class="header__item " href="/collections/all" data-aside=".aside--menu-0" data-aside-section="/collections/all" aria-haspopup="true" aria-ex…

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.