Compliance
· 13 checks — WCAG, consent & privacy, language, viewport, cookie inventory, and legal pages rolled into one auditable list.FThird-Party TrackersAction21 trackers detectedFIX
CLegal Page EcosystemAction2 of 7 expected legal pages detectedREVIEW
BCompliance Badges1 compliance badge(s) detectedREVIEW
Detected by: link URL
Evidence: https://preferences-mgr.truste.com/?pid=crain01&aid=crain01&type=crain&site=crain.com&action=notice&country=us&locale=en&behavior=implied&privacypolicylink=http%253a%252f%252fwww.autonews.com%252fsection%252fprivacy-policy&from=http%3a//consent.trustarc.com/
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 2 image(s)
~8M screen reader users in the US
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
ACookie Consent & PrivacyTrustArc detectedPASS
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.
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+Viewport ConfigurationViewport properly configuredPASS
Responsive layout enabled
Correct initial zoom level
Accessibility-friendly — users can zoom
A+Copyright NoticeCopyright © 2026PASS
Copyright © 2026
Regulatory Indicators2 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
- Consent management platform detected: trustarc.com
- Privacy policy page found
Payment Card Industry Data Security Standard — applies to organizations handling credit card data.
Indicators detected
- Payment processor detected: js.stripe.com
Third-Party Data Sharing7 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 Scores1805 words, Flesch-Kincaid grade 20.9INFO
Readability Analysis (Flesch-Kincaid)
Grade Level
20.9
Grade 21 (college+)
Reading Ease
17
Very Difficult
Words
1805
Sentences
45