Compliance
· 23 checks — WCAG, consent & privacy, language, viewport, cookie inventory, and legal pages rolled into one auditable list.DGDPR Article 13 DisclosuresAction0 / 8 Art. 13 categories matched in homepage bodyFIX
FLegal Page EcosystemAction0 of 7 expected legal pages detectedFIX
BCookie Consent & PrivacyNo consent signals detectedREVIEW
Pre-consent Cookies
This is an automated check, not legal advice. Consult a privacy professional for GDPR/CCPA compliance.
No link matching the privacy-policy vocabulary was found in the rendered page, and the common privacy-policy paths returned nothing. A privacy policy page is recommended for transparency and may be legally required.
No privacy policy was found in the page or at any common path — GDPR, CCPA and most privacy laws require one.
Learn more ▾ ▴
The rendered page links no privacy policy and the well-known paths (/privacy, /gdpr, and their localized variants) returned nothing. 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 EUR 10M or 2% of global revenue, whichever is higher.
Source: GDPR Article 13 / CCPA
These cookies could not be matched to a known tracker or to a known essential-cookie family, so the scanner cannot tell whether consent was required. Verify each is strictly necessary; if any is analytics or advertising, it needs consent first. Unrecognized (treated as non-essential): redirex-original
Cookies the scanner could not identify were set before any consent UI existed -- verify each is strictly necessary.
Learn more ▾ ▴
These cookies matched neither a known tracker nor a known essential-cookie family, so this is a prompt to check, not a finding of violation. Name each cookie's purpose: session, CSRF, load-balancer affinity and locale are exempt under ePrivacy Art 5(3); analytics and advertising are not and must wait for consent. Renaming cookies to something recognizable also helps every other scanner your customers run.
Source: ePrivacy Directive Art 5(3)
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.
BLanguage & i18nLang attribute presentREVIEW
Use a valid BCP 47 language tag (e.g. 'en', 'fr', 'de-DE').
An invalid lang code (typo, made-up value) causes screen readers to fall back to user-default voice — content gets mispronounced.
Learn more ▾ ▴
lang values must be valid BCP 47 language tags (e.g., 'en', 'en-US', 'fr', 'zh-Hans'). Common typos: 'eng' (should be 'en'), 'EN_US' (should be 'en-US'). Invalid values silently degrade to the user's default voice. Validate against the IANA language subtag registry.
Source: BCP 47 / IANA Language Subtag Registry
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
BAccessibility StatementNo accessibility statement detectedREVIEW
CThird-Party TrackersAction2 trackers 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
Images without alt text
Screen reader users cannot understand 1 image(s)
~8M screen reader users in the US
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
A+Hreflang ConfigurationNo hreflang tags on this pagePASS
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+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 giocodigitalePASS
© 2026 giocodigitale
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 Scores32 words, Flesch-Kincaid grade 12.5INFO
Readability Analysis (Flesch-Kincaid)
Grade Level
12.5
Grade 12 (college+)
Reading Ease
24
Very Difficult
Words
32
Sentences
3