Public accessibility assessment

Accessibility issues detected on wigglybridgedistillery.com

Evolize inspected 5 public pages on wigglybridgedistillery.com and detected 33 automatically identifiable accessibility findings.

33Findings detected
4WCAG criteria affected
5Pages inspected
13 Aug 2026Assessment date

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

Most widespread issueLinks lack accessible textDetected on 5 inspected pages
Most affected page/shop15 findings detected
Most represented WCAG criterionWCAG 2.4.4 — Link Purpose (In Context)16 detected findings

Is wigglybridgedistillery.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 wigglybridgedistillery.com and detected 33 accessibility findings. The most widespread issue was "Links lack accessible text", detected on 5 inspected pages. The most affected inspected page was "/shop", where 15 findings were detected. The assessment identified findings mapped to 4 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 · 5 instances
    Why this matters

    Links expose no accessible name, so their destination is unknown to screen reader users.

    Recommended action

    Add text to these links that describes their purpose, or use the 'aria-label' attribute to provide a text description for screen readers.

    View technical evidence →
  2. Critical

    Links lack accessible text

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

    Links expose no accessible name, so their destination is unknown to screen reader users.

    Recommended action

    Add alternative text to the images within the links, or provide a text description of the link's purpose and destination.

    View technical evidence →
  3. Critical

    Links lack accessible text

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

    Links expose no accessible name, so their destination is unknown to screen reader users.

    Recommended action

    Add alternative text to the images within the links, or provide a text description of the link's purpose and destination.

    View technical evidence →
  4. Critical

    Links lack accessible text

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

    Links expose no accessible name, so their destination is unknown to screen reader users.

    Recommended action

    Add alternative text to the images within the links, or provide a text description of the link's purpose and destination.

    View technical evidence →
  5. Critical

    Links lack accessible text

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

    Links expose no accessible name, so their destination is unknown to screen reader users.

    Recommended action

    Add alternative text to the images within the links, or provide a text description of the link's purpose and destination.

    View technical evidence →

03 · WCAG criteria affected

CriterionNameLevelFindingsPagesReach
2.4.4Link Purpose (In Context)A1655 / 5
1.4.3Contrast (Minimum)AA1455 / 5
2.4.3Focus OrderA255 / 5
4.1.2Name, Role, ValueA111 / 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

Text has insufficient colour contrast

WCAG 1.4.3 (AA)43 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 between the text color and its background by adjusting either the text or background color to meet the minimum contrast ratio as defined by WCAG 2.1 SC 1.4.3.

View 43 affected elements
Component · Ref QNWOFN
Affected pagehttps://wigglybridgedistillery.com/shop/
Element#menu-item-1048 > a[title="visit-us"]
Accessible nameVisit Us
Markup
<a href="https://wigglybridgedistillery.com/visit-us/" title="visit-us">Visit Us</a>
Affected pages/shop /locations/market-basket-biddeford /wpbc-booking-received
Component · Ref MS6K0T
Affected pagehttps://wigglybridgedistillery.com/shop/
Element.white-nav:nth-child(1) > .bottom-nav.widewrap.cf > .left
Accessible nameSmall Batch
Markup
<p class="left">Small Batch</p>
Affected pages/shop /locations/market-basket-biddeford /wpbc-booking-received
Component · Ref 1CBUCH
Affected pagehttps://wigglybridgedistillery.com/shop/
Element.white-nav:nth-child(1) > .bottom-nav.widewrap.cf > .right
Accessible nameDISTILLED & BOTTLED IN YORK, ME
Markup
<p class="right">DISTILLED &amp; BOTTLED IN YORK, ME</p>
Affected pages/shop /locations/market-basket-biddeford /wpbc-booking-received
Component · Ref K907OT
Affected pagehttps://wigglybridgedistillery.com/shop/
Element#menu-item-1204 > .mega-drop[title="experiences"][href="#"]
Accessible nameExperiences
Markup
<a href="#" title="experiences" class="mega-drop">Experiences</a>
Affected pages/shop /locations/market-basket-biddeford /wpbc-booking-received
Component · Ref 5VFI8Q
Affected pagehttps://wigglybridgedistillery.com/faqs/
Element.age-gate__submit--yes
Accessible nameYes
Markup
<button type="submit" class="age-gate__submit age-gate__submit--yes" data-submit="yes" value="1" name="age_gate[confirm]">Yes</button>
Affected pages/ /faqs /shop /locations/market-basket-biddeford /wpbc-booking-received
Component · Ref C9H56A
Affected pagehttps://wigglybridgedistillery.com/shop/
Element#gform_submit_button_1
Markup
<input type="submit" id="gform_submit_button_1" class="gform_button button" onclick="gform.submission.handleButtonClick(this);" data-submission-type="submit" value="Sign Up">
Affected pages/shop /wpbc-booking-received
Component · Ref YBRL0L
Affected pagehttps://wigglybridgedistillery.com/faqs/
Element.age-gate__heading-title
Accessible nameARE YOU 21 OR OLDER?
Markup
<h1 class="age-gate__heading-title">ARE YOU 21 OR OLDER?</h1>
Affected pages/ /faqs /locations/market-basket-biddeford
Component · Ref Y4NL59
Affected pagehttps://wigglybridgedistillery.com/shop/
Element.vc_custom_1705009753596 > .wpb_wrapper > p
Accessible nameDrop us your email to stay up to date with all the Wiggly Bridge Distillery happenings. Get updates on special projects, recipes & more.
Markup
<p style="text-align: center;">Drop us your email to stay up to date with all the Wiggly Bridge Distillery happenings. Get updates on special projects, recipes &amp; more.</p>
Affected pages/shop /wpbc-booking-received
Component · Ref 87ROXO
Affected pagehttps://wigglybridgedistillery.com/shop/
Elementh2
Accessible nameStay in the know
Markup
<h2 style="text-align: center;">Stay in the know</h2>
Affected pages/shop /wpbc-booking-received
Component · Ref 7KWWJ3
Affected pagehttps://wigglybridgedistillery.com/shop/
Elementh1
Accessible nameARE YOU 21 OR OLDER?
Markup
<h1 class="age-gate__heading-title">ARE YOU 21 OR OLDER?</h1>
Affected pages/shop /wpbc-booking-received
Component · Ref SYLCX9
Affected pagehttps://wigglybridgedistillery.com/wpbc-booking-received/
Element#main > p
Accessible nameThank you for your booking. Your booking has been successfully received. [booking_confirm]
Markup
<p>Thank you for your booking. Your booking has been successfully received.<br>
 [booking_confirm]</p>
Component · Ref JNENRU
Affected pagehttps://wigglybridgedistillery.com/
Element.wpb_wrapper > p:nth-child(2) > span
Accessible nameWe are a craft distillery in the beautiful oceanside town of York, Maine. We look forward to stocking your liquor cabinet with our handmade spirits to enjoy the fruits and grains of our passion.
Markup
<span style="color: #ffffff;">We are a craft distillery in the beautiful oceanside town of York, Maine. We look forward to stocking your liquor cabinet with our handmade spirits to enjoy the fruits and grains of our passion.</span>
Component · Ref YZJ2WB
Affected pagehttps://wigglybridgedistillery.com/
Element.home-hero-left > .vc_column-inner > .wpb_wrapper > .wpb_text_column.wpb_content_element > .wpb_wrapper > h1 > span
Accessible nameWelcome To Wiggly Bridge Distillery
Markup
<span style="color: #ffffff;">Welcome To Wiggly Bridge Distillery</span>
Component · Ref 24YJLK
Affected pagehttps://wigglybridgedistillery.com/shop/
Element#input_1_1
Markup
<input name="input_1" id="input_1_1" type="email" value="" class="large" placeholder="Email Address" aria-invalid="false">
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

To fix this issue, ensure that any element that is not visible is also removed from the tab order, or make the element visible when it receives focus. This can be achieved by adding 'tabindex=-1' to the element or by adjusting the CSS to make the element visible when focused.

View 50 affected elements
Component · Ref IPCRXS
Affected pagehttps://wigglybridgedistillery.com/faqs/
Elementdiv:nth-of-type(1) > div > div:nth-of-type(2) > ul:nth-of-type(1) > li:nth-of-type(2) > a
Accessible nameView All Spirits
Markup
<a href="/spirits">View All Spirits</a>
Affected pages/ /faqs /shop /locations/market-basket-biddeford /wpbc-booking-received
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 implementing a focus trap using JavaScript. This will prevent focus from escaping the dialog and ensure that keyboard users can navigate the dialog as intended.

View 5 affected elements
Component · Ref CY4BYZ
Affected pagehttps://wigglybridgedistillery.com/faqs/
Elementhtml > body > div:nth-of-type(1) > div:nth-of-type(4)
Accessible nameARE YOU 21 OR OLDER? Yes No
Roledialog
Markup
<div class="age-gate" role="dialog" aria-modal="true" aria-label="">    <form method="post" class="age-gate__form">
<div class="age-gate__heading">            <h1 class="age-gate__heading-title">ARE YOU 21 OR OLDER?</h1>    </div>
<p class="age-gate__subheadline">    </p>
<div class="age-gate__fields">        
<p class="age-gate__challenge">    </p>
<div class="age-gate__buttons">        <button type="submit" class="age-gate__submit age-gate__submit--yes" data-submit="yes" value="1" name="age_gate[confirm]">Yes</button>            <button class="age-gate__submit age-gate__submit--no" data-subm…
Affected pages/ /faqs /shop /locations/market-basket-biddeford /wpbc-booking-received
Medium

Frames must have a unique title attribute

WCAG 4.1.2 (A)5 instances1 inspected page

Frames must have a unique title attribute

Why it matters

Frames must have a unique title attribute

Recommended correction

Update the title attribute of the iframe to be unique and descriptive of its content, such as including the product name or a brief description of the frame's purpose.

View 5 affected elements
Component · Ref RF9LPU
Affected pagehttps://wigglybridgedistillery.com/
Elementiframe[name="frame-product-10085480792351"]
Accessible nameADD TO CART
Markup
<iframe horizontalscrolling="no" verticalscrolling="no" allowtransparency="true" frameborder="0" scrolling="no" name="frame-product-10085480792351" title="ADD TO CART" style="width: 100%; overflow: hidden; border-width: 0px; border-style: none; height: 71px;"></iframe>

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.