Compliance
· 23 checks — WCAG, consent & privacy, language, viewport, cookie inventory, and legal pages rolled into one auditable list.FGDPR Article 13 DisclosuresAction1 / 8 Art. 13 categories matched in homepage bodyFIX
BCookie Consent & Privacyprivacy policy foundREVIEW
Pre-consent Cookies
This is an automated check, not legal advice. Consult a privacy professional for GDPR/CCPA compliance.
Unrecognized (treated as non-essential): cid
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.
BAccessibility StatementNo accessibility statement detectedREVIEW
BLegal Page Ecosystem3 of 7 expected legal pages detectedREVIEW
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
Links with unclear purpose
29 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 ConfigurationAll 87 hreflang tag(s) look correctPASS
A+Internationalization ExtrasNo additional i18n signals detectedPASS
A+Readability & TypographyFont sizes and tap targets checkedPASS
A+Viewport ConfigurationViewport properly configuredPASS
Responsive layout enabled
Correct initial zoom level
Accessibility-friendly — users can zoom
A+Third-Party Trackers4 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
A+Copyright Notice© 2026 StripePASS
© 2026 Stripe
Regulatory Indicators1 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.
EU General Data Protection Regulation — governs collection and processing of personal data of EU residents.
Indicators detected
- Privacy policy page found
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 Scores2113 words, Flesch-Kincaid grade 10.5INFO
Readability Analysis (Flesch-Kincaid)
Grade Level
10.5
Grade 10 (high school)
Reading Ease
43
Difficult
Words
2113
Sentences
162