Public accessibility assessment

Accessibility issues detected on wolffer.com

Evolize inspected 4 public pages on wolffer.com and detected 24 automatically identifiable accessibility findings.

24Findings detected
7WCAG criteria affected
4Pages inspected
8 Sep 2026Assessment date

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

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

Is wolffer.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 4 public pages on wolffer.com and detected 24 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 "/", where 17 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. Critical

    Links lack accessible text

    WCAG 2.4.4 (A) · 1 inspected page · 2 instances
    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 /pages/the-tasting-room.

    View technical evidence →
  2. High

    Hidden elements can still receive keyboard focus

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

    Hidden elements can still receive keyboard focus

    WCAG 2.4.3 (A) · 4 inspected pages · 4 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) · 4 inspected pages · 4 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)AA1444 / 4
2.4.3Focus OrderA444 / 4
1.2.2Captions (Prerecorded)A211 / 4
1.3.1Info and RelationshipsA144 / 4
2.4.4Link Purpose (In Context)A111 / 4
2.5.8Target Size (Minimum)AA111 / 4
4.1.2Name, Role, ValueA111 / 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.

04 · All detected findings

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 Q1JPTR
Affected pagehttps://wolffer.com/collections/whats-in-our-cart
Elementform#predictive-search-form > div > dialog-close-button > button
Accessible nameClose
Markup
<button type="button">
            <span class="sr-only">Close</span><svg aria-hidden="true" focusable="false" fill="none" width="16" class="icon icon-close" viewBox="0 0 16 16">
      <path d="m1 1 14 14M1 15 15 1" stroke="currentColor" stroke-width="1.5"></path>
    </svg>

  </button>
Affected pages/ /pages/email-signup /collections/whats-in-our-cart /cart
Component · Ref EXA013
Affected pagehttps://wolffer.com/pages/email-signup
Elementdiv#MobileStateSelector > div > div > label > select
Accessible nameAKALARAZCACOCTDCDEFLGAHIIAIDILINKSKYLAMAMDMEMIMNMOMSMTNCNDNENHNJNMNVNYOHOKORPARISCSDTNTXUTVAVTWAWIWVWY
Markup
<select name="drinks-header-state-select" data-drinks-select="">
          <option value=""></option>
        <option value="AK">AK</option><option value="AL">AL</option><option value="AR">AR</option><option value="AZ">AZ</option><option value="CA">CA</option><option value="CO">CO</option><option value="CT">CT</option><option value="DC">DC</option><option value="DE">DE</option><option value="FL">FL</option><option value="GA">GA</option><option value="HI">HI</option><option value="IA">IA</option><option value="ID">ID</option><option value="IL">IL</option><option value="IN">IN</option><option va…
Affected pages/ /pages/email-signup /collections/whats-in-our-cart /cart
Component · Ref BBJ7F2
Affected pagehttps://wolffer.com/
Elementheader-sidebar#sidebar-menu > div > div:nth-of-type(1) > ul > li:nth-of-type(6) > button
Accessible nameABOUT
Markup
<button type="button" class="header-sidebar__linklist-button " aria-controls="header-panel-6" aria-expanded="false">ABOUT<svg aria-hidden="true" focusable="false" fill="none" width="12" class="icon icon-chevron-right  icon--direction-aware" viewBox="0 0 10 10">
      <path d="m3 9 4-4-4-4" stroke="currentColor" stroke-linecap="square"></path>
    </svg></button>
Affected pages/ /pages/email-signup /collections/whats-in-our-cart /cart
Component · Ref MVQ4LK
Affected pagehttps://wolffer.com/pages/email-signup
Elementdiv#header-panel-1 > ul > li:nth-of-type(1) > a
Accessible nameShop All
Markup
<a href="/collections/wines" class="header-sidebar__linklist-button ">Shop All</a>
Affected pages/ /pages/email-signup /collections/whats-in-our-cart /cart
Medium

Text has insufficient colour contrast

WCAG 1.4.3 (AA)40 instances4 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 40 affected elements
Component · Ref W5U2YT
Affected pagehttps://wolffer.com/cart
Element.prose.text-center > a[href$="privacy-policy"]
Accessible namePrivacy Policy
Markup
<a href="/policies/privacy-policy" class="link">Privacy Policy</a>
Affected pages/ /pages/email-signup /collections/whats-in-our-cart /cart
Component · Ref JDD0H4
Affected pagehttps://wolffer.com/cart
Elementa[href$="terms-of-service"]
Accessible nameTerms of Service
Markup
<a href="/policies/terms-of-service" class="link">Terms of Service</a>
Affected pages/ /pages/email-signup /collections/whats-in-our-cart /cart
Component · Ref OECBRZ
Affected pagehttps://wolffer.com/cart
Element.heading.prose:nth-child(1) > a[title="Shop All"][href$="wines"]
Accessible nameLabor Day DISCOUNT 4 bTLS, $15 OFF | 12 BTLS, $50 OFF | 24+ BTLS, $100 OFF
Markup
<a href="/collections/wines" title="Shop All">Labor Day DISCOUNT 4 bTLS, $15 OFF | 12 BTLS, $50 OFF | 24+ BTLS, $100 OFF</a>
Affected pages/ /collections/whats-in-our-cart /cart
Component · Ref STUQ7T
Affected pagehttps://wolffer.com/pages/email-signup
Element.shopify-pc__banner__body > p
Accessible nameWe use cookies and other technologies to personalize your experience, show you ads, and perform analytics, and we will not use cookies or other technologies for these purposes unless you accept them. Learn more in our Privacy Policy
Markup
<p>
Affected pages/pages/email-signup /cart
Component · Ref M419Z
Affected pagehttps://wolffer.com/
Element.button[href$="private-events"]
Accessible nameMake a Reservation
Markup
<a class="button" href="/pages/private-events">Make a Reservation</a>
Affected pages/ /collections/whats-in-our-cart
Component · Ref 4C2RTZ
Affected pagehttps://wolffer.com/
Element.upcoming-events__event:nth-child(1) > .upcoming-events__event-content > .upcoming-events__event-detail:nth-child(3) > .link > .link-parent-for-hover > .link__text
Accessible nameLEARN MORE
Markup
<span class="link__text">
                                LEARN MORE
                              </span>
Component · Ref 7A7TGT
Affected pagehttps://wolffer.com/
Element.media-grid__item[href$="happenings"] > .content-over-media.color-scheme--scheme-4[reveal-on-scroll="true"] > .prose--tight.place-self-center.prose > .link[type="button"]
Accessible nameCHECK EVENTS
Markup
<button type="button" class="link">CHECK EVENTS</button>
Component · Ref 5AMPWO
Affected pagehttps://wolffer.com/
Element.blog-post-card.snap-center.group:nth-child(3) > .blog-post-card__info > .blog-post-card__read-more.link
Accessible nameRead more
Markup
<a href="/blogs/news/featured-in-long-island-wine-press-2026-cab-franc-forward" class="blog-post-card__read-more link">Read more</a>
Component · Ref X0RY15
Affected pagehttps://wolffer.com/
Element.media-grid__item[href$="grandioso-rose-2025"] > .content-over-media.color-scheme--scheme-4[reveal-on-scroll="true"] > .prose--tight.place-self-center.prose > .h4
Accessible nameSTAFF PICK: GRANDIOSO ROSÉ
Markup
<p class="h4">STAFF PICK: GRANDIOSO ROSÉ</p>
Component · Ref OTQ06H
Affected pagehttps://wolffer.com/pages/email-signup
Element.is-selected > a[title="Shop All"][href$="wines"]
Markup
<a href="/collections/wines" title="Shop All">Labor Day DISCOUNT 4 bTLS, $15 OFF | 12 BTLS, $50 OFF | 24+ BTLS, $100 OFF</a>
Component · Ref 0GDH0O
Affected pagehttps://wolffer.com/collections/whats-in-our-cart
Element.h3
Accessible nameJoin the Wölffer Family
Markup
<p class="h3">
                      Join the Wölffer Family
                    </p>
Component · Ref O0HCV5
Affected pagehttps://wolffer.com/collections/whats-in-our-cart
Element.place-self-center-start > .prose > div > p
Accessible nameEnjoy complimentary tastings, 15% off every bottle, exclusive wine releases, and invitations to memorable events.
Markup
<p>Enjoy complimentary tastings, 15% off every bottle, exclusive wine releases, and invitations to memorable events.</p>
Component · Ref 3NFR9I
Affected pagehttps://wolffer.com/
Element.button[href$="happenings"] > .link-parent-for-hover > .link__text
Accessible nameVIEW ALL EVENTS
Markup
<span class="link__text">VIEW ALL EVENTS</span>
Component · Ref Y893YU
Affected pagehttps://wolffer.com/cart
Element.prose > .button[href$="wines"]
Accessible nameExplore Collections
Markup
<a class="button" href="/collections/wines">Explore Collections</a>
Medium

Content sits outside any landmark region

WCAG 1.3.1 (A)4 instances4 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 4 affected elements
Component · Ref W4DUEA
Affected pagehttps://wolffer.com/cart
Elementsection#shopify-pc__banner > div
Accessible nameWE USE COOKIESWe use cookies and other technologies to personalize your experience, show you ads, and perform analytics, and we will not use cookies or other technologies for these purposes unless you accept them. Learn more in our Privacy PolicyManage PreferencesACCEPTDECLINE
Markup
<div class="shopify-pc__banner__wrapper"><div class="shopify-pc__banner__body"><h2 id="shopify-pc__banner__body-title">WE USE COOKIES</h2><p>We use cookies and other technologies to personalize your experience, show you ads, and perform analytics, and we will not use cookies or other technologies for these purposes unless you accept them. Learn more in our  <a id="shopify-pc__banner__body-policy-link" href="https://3gbsuq-x7.myshopify.com/policies/privacy-policy" target="_blank" rel="noopener noreferrer">Privacy Policy</a></p></div><div class="shopify-pc__banner__btns shopify-pc__banner__btns-…
Affected pages/ /pages/email-signup /collections/whats-in-our-cart /cart
Medium

<video> elements must have captions

WCAG 1.2.2 (A)1 instance1 inspected page

<video> elements must have captions

Why it matters

<video> elements must have captions

Recommended correction

Review the affected element and correct the reported accessibility issue.

View 1 affected element
Component · Ref ASXZO7
Affected pagehttps://wolffer.com/
Elementvideo
Markup
<video class="ai-video-hero__video-arvltntrnmw1qa0y3daigenblock732db39tkmm6b" autoplay="" muted="" loop="" playsinline="">
        <source src="https://cdn.shopify.com/videos/c/o/v/e334243a41cc4f59afdc385c00fb5ef6.mp4" type="video/mp4">
      </video>
Low

ARIA attributes have invalid values

WCAG 4.1.2 (A)1 instance1 inspected page

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 1 affected element
Component · Ref 9WSZIA
Affected pagehttps://wolffer.com/collections/whats-in-our-cart
Elementbutton[aria-controls="sort-by-popover"]
Accessible nameSort by
Markup
<button type="button" aria-controls="sort-by-popover" class="collection-toolbar__button heading text-xxs w-full" aria-haspopup="dialog">
Low

Video may be missing captions

WCAG 1.2.2 (A)1 instance1 inspected page

A video element has no captions or subtitles track. Whether captions are needed depends on the audio content and requires manual review.

Why it matters

A video element has no captions or subtitles track. Whether captions are needed depends on the audio content and requires manual review.

Recommended correction

Provide a synchronized captions track (<track kind="captions">) for video with meaningful audio.

View 1 affected element
Component · Ref 6K4WZ2
Affected pagehttps://wolffer.com/
Elementdiv#shopify-section-template--20288756515051__1762869382746e16ce > div > div:nth-of-type(1) > video
Markup
<video class="ai-video-hero__video-arvltntrnmw1qa0y3daigenblock732db39tkmm6b" autoplay="" muted="" loop="" playsinline="">
        <source src="https://cdn.shopify.com/videos/c/o/v/e334243a41cc4f59afdc385c00fb5ef6.mp4" type="video/mp4">
      </video>
Low

Touch targets are too small

WCAG 2.5.8 (AA)2 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

Increase this <input>'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 2 affected elements
Component · Ref GN8G4L
Affected pagehttps://wolffer.com/collections/whats-in-our-cart
Elementfacets-form[update-on-change=""] > .facets[action="/collections/whats-in-our-cart"][method="GET"] > .accordion-list > accordion-disclosure:nth-child(3) > .accordion__disclosure[open=""] > .accordion__content > price-range > .range-group > .range[value="0"][type="range"]
Accessible nameFrom price
Markup
<input type="range" aria-label="From price" class="range" min="0" max="48" value="0">

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.