Compliance
· 23 checks — WCAG, consent & privacy, language, viewport, cookie inventory, and legal pages rolled into one auditable list.FViewport ConfigurationActionNo viewport meta tagFIX
No viewport meta tag found. Mobile devices will render at desktop width.
<meta name="viewport" content="width=device-width, initial-scale=1">Without a viewport meta tag, the page will not render correctly on mobile devices.
No viewport meta means mobile browsers render at desktop width and shrink — unusable on phones, fails WCAG reflow.
Learn more ▾ ▴
Mobile browsers default to a 980px viewport for legacy desktop layouts. Setting `<meta name="viewport" content="width=device-width, initial-scale=1">` opts into responsive rendering. Without it, the page renders zoomed out and users have to pinch-zoom to interact.
Source: MDN Viewport / WCAG 1.4.10
FGDPR Article 13 DisclosuresAction0 / 8 Art. 13 categories matched in homepage bodyFIX
DLegal Page EcosystemAction2 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. The common privacy-policy paths were not probed for this scan, so this is an unconfirmed absence and is excluded from the regulatory-risk estimate.
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
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): yandex_gid, yp, is_gdpr, is_gdpr_b, _yasc, pi, i, yandexuid, yashr, bh
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.
BAccessibility StatementNo accessibility statement detectedREVIEW
CThird-Party TrackersAction2 trackers detectedREVIEW
BBeacon Tracking (sendBeacon)1 sendBeacon call site(s) in inline scriptsREVIEW
CCopyright NoticeActionNo copyright notice detectedREVIEW
Copyright exists automatically — a notice is standard practice but not legally required.
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 1 input(s)
Screen reader and voice-control users
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 11 hreflang tag(s) look correctPASS
A+Internationalization ExtrasNo additional i18n signals detectedPASS
A+Readability & TypographyFont sizes and tap targets checkedPASS
A+Tracking Pixel InventoryNo image data to inspect for tracking pixelsPASS
A+Browser FingerprintingNo browser-fingerprinting libraries detectedPASS
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 Scores188 words, Flesch-Kincaid grade 13.6INFO
Readability Analysis (Flesch-Kincaid)
Grade Level
13.6
Grade 14 (college+)
Reading Ease
25
Very Difficult
Words
188
Sentences
12