Public accessibility assessment

Accessibility issues detected on herculescandy.com

Evolize inspected 5 public pages on herculescandy.com and detected 29 automatically identifiable accessibility findings.

29Findings detected

6WCAG criteria affected

5Pages inspected

9 Sep 2026Assessment date

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

Most widespread issueHidden elements can still receive keyboard focusDetected on 5 inspected pages

Most affected page/25 findings detected

Most represented WCAG criterionWCAG 1.4.3 — Contrast (Minimum)12 detected findings

Is herculescandy.com your website?

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

ACTIVATE MONITORING RUN A FREE ASSESSMENT

Not your website? Scan your own site →

01 · Accessibility summary

Evolize inspected 5 public pages on herculescandy.com and detected 29 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 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.

Critical
Buttons have no accessible name
WCAG 4.1.2 (A) · 2 inspected pages · 2 instances
Why this matters
Interactive buttons expose no accessible name, so their purpose cannot be determined by assistive technology.
Recommended action
Give it an accessible name that describes the action it performs: provide visible text when a visible label is appropriate, an aria-label for an icon-only control (for example aria-label="Dismiss notification"), or aria-labelledby when an existing visible label already describes it. Avoid vague names such as "Button", "Action", or the component's internal name.
View technical evidence →
Critical
Buttons have no accessible name
WCAG 4.1.2 (A) · 1 inspected page · 1 instance
Why this matters
Interactive buttons expose no accessible name, so their purpose cannot be determined by assistive technology.
Recommended action
Give it an accessible name that describes the action it performs: provide visible text when a visible label is appropriate, an aria-label for an icon-only control (for example aria-label="Dismiss notification"), or aria-labelledby when an existing visible label already describes it. Avoid vague names such as "Button", "Action", or the component's internal name.
View technical evidence →
Critical
Buttons have no accessible name
WCAG 4.1.2 (A) · 1 inspected page · 1 instance
Why this matters
Interactive buttons expose no accessible name, so their purpose cannot be determined by assistive technology.
Recommended action
Give it an accessible name that describes the action it performs: provide visible text when a visible label is appropriate, an aria-label for an icon-only control (for example aria-label="Dismiss notification"), or aria-labelledby when an existing visible label already describes it. Avoid vague names such as "Button", "Action", or the component's internal name.
View technical evidence →
High
Hidden elements can still receive keyboard focus
WCAG 2.4.3 (A) · 5 inspected pages · 30 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 →
High
Interactive controls are not keyboard-accessible
WCAG 2.1.1 (A) · 5 inspected pages · 30 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.
View technical evidence →

03 · WCAG criteria affected

Criterion	Name	Level	Findings	Pages	Reach
1.4.3	Contrast (Minimum)	AA	12	5	5 / 5
1.3.1	Info and Relationships	A	5	5	5 / 5
4.1.2	Name, Role, Value	A	5	3	3 / 5
2.4.3	Focus Order	A	4	5	5 / 5
2.1.1	Keyboard	A	3	5	5 / 5
3.3.2	Labels or Instructions	A	1	5	5 / 5

Absence of a criterion here does not indicate conformance with it — only that no automatically detectable issue was found for it.

04 · All detected findings

Critical

Buttons have no accessible name

WCAG 4.1.2 (A)4 instances3 inspected pages

Interactive buttons expose no accessible name, so their purpose cannot be determined by assistive technology.

Why it matters

Interactive buttons expose no accessible name, so their purpose cannot be determined by assistive technology.

Recommended correction

Give it an accessible name that describes the action it performs: provide visible text when a visible label is appropriate, an aria-label for an icon-only control (for example aria-label="Dismiss notification"), or aria-labelledby when an existing visible label already describes it. Avoid vague names such as "Button", "Action", or the component's internal name.

View 4 affected elements

Component · Ref LPN54E

Affected pagehttps://www.herculescandy.com/collections/easter/products/rabbit-sitting-on-basket

Element.js-photoswipe__zoom

Accessible nameClose (esc)

Markup

<button type="button" class="btn btn--body btn--circle js-photoswipe__zoom product__photo-zoom">

Affected pages/products/rabbit-sitting-on-basket /collections/easter/products/rabbit-sitting-on-basket

Component · Ref NDTXAU

Affected pagehttps://www.herculescandy.com/

Element.owl-next

Rolepresentation

Markup

<button type="button" role="presentation" class="owl-next"><img src="//www.herculescandy.com/cdn/shop/t/42/assets/b1.png?v=164672958981769429441737663532" alt=""></button>

Component · Ref EL7RT7

Affected pagehttps://www.herculescandy.com/

Element.owl-prev

Rolepresentation

Markup

<button type="button" role="presentation" class="owl-prev"><img src="//www.herculescandy.com/cdn/shop/t/42/assets/b2.png?v=139972108938311920291737663532" alt=""></button>

High

ARIA role is missing its required parent

WCAG 1.3.1 (A)36 instances5 inspected pages

An element with an ARIA role is not inside the container role it requires, so the relationship is lost.

Why it matters

An element with an ARIA role is not inside the container role it requires, so the relationship is lost.

Recommended correction

Place the element inside its required parent role (e.g. option must be within listbox).

View 36 affected elements

Component · Ref 8574AK

Affected pagehttps://www.herculescandy.com/

Element.mega_menu

Accessible nameCatalog ASSORTED CHOCOLATES BEST SELLERS CANDY BARS AND MORE CHOCOLATE BARK CHOCOLATE COVERED CHOCOLATE NOVELTIES CHOCOLATE PARTY FAVORS CHRISTMAS CLUSTERS AND CHUNK CHOCOLATE EASTER HALLOWEEN CHOCOLATES HARD CANDY HERCULES CANDY MERCHANDISE HERCULES EXCLUSIVES LOCAL PICK UP ONLY MOTHER'S DAY NUT BRITTLE, HARD CANDY, RIBBON CANDY NUT BRITTLES PARTY FAVORS PERSONALIZED FAVOR BOXES RIBBON CANDY, FILLED SINGLES STOCKING STUFFERS THANKSGIVING VALENTINES HEART BOXES VALENTINES NOVELTIES VEGAN CANDY Assorted Chocolates Chocolate Bark Hard Candy Nut Brittles Ribbon Candy Chocolate Covered Clusters and Chunk Chocolate Christmas Vegan Candy Candy Bars Chocolate Novelties Hercules Exclusives Hercules Candy Merchandise Corporate Chocolates Personalized Favor Boxes Party Favors

Rolemenuitem

Markup

<li class="site-nav__item site-nav__expanded-item  mega_menu site-nav--has-dropdown" role="menuitem">

Affected pages/ /account/login /products/rabbit-sitting-on-basket /collections/easter/products/rabbit-sitting-on-basket /cart

Component · Ref NSVC1U

Affected pagehttps://www.herculescandy.com/cart

Element.site-nav__item.site-nav__expanded-item[role="menuitem"]:nth-child(4)

Accessible nameFAQs

Rolemenuitem

Markup

<li class="site-nav__item site-nav__expanded-item " role="menuitem">

      <a href="/pages/faqs" class="site-nav__link site-nav__link--underline" alt="FAQs">
        FAQs
      </a></li>

Affected pages/ /account/login /products/rabbit-sitting-on-basket /collections/easter/products/rabbit-sitting-on-basket /cart

Component · Ref 7RAULU

Affected pagehttps://www.herculescandy.com/

Element.slideshow__slide

Accessible name.slideshow__slide--1524768368258-0 .hero__title { font-size: 30.0px; } @media only screen and (min-width: 769px) { .slideshow__slide--1524768368258-0 .hero__title { font-size: 60px; } } .slideshow__slide--1524768368258-0 .btn { background: #ffffff !important; border: none; color: #000 !important; } .hero__image--1524768368258-0 { object-position: top center; font-family: "object-fit: cover; object-position: top center;"; } <img class="image-fit hero__image hero__image--1524768368258-0" src="//www.herculescandy.com/cdn/shop/files/Creams_enrobed_biggest_1400x.jpg?v=1619209340" alt=""> welcome to our shop Hercules Candy explore now

Roleoption

Markup

<div class="slideshow__slide sli..." data-id="1524768368258-0" data-slick-index="0" aria-hidden="false" tabindex="-1" role="option" aria-describedby="slick-slide00" style="width: 1400px; posit...">

High

Text has insufficient colour contrast

WCAG 1.4.3 (AA)25 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 ratio to at least 4.5:1 for normal text and 3:1 for large text.

View 25 affected elements

Component · Ref Q8D3RK

Affected pagehttps://www.herculescandy.com/cart

Element.announcement-text

Accessible nameIt's hot. heed shipping recommendations! Store hours monday through friday 10am to 6pm saturday 10am to 4pm

Markup

<span class="announcement-text">It's hot. heed shipping recommendations! Store hours monday through friday 10am to 6pm saturday 10am to 4pm</span>

Affected pages/ /account/login /products/rabbit-sitting-on-basket /collections/easter/products/rabbit-sitting-on-basket /cart

Component · Ref J2IW4X

Affected pagehttps://www.herculescandy.com/products/rabbit-sitting-on-basket

Element.announcement-link-text

Accessible namesee shipping info update

Markup

<span class="announcement-link-text">see shipping info update</span>

Affected pages/ /account/login /products/rabbit-sitting-on-basket /collections/easter/products/rabbit-sitting-on-basket /cart

Component · Ref FMMNDC

Affected pagehttps://www.herculescandy.com/account/login

Elementinput[placeholder="Search..."]

Accessible nameSearch our store

Markup

<input type="search" name="q" value="" placeholder="Search..." class="site-header__search-input" aria-label="Search our store">

Affected pages/ /account/login /products/rabbit-sitting-on-basket /collections/easter/products/rabbit-sitting-on-basket /cart

Component · Ref Y8FK6H

Affected pagehttps://www.herculescandy.com/collections/easter/products/rabbit-sitting-on-basket

Element#ProductPrice-2583369027

Accessible name$ 6.99

Markup

<span id="ProductPrice-2583369027" class="product__price">
              $ 6.99
            </span>

Affected pages/products/rabbit-sitting-on-basket /collections/easter/products/rabbit-sitting-on-basket

Component · Ref F6JNPO

Affected pagehttps://www.herculescandy.com/

Elementa[alt="Read More"]

Accessible nameRead More

Markup

<a href="/pages/about-us" class="btn" alt="Read More">
          Read More
        </a>

Component · Ref KMUIAL

Affected pagehttps://www.herculescandy.com/

Element.rte > p:nth-child(1)

Accessible nameHercules Candy Company was founded over 100 years ago. In 1905, my grandfather, Robert and his 2 brothers, Jim and Pete arrived in America from Greece through a port in Boston, MA .

Markup

<p>Hercules Candy Company was founded over 100 years ago. In 1905, my grandfather, Robert and his 2 brothers, Jim and Pete arrived in America from Greece through a port in Boston, MA .<br></p>

Component · Ref 6SB8U7

Affected pagehttps://www.herculescandy.com/collections/easter/products/rabbit-sitting-on-basket

Element.return-link

Accessible nameBack to Easter

Markup

<a href="/collections/easter" class="btn btn--small return-link">
      <svg aria-hidden="true" focusable="false" role="presentation" class="icon icon--wide icon-arrow-left" viewBox="0 0 50 15"><path d="M50 5.38v4.25H15V15L0 7.5 15 0v5.38z"></path></svg> Back to Easter
    </a>

Component · Ref MNPN6D

Affected pagehttps://www.herculescandy.com/

Element.h1 > .animation-cropper > .animation-contents

Accessible nameHercules Candy

Markup

<div class="animation-contents">
                              Hercules Candy
                            </div>

Component · Ref VFQ3RV

Affected pagehttps://www.herculescandy.com/

Element.itg_btn

Accessible nameexplore now

Markup

<a href="/collections/all" class="btn itg_btn" alt="explore now" tabindex="0">
                                  explore now
                                </a>

Component · Ref KO4W2R

Affected pagehttps://www.herculescandy.com/account/login

Element.btn--full

Accessible nameSign In

Markup

<button type="submit" class="btn btn--full">
              Sign In
            </button>

Component · Ref 5UWCQ1

Affected pagehttps://www.herculescandy.com/

Element.hero__top-subtitle > .animation-cropper > .animation-contents

Accessible namewelcome to our shop

Markup

<div class="animation-contents">
                              welcome to our shop
                            </div>

Component · Ref A4LJ5Z

Affected pagehttps://www.herculescandy.com/

Element.h3

Accessible nameAbout us

Markup

<h2 class="h3">About us
      	</h2>

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

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 50 affected elements

Component · Ref 6S17BD

Affected pagehttps://www.herculescandy.com/products/rabbit-sitting-on-basket

Elementdiv:nth-of-type(2) > ul:nth-of-type(1) > li:nth-of-type(2) > div:nth-of-type(1) > div > button

Markup

<button type="button" aria-controls="Linklist-collections2" class="collapsible-trigger collapsible--auto-height" aria-expanded="false"><span class="collapsible-trigger__icon collapsible-trigger__icon--open" role="presentation">
  <svg aria-hidden="true" focusable="false" role="presentation" class="icon icon--wide icon-chevron-down" viewBox="0 0 28 16"><path d="M1.57 1.59l12.76 12.77L27.1 1.59" stroke-width="2" stroke="#000" fill="none" fill-rule="evenodd"></path></svg>
</span>
</button>

Affected pages/ /account/login /products/rabbit-sitting-on-basket /collections/easter/products/rabbit-sitting-on-basket /cart

Component · Ref 9EZNLQ

Affected pagehttps://www.herculescandy.com/

Elementdiv#NavDrawer > div > div:nth-of-type(1) > div > div:nth-of-type(2) > button

Accessible nameClose menu

Markup

<button type="button" class="drawer__close-button js-drawer-close">
            <svg aria-hidden="true" focusable="false" role="presentation" class="icon icon-close" viewBox="0 0 64 64"><path d="M19 17.61l27.12 27.13m0-27.12L19 44.74"></path></svg>
            <span class="icon__fallback-text">Close menu</span>
          </button>

Affected pages/ /account/login /products/rabbit-sitting-on-basket /collections/easter/products/rabbit-sitting-on-basket /cart

Component · Ref HRAAX7

Affected pagehttps://www.herculescandy.com/cart

Elementdiv#NavDrawer > div > div:nth-of-type(2) > ul:nth-of-type(1) > li:nth-of-type(6) > a

Accessible nameShipping Info

Markup

<a href="/pages/shipping-rules" class="mobile-nav__link mobile-nav__link--top-level">Shipping Info</a>

Affected pages/ /account/login /products/rabbit-sitting-on-basket /collections/easter/products/rabbit-sitting-on-basket /cart

Component · Ref 6FDLHC

Affected pagehttps://www.herculescandy.com/

Elementa#Label-collections2

Accessible nameCatalog

Markup

<a href="/collections" class="mobile-nav__link mobile-nav__link--top-level" id="Label-collections2">
                    Catalog
                  </a>

Affected pages/ /account/login /products/rabbit-sitting-on-basket /collections/easter/products/rabbit-sitting-on-basket /cart

High

Interactive controls are not keyboard-accessible

WCAG 2.1.1 (A)36 instances5 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.

View 36 affected elements

Component · Ref JVVQQ8

Affected pagehttps://www.herculescandy.com/

Elementheader > div:nth-of-type(1) > div > div:nth-of-type(2) > ul > li:nth-of-type(5)

Accessible nameContact

Rolemenuitem

Markup

<li class="site-nav__item site-nav__expanded-item " role="menuitem">

      <a href="/pages/contact" class="site-nav__link site-nav__link--underline" alt="Contact">
        Contact
      </a></li>

Affected pages/ /account/login /products/rabbit-sitting-on-basket /collections/easter/products/rabbit-sitting-on-basket /cart

Component · Ref YVP6A

Affected pagehttps://www.herculescandy.com/

Elementheader > div:nth-of-type(1) > div > div:nth-of-type(2) > ul > li:nth-of-type(2)

Rolemenuitem

Markup

<li class="site-nav__item site-nav__expanded-item  mega_menu site-nav--has-dropdown" role="menuitem">

      <a href="/collections" class="site-nav__link site-nav__link--underline site-nav__link--has-dropdown" alt="Catalog">
        Catalog
      </a>
         <div class="mega_menu_container site-nav__dropdown">
           
           <div class="grid grid--uniform">
             <div class="grid__item small--one-half medium-up--one-half">
               
               
                
               
                 <div data-img="assorted-chocolates" class="menu_img menu__img_2 active"><d…

Affected pages/ /account/login /products/rabbit-sitting-on-basket /collections/easter/products/rabbit-sitting-on-basket /cart

Component · Ref T1279C

Affected pagehttps://www.herculescandy.com/

Elementdiv#Slideshow-1524768368258 > div > div > div

Roleoption

Markup

<div class="slideshow__slide slideshow__slide--1524768368258-0 slick-slide slick-current slick-active" data-id="1524768368258-0" data-slick-index="0" aria-hidden="false" tabindex="-1" role="option" aria-describedby="slick-slide00" style="width: 1400px; position: relative; left: 0px; top: 0px; z-index: 999; opacity: 1;"><style data-shopify="">.slideshow__slide--1524768368258-0 .hero__title {
                  font-size: 30.0px;
                }
                @media only screen and (min-width: 769px) {
                  .slideshow__slide--1524768368258-0 .hero__title {
                    fon…

High

Form fields use placeholder text as the only label

WCAG 1.3.1 (A)5 instances5 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 5 affected elements

Component · Ref 512XSA

Affected pagehttps://www.herculescandy.com/collections/easter/products/rabbit-sitting-on-basket

Elementinput#destination-zip-code

Markup

<input type="text" name="zip-code" id="destination-zip-code" placeholder="Zip Code">

Affected pages/ /account/login /products/rabbit-sitting-on-basket /collections/easter/products/rabbit-sitting-on-basket /cart

High

Interactive controls must not be nested

WCAG 4.1.2 (A)1 instance1 inspected page

Interactive controls must not be nested

Why it matters

Interactive controls must not be nested

Recommended correction

Review the affected element and correct the reported accessibility issue.

View 1 affected element

Component · Ref 47E6LW

Affected pagehttps://www.herculescandy.com/

Element.slideshow__slide

Roleoption

Markup

<div class="slideshow__slide sli..." data-id="1524768368258-0" data-slick-index="0" aria-hidden="false" tabindex="-1" role="option" aria-describedby="slick-slide00" style="width: 1400px; posit...">

Medium

Navigation regions are not distinguishable

WCAG 1.3.1 (A)5 instances5 inspected pages

The page has multiple navigation landmarks but they lack accessible names, so screen reader users cannot tell them apart.

Why it matters

The page has multiple navigation landmarks but they lack accessible names, so screen reader users cannot tell them apart.

Recommended correction

Give each navigation region a distinct aria-label (e.g. "Primary", "Footer") when more than one is present.

View 5 affected elements

Component · Ref EG8V2H

Affected pagehttps://www.herculescandy.com/collections/easter/products/rabbit-sitting-on-basket

Elementdiv > header > div:nth-of-type(1) > div > div:nth-of-type(2) > ul

Accessible nameHome Catalog ASSORTED CHOCOLATES BEST SELLERS CANDY BARS AND MORE CHOCOLATE BARK CHOCOLATE COVERED CHOCOLATE NOVELTIES CHOCOLATE PARTY FAVORS CHRISTMAS CLUSTERS AND CHUNK CHOCOLATE EASTER HALLOWEEN CHOCOLATES HARD CANDY HERCULES CANDY MERCHANDISE HERCULES EXCLUSIVES LOCAL PICK UP ONLY MOTHER'S DAY NUT BRITTLE, HARD CANDY, RIBBON CANDY NUT BRITTLES PARTY FAVORS PERSONALIZED FAVOR BOXES RIBBON CANDY, FILLED SINGLES STOCKING STUFFERS THANKSGIVING VALENTINES HEART BOXES VALENTINES NOVELTIES VEGAN CANDY Assorted Chocolates Chocolate Bark Hard Candy Nut Brittles Ribbon Candy Chocolate Covered Clusters and Chunk Chocolate Christmas Vegan Candy Candy Bars Chocolate Novelties Hercules Exclusives Hercules Candy Merchandise Corporate Chocolates Personalized Favor Boxes Party Favors About Us FAQs Contact Shipping Info Gift Cards

Rolenavigation

Markup

<ul class="site-nav site-navigation small--hide medium-up--hide widescreen--show" role="navigation"><li class="site-nav__item site-nav__expanded-item " role="menuitem">

      <a href="/" class="site-nav__link site-nav__link--underline" alt="Home">
        Home
      </a></li><li class="site-nav__item site-nav__expanded-item  mega_menu site-nav--has-dropdown" role="menuitem">

      <a href="/collections" class="site-nav__link site-nav__link--underline site-nav__link--has-dropdown" alt="Catalog">
        Catalog
      </a>
         <div class="mega_menu_container site-nav__dropdown">
         …

Affected pages/ /account/login /products/rabbit-sitting-on-basket /collections/easter/products/rabbit-sitting-on-basket /cart

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 2HMRQC

Affected pagehttps://www.herculescandy.com/

Element.slideshow__slide

Roleoption

Markup

<div class="slideshow__slide sli..." data-id="1524768368258-0" data-slick-index="0" aria-hidden="false" tabindex="-1" role="option" aria-describedby="slick-slide00" style="width: 1400px; posit...">

05 · Most affected inspected pages

/
Critical
34 findings
/collections/easter/products/rabbit-sitting-on-basket
Critical
22 findings
/products/rabbit-sitting-on-basket
Critical
21 findings
/account/login
High
20 findings
/cart
High
18 findings

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 MONITORING SEE PRICING

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

Accessibility issues detected on herculescandy.com

Is herculescandy.com your website?

01 · Accessibility summary

02 · Start here

Buttons have no accessible name

Buttons have no accessible name

Buttons have no accessible name

Hidden elements can still receive keyboard focus

Interactive controls are not keyboard-accessible

03 · WCAG criteria affected

A scan shows today's exposure. Monitoring shows what changes next.

04 · All detected findings

Buttons have no accessible name

ARIA role is missing its required parent

Text has insufficient colour contrast

Hidden elements can still receive keyboard focus

Interactive controls are not keyboard-accessible

Form fields use placeholder text as the only label

Interactive controls must not be nested

Navigation regions are not distinguishable

ARIA attributes have invalid values

05 · Most affected inspected pages

06 · About this assessment

07 · Continuous monitoring

Reports with similar accessibility findings