Evolize inspected 5 public pages on hatattack.com and detected 14 accessibility findings. The most widespread issue was "Interactive controls are not keyboard-accessible", detected on 5 inspected pages. The most affected inspected page was "/products/mimi-basket", where 9 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) · 5 inspected pages · 5 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.
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.
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 class="btn btn--hollow btn--fade" href="/collections/spring-summer-2026">DISCOVER THE COLLECTION</a>
Medium
Carousel has no accessible controls
WCAG 2.1.1 (A)7 instances5 inspected pages
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.
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 <summary>'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.
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.