Compliance
· 12 checks — WCAG, consent & privacy, language, viewport, cookie inventory, and legal pages rolled into one auditable list.FThird-Party TrackersAction10 trackers detectedFIX
BCookie Consent & PrivacyNo consent signals detectedREVIEW
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.
BLegal Page Ecosystem3 of 7 expected legal pages detectedREVIEW
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
Links with unclear purpose
4 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
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+Viewport ConfigurationViewport properly configuredPASS
Responsive layout enabled
Correct initial zoom level
Accessibility-friendly — users can zoom
Regulatory Indicators3 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
California Consumer Privacy Act — gives California residents rights over their personal data.
Indicators detected
- Text mentions: do not sell
- Link URL pattern: /pages/do-not-sell-my-data
- Link text: Do Not Sell My Data
Americans with Disabilities Act / Section 508 — requires digital accessibility for people with disabilities.
Indicators detected
- Accessibility statement page found
Third-Party Data Sharing3 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 Scores1858 words, Flesch-Kincaid grade 9.9INFO
Readability Analysis (Flesch-Kincaid)
Grade Level
9.9
Grade 10 (high school)
Reading Ease
57
Fairly Difficult
Words
1858
Sentences
102