Evolize inspected 4 public pages on laughingmancoffee.com and detected 32 accessibility findings. The most widespread issue was "Interactive controls are not keyboard-accessible", detected on 4 inspected pages. The most affected inspected page was "/", where 25 findings were detected. The assessment identified findings mapped to 6 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.
High
Interactive controls are not keyboard-accessible
WCAG 2.1.1 (A) · 4 inspected pages · 16 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.
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.
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.
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.
Accessible nameSign up & Get 10% Off Your First Order!
Markup
<span style="font-size: 48px; color: #373f47; font-family: Kanit-Klaviyo-Hosted, Arial, 'Helvetica Neue', Helvetica, sans-serif; font-weight: bold;" class="ql-font-kanit">Sign up & Get 10% Off Your First Order!</span>
Element#ImageWithText--template--20108705956088__image-with-text-1 > .image-with-text__text.body.rte > p
Accessible nameIt started 14 years ago with a promise to Dukale, an Ethiopian farmer, to bring his coffee to the world and share his story. His journey reflects the hardships and generosity that go into farming the perfect cup.
Markup
<p>It started 14 years ago with a promise to Dukale, an Ethiopian farmer, to bring his coffee to the world and share his story. His journey reflects the hardships and generosity that go into farming the perfect cup.</p>
Component · Ref 450RPZ
Affected pagehttps://laughingmancoffee.com/
Element.newsletter__subheading > p
Accessible nameBe the first to know about new collections and exclusive offers.
Markup
<p>Be the first to know about new collections and exclusive offers.</p>
Component · Ref 5LXAT2
Affected pagehttps://laughingmancoffee.com/cart
Elementp > .ql-font-kanit
Accessible nameBy signing up, you agree to receive email marketing
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 35 affected elements
Component · Ref H3UW5E
Affected pagehttps://laughingmancoffee.com/cart
Elementul#HeaderMenu-MenuList-5 > li > a
Accessible nameEvents
Markup
<a href="/pages/events" class="header__menu-item list-menu__item link link--text focus-inset caption-large">
Events
</a>
Elementdiv > div > div > div:nth-of-type(1) > small > a
Accessible nameshipping
Markup
<a href="/policies/shipping-policy">shipping</a>
High
Interactive controls are not keyboard-accessible
WCAG 2.1.1 (A)53 instances4 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.
A carousel/slider exposes no previous/next or pause controls, so keyboard and assistive-technology users cannot navigate or stop it. Requires manual review of the specific widget.
Why it matters
A carousel/slider exposes no previous/next or pause controls, so keyboard and assistive-technology users cannot navigate or stop it. Requires manual review of the specific widget.
Recommended correction
Provide keyboard-operable previous/next controls and a pause control for auto-advancing carousels, with accessible names.
View 1 affected element
Component · Ref 4SFRGW
Affected pagehttps://laughingmancoffee.com/
Elementsection#shopify-section-template--20108705956088__multicolumn-1 > div > div > slider-component
Accessible nameFAIR TRADEOur fairly traded coffees ensure farmers receive fair compensation for the excellent product they bring to market and promote farming practices that protect the earth and sustainable growth.
GIVING BACKLaughing Man Foundation supports educational programs, community development and social entrepreneurs around the world
GREATER GOODWhen we say ALL BE HAPPY we mean for you and the planet. Our organic coffee is part of our commitment to your health and empowering a sustainable way of life around the globe.
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.