Compliance
· 13 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
FLegal Page EcosystemAction1 of 7 expected legal pages detectedFIX
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
30 link(s) have empty or generic text
Screen reader users navigating by link list
Images without alt text
Screen reader users cannot understand 1 image(s)
~8M screen reader users in the US
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+Cookie Consent & Privacyprivacy policy foundPASS
This is an automated check, not legal advice. Consult a privacy professional for GDPR/CCPA compliance.
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.
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+Third-Party Trackers3 trackers detectedPASS
Regulatory Indicators1 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
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 Scores245 words, Flesch-Kincaid grade 14.1INFO
Readability Analysis (Flesch-Kincaid)
Grade Level
14.1
Grade 14 (college+)
Reading Ease
34
Difficult
Words
245
Sentences
11