Compliance
· 13 checks — WCAG, consent & privacy, language, viewport, cookie inventory, and legal pages rolled into one auditable list.DThird-Party TrackersAction6 trackers detectedFIX
FLegal Page EcosystemAction1 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.
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
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.
BViewport ConfigurationViewport properly configuredREVIEW
Responsive layout enabled
Correct initial zoom level
Accessibility-friendly — users can zoom
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
3 link(s) have empty or generic text
Screen reader users navigating by link list
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
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+Readability & TypographyFont sizes and tap targets checkedPASS
A+Copyright Notice© 2006–2026 LLC VK We apply recommended technologies MorePASS
© 2006–2026 LLC VK We apply recommended technologies More
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 Sharing2 third-party service(s) detectedINFO
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 Scores207 words, Flesch-Kincaid grade 11.9INFO
Readability Analysis (Flesch-Kincaid)
Grade Level
11.9
Grade 12 (high school)
Reading Ease
56
Fairly Difficult
Words
207
Sentences
8