Compliance
· 23 checks — WCAG, consent & privacy, language, viewport, cookie inventory, and legal pages rolled into one auditable list.DCookie Consent & PrivacyActionUsercentrics detectedFIX
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
A consent banner is present but non-essential cookies were already set on the initial response, before the banner could be acknowledged. Configure the CMP to gate tag firing on user consent. Unrecognized (treated as non-essential): CLOUDWAFSESID, CLOUDWAFSESTIME
A consent banner exists but trackers fire BEFORE the user clicks -- still a GDPR violation. Strict liability under EU DPA enforcement.
Learn more ▾ ▴
The presence of a banner is not consent. ePrivacy + GDPR Art. 7 require AFFIRMATIVE acknowledgment before non-essential cookies are set. Reconfigure the CMP to gate tag firing on user consent: most platforms (OneTrust, Cookiebot, Didomi) provide a 'block until consent' or 'consent mode' setting that delays tracker scripts until the banner is acknowledged.
Source: GDPR Article 7 / ePrivacy Directive / IAB TCF v2.2
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.
FGDPR Article 13 DisclosuresAction0 / 8 Art. 13 categories matched in homepage bodyFIX
FLegal Page EcosystemAction1 of 7 expected legal pages detectedFIX
DCopyright NoticeAction© 2022 | A product of eVergabeFIX
© 2022 | A product of eVergabe
BAccessibility StatementNo accessibility statement detectedREVIEW
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
Form controls without labels
Assistive technology cannot identify 2 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
AConsent UX Depth1 consent-UX signal(s) surfacedPASS
A+Tracker InventoryNo known trackers detected on this pagePASS
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+Viewport ConfigurationViewport properly configuredPASS
Responsive layout enabled
Correct initial zoom level
Accessibility-friendly — users can zoom
A+Third-Party TrackersNo third-party trackers detectedPASS
A+Tracking Pixel InventoryNo tracking pixels detectedPASS
A+Browser FingerprintingNo browser-fingerprinting libraries detectedPASS
A+Beacon Tracking (sendBeacon)No navigator.sendBeacon usage detected in inline scriptsPASS
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 Scores917 words, Flesch-Kincaid grade 15.7INFO
Readability Analysis (Flesch-Kincaid)
Grade Level
15.7
Grade 16 (college+)
Reading Ease
20
Very Difficult
Words
917
Sentences
43