Compliance
· 7 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
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.
CThird-Party TrackersAction2 trackers detectedREVIEW
A+WCAG ComplianceNo testable criteriaPASS
0
Passed
0
Failed
0
Partial
0
Manual review
0
Not tested
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