Compliance
· 13 checks — WCAG, consent & privacy, language, viewport, cookie inventory, and legal pages rolled into one auditable list.FLegal Page EcosystemAction1 of 7 expected legal pages 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.
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
CThird-Party TrackersAction1 trackers 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
Images without alt text
Screen reader users cannot understand 37 image(s)
~8M screen reader users in the US
Links with unclear purpose
33 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+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 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 Scores370 words, Flesch-Kincaid grade 68.5INFO
Readability Analysis (Flesch-Kincaid)
Grade Level
68.5
Grade 68 (college+)
Reading Ease
-66
Very Difficult
Words
370
Sentences
2