Compliance
· 13 checks — WCAG, consent & privacy, language, viewport, cookie inventory, and legal pages rolled into one auditable list.FLanguage & i18nActionMissing <html lang>FIX
The lang attribute on <html> is required for screen readers and WCAG 3.1.1 compliance.
Without a lang attribute, screen readers mispronounce every word on the page.
Learn more ▾ ▴
An HTML element without lang="..." causes screen readers to fall back to the user's default voice — a French page read in English sounds like nonsense. Setting lang on the <html> element is a one-character fix that lets every assistive tool pronounce content correctly.
Source: W3C WCAG 2.1
FLegal Page EcosystemAction0 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.
CViewport ConfigurationActionViewport prevents zoomingREVIEW
Responsive layout enabled
Correct initial zoom level
User zooming BLOCKED
User zooming BLOCKED
WCAG 1.4.4 violation — users with low vision cannot zoom. Remove user-scalable=no and set maximum-scale to at least 5.0.
user-scalable=no or maximum-scale < 2 prevents users from zooming. This is a WCAG 1.4.4 (Level AA) failure and an accessibility barrier for users with low vision.
user-scalable=no is a WCAG 1.4.4 failure and creates ADA/EAA legal exposure — low-vision users rely on pinch-zoom every day.
Learn more ▾ ▴
Setting user-scalable=no (or maximum-scale=1) in the viewport meta blocks pinch-zoom. WCAG 2.1 success criterion 1.4.4 (Resize Text) requires zoom up to 200%. ADA lawsuits against inaccessible US sites have risen sharply; the EU Accessibility Act adds another enforcement layer in 2025. Remove user-scalable and maximum-scale from the viewport meta.
Source: WCAG 2.1 SC 1.4.4 / ADA / EAA
CThird-Party TrackersAction2 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 4 image(s)
~8M screen reader users in the US
Links with unclear purpose
4 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
A+Readability & TypographyFont sizes and tap targets checkedPASS
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 Sharing1 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 Scores9 words, Flesch-Kincaid grade 0.0INFO
Readability Analysis (Flesch-Kincaid)
Grade Level
0.0
Grade 5 (easy)
Reading Ease
0
Very Difficult
Words
9
Sentences
2