Compliance
· 23 checks — WCAG, consent & privacy, language, viewport, cookie inventory, and legal pages rolled into one auditable list.FGDPR Article 13 DisclosuresAction1 / 8 Art. 13 categories matched in homepage bodyFIX
FLegal Page EcosystemAction0 of 7 expected legal pages detectedFIX
BViewport ConfigurationViewport properly configuredREVIEW
Responsive layout enabled
Correct initial zoom level
Accessibility-friendly — users can zoom
BAccessibility StatementNo accessibility statement detectedREVIEW
BThird-Party Trackers14 trackers detectedREVIEW
BTracking Pixel Inventory2 tracking pixel(s) on the pageREVIEW
CCopyright NoticeActionNo copyright notice detectedREVIEW
Copyright exists automatically — a notice is standard practice but not legally required.
BCompliance Badges1 compliance badge(s) detectedREVIEW
Detected by: body text
Evidence: bbb
A+WCAG ComplianceNo testable criteriaPASS
0
Passed
0
Failed
0
Partial
0
Manual review
0
Not tested
Key accessibility barriers
Links with unclear purpose
145 link(s) have empty or generic text
Screen reader users navigating by link list
Images without alt text
Screen reader users cannot understand 3 image(s)
~8M screen reader users in the US
Form controls without labels
Assistive technology cannot identify 3 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+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.
A+Consent UX DepthNo consent-UX depth issues detectedPASS
A+Tracker Inventory1 known tracker(s) detectedPASS
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+Hreflang ConfigurationNo hreflang tags on this pagePASS
A+Internationalization ExtrasNo additional i18n signals detectedPASS
A+Readability & TypographyFont sizes and tap targets checkedPASS
A+Browser FingerprintingNo browser-fingerprinting libraries detectedPASS
A+Beacon Tracking (sendBeacon)No navigator.sendBeacon usage detected in inline scriptsPASS
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.
Health Insurance Portability and Accountability Act — protects sensitive patient health information.
Indicators detected
- Text mentions: phi
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 Scores7503 words, Flesch-Kincaid grade 18.5INFO
Readability Analysis (Flesch-Kincaid)
Grade Level
18.5
Grade 18 (college+)
Reading Ease
12
Very Difficult
Words
7503
Sentences
272