Compliance
· 23 checks — WCAG, consent & privacy, language, viewport, cookie inventory, and legal pages rolled into one auditable list.DCookie Consent & PrivacyActionNo consent signals detectedFIX
Pre-consent Cookies
This is an automated check, not legal advice. Consult a privacy professional for GDPR/CCPA compliance.
A privacy policy page is recommended for transparency and may be legally required.
GDPR, CCPA, and most other privacy laws require a published privacy policy — its absence is a per-violation fine.
Learn more ▾ ▴
If you collect any personal data (analytics counts), GDPR requires a clear privacy notice describing what you collect, why, and how to exercise data rights. Fines start at €10M or 2% of global revenue, whichever is higher. CCPA's penalties scale per affected user.
Source: GDPR Article 13 / CCPA
Unrecognized (treated as non-essential): BITRIX_SM_GUEST_ID, BITRIX_SM_LAST_VISIT
Setting tracking cookies without a consent banner is the single most-fined GDPR violation in EU enforcement actions.
Learn more ▾ ▴
GDPR + ePrivacy require opt-in BEFORE setting non-essential cookies. Loading Google Analytics, Facebook Pixel, or any third-party tracker on page load -- without a consent mechanism -- is the highest-frequency fine pattern in EU enforcement. Add a Consent Management Platform (Cookiebot, OneTrust, Klaro) that blocks tracker scripts until consent.
Source: GDPR + ePrivacy Directive / EU DPA enforcement
BeaverCheck detects technical indicators of consent management. This does not constitute a legal compliance assessment. Consult a privacy professional for GDPR/CCPA compliance.
Disclaimer: legal-page checks identify presence/absence; consult counsel for legal sufficiency.
FGDPR Article 13 DisclosuresAction0 / 8 Art. 13 categories matched in homepage bodyFIX
FLegal Page EcosystemAction0 of 7 expected legal pages detectedFIX
CViewport ConfigurationActionViewport prevents zoomingREVIEW
Responsive layout enabled
Correct initial zoom level
Restricts zoom — set to 5.0 or higher, or remove entirely
User zooming BLOCKED
WCAG 1.4.4 violation — users with low vision cannot zoom. Remove user-scalable=no and set maximum-scale to at least 5.0.
user-scalable=no or maximum-scale < 2 prevents users from zooming. This is a WCAG 1.4.4 (Level AA) failure and an accessibility barrier for users with low vision.
user-scalable=no is a WCAG 1.4.4 failure and creates ADA/EAA legal exposure — low-vision users rely on pinch-zoom every day.
Learn more ▾ ▴
Setting user-scalable=no (or maximum-scale=1) in the viewport meta blocks pinch-zoom. WCAG 2.1 success criterion 1.4.4 (Resize Text) requires zoom up to 200%. ADA lawsuits against inaccessible US sites have risen sharply; the EU Accessibility Act adds another enforcement layer in 2025. Remove user-scalable and maximum-scale from the viewport meta.
Source: WCAG 2.1 SC 1.4.4 / ADA / EAA
BAccessibility StatementNo accessibility statement detectedREVIEW
BCopyright Notice© 2025 Компания «МульчаREVIEW
© 2025 Компания «Мульча
CCompliance BadgesAction0 compliance badge(s) detectedREVIEW
A+WCAG ComplianceNo testable criteriaPASS
0
Passed
0
Failed
0
Partial
0
Manual review
0
Not tested
Key accessibility barriers
Form controls without labels
Assistive technology cannot identify 28 input(s)
Screen reader and voice-control users
Links with unclear purpose
7 link(s) have empty or generic text
Screen reader users navigating by link list
Automated testing covers ~30–40% of WCAG criteria. Manual review is recommended for full conformance.
Full WCAG 2.1 AA compliance checklist — paste into a client deliverable or ticket
A+Consent UX DepthNo consent-UX depth issues detectedPASS
A+Tracker InventoryNo known trackers detected on this pagePASS
ALanguage & i18nLang attribute presentPASS
The <html lang> attribute and Content-Language header should agree.
<html lang>, Content-Language, or og:locale disagree — pick one source of truth and align the others.
Learn more ▾ ▴
Browsers and assistive tech use different sources for language. When they disagree, behavior is undefined: some pronounce by <html lang>, some by Content-Language. Decide on the canonical language for the page and set all signals to match.
Source: WCAG 2.1 SC 3.1.1
A+Hreflang ConfigurationNo hreflang tags on this pagePASS
A+Internationalization ExtrasNo additional i18n signals detectedPASS
A+Readability & TypographyFont sizes and tap targets checkedPASS
A+Third-Party TrackersNo third-party trackers detectedPASS
A+Tracking Pixel InventoryNo tracking pixels detectedPASS
A+Browser FingerprintingNo browser-fingerprinting libraries detectedPASS
A+Beacon Tracking (sendBeacon)No navigator.sendBeacon usage detected in inline scriptsPASS
Regulatory Indicators0 regulatory indicator(s) detectedINFO
This is a technical scan, not a legal assessment.
BeaverCheck detects technical indicators that may suggest regulatory relevance. This should not be relied upon for legal decisions. Consult qualified legal counsel.
No specific regulatory indicators detected.
This does not mean no regulations apply.
Third-Party Data Sharing0 third-party service(s) detectedINFO
No recognized data-sharing services detected.
This inventory identifies services receiving visitor data.
Under regulations like GDPR Article 30, maintaining records of data processing is commonly considered a best practice. This scan provides a starting point.
Readability Scores1560 words, Flesch-Kincaid grade 3.1INFO
Readability Analysis (Flesch-Kincaid)
Grade Level
3.1
Grade 5 (easy)
Reading Ease
104
Very Easy
Words
1560
Sentences
89