Skip to content
https://ridge.com

Compliance

· 12 checks — WCAG, consent & privacy, language, viewport, cookie inventory, and legal pages rolled into one auditable list.
SCORE
74
GRADE
C
FIX
1
REVIEW
4
PASS
4
INFO
3
Checks
12
4 PASS 4 REVIEW 1 FIX
F
Third-Party Trackers
Action
21 trackers detected
FIX
21 trackers detected
Info::
21 third-party trackers detected
Found 10 analytics, 6 advertising, 4 marketing, 1 tag manager trackers.
Got: 21 trackers
Warning::
6 advertising/retargeting trackers detected
Advertising trackers collect user data for ad targeting. Under GDPR, these typically require explicit consent.
Warning::
Trackers detected but no cookie policy found
This page loads 21 trackers but no cookie policy was detected. GDPR requires disclosure when using tracking cookies.
Warning::
Trackers detected but no privacy policy found
Most data protection regulations require a privacy policy when collecting user data via trackers.
Warning::
Session replay tool detected: Hotjar
Session replay tools record user interactions. These require clear disclosure and often explicit consent under GDPR.
C
Viewport Configuration
Action
Viewport prevents zooming
REVIEW
Viewport prevents zooming
Info::
Viewport meta tag is present
Info::
width=device-width is set
Critical::
Viewport prevents user zooming
user-scalable=no or maximum-scale < 2 prevents users from zooming. This is a WCAG 1.4.4 (Level AA) failure and an accessibility barrier for users with low vision.
Got: width=device-width,initial-scale=1,user-scalable=0 Expected: width=device-width, initial-scale=1 (without zoom restrictions)
Viewport Configuration Problem
Content
width=device-width, initial-scale=1, user-scalable=0
width=device-width

Responsive layout enabled

initial-scale=1

Correct initial zoom level

user-scalable=0

User zooming BLOCKED

User zooming BLOCKED

WCAG 1.4.4 violation — users with low vision cannot zoom. Remove user-scalable=no and set maximum-scale to at least 5.0.

user-scalable=no or maximum-scale < 2 prevents users from zooming. This is a WCAG 1.4.4 (Level AA) failure and an accessibility barrier for users with low vision.

Why this matters

user-scalable=no is a WCAG 1.4.4 failure and creates ADA/EAA legal exposure — low-vision users rely on pinch-zoom every day.

Learn more

Setting user-scalable=no (or maximum-scale=1) in the viewport meta blocks pinch-zoom. WCAG 2.1 success criterion 1.4.4 (Resize Text) requires zoom up to 200%. ADA lawsuits against inaccessible US sites have risen sharply; the EU Accessibility Act adds another enforcement layer in 2025. Remove user-scalable and maximum-scale from the viewport meta.

Source: WCAG 2.1 SC 1.4.4 / ADA / EAA

C
Compliance Badges
Action
0 compliance badge(s) detected
REVIEW
0 compliance badge(s) detected
Info::
No compliance badges detected
No recognized compliance certification badges or seals were found. This is common — many sites do not display compliance badges.
SOC 2
ISO 27001
PCI DSS
GDPR Certified
HIPAA Compliant
Better Business Bureau
TRUSTe / TrustArc
Privacy Shield
McAfee SECURE / TrustedSite
Norton Secured
Badge detection is based on image alt text, link URLs, and page content. Detection does not verify that certifications are current or valid.
A+
WCAG Compliance
No testable criteria
PASS
No testable criteria
Level A
Level AA

0

Passed

0

Failed

0

Partial

0

Manual review

0

Not tested

Key accessibility barriers

Links with unclear purpose

57 link(s) have empty or generic text

Screen reader users navigating by link list

Form controls without labels

Assistive technology cannot identify 10 input(s)

Screen reader and voice-control users

Images without alt text

Screen reader users cannot understand 9 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
Language & i18n
Lang attribute present
PASS
Lang attribute present
Info::
<html lang> attribute is present
Info::
<html lang> value is valid
Info::
No Content-Language HTTP header
Info::
Language signals are inconsistent
The <html lang> attribute and Content-Language header should agree.
Page Language DetectedContent-Language Header Consistent No

The <html lang> attribute and Content-Language header should agree.

Why this matters

<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 & Typography
Font sizes and tap targets checked
PASS
Font sizes and tap targets checked
Regulatory Indicators
1 regulatory indicator(s) detected
INFO
1 regulatory indicator(s) detected
Info::
This is a technical scan, not a legal assessment
BeaverCheck detects technical indicators that may suggest regulatory relevance. This is not a compliance audit and should not be relied upon for legal decisions. Consult qualified legal counsel for compliance assessments.
Info::
GDPR indicators detected (strong confidence)
Indicators suggesting GDPR may be relevant: European TLD detected: .eu; Privacy policy page found. EU General Data Protection Regulation — governs collection and processing of personal data of EU residents.
Got: 2 indicators: European TLD detected: .eu, Privacy policy page found

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.

GDPR Strong

EU General Data Protection Regulation — governs collection and processing of personal data of EU residents.

Indicators detected

  • European TLD detected: .eu
  • Privacy policy page found
Third-Party Data Sharing
6 third-party service(s) detected
INFO
6 third-party service(s) detected
Info::
Data inventory for transparency purposes
This inventory identifies third-party services that receive data from your site visitors. Under regulations like GDPR (Article 30), maintaining records of data processing activities is commonly considered a best practice. This automated scan provides a starting point — it may not capture all data flows.
Info::
6 third-party services across 5 categories
6 third-party services detected across 5 categories: Analytics (1), Tag Management (1), Advertising (2), Session Recording (1), CDN (1). Each of these services receives some user data from your site visitors.
Info::
Google Analytics (Analytics)
Detected via script URL. Typically collects: Page views, User behavior, Demographics, Device info, IP address. Privacy policy: https://policies.google.com/privacy. Data Processing Agreement available.
Got: Category: Analytics | Data types: Page views, User behavior, Demographics, Device info, IP address
Info::
Google Tag Manager (Tag Management)
Detected via script URL. Typically collects: Orchestrates other tracking scripts, Page views. Privacy policy: https://policies.google.com/privacy. Data Processing Agreement available.
Got: Category: Tag Management | Data types: Orchestrates other tracking scripts, Page views
Info::
Facebook Pixel (Advertising)
Detected via script URL. Typically collects: Page views, Conversions, User behavior, Ad targeting. Privacy policy: https://www.facebook.com/privacy/policy. Data Processing Agreement available.
Got: Category: Advertising | Data types: Page views, Conversions, User behavior, Ad targeting
Info::
Hotjar (Session Recording)
Detected via script URL. Typically collects: Session recordings, Heatmaps, Click patterns, Form interactions. Privacy policy: https://www.hotjar.com/privacy/. Data Processing Agreement available.
Got: Category: Session Recording | Data types: Session recordings, Heatmaps, Click patterns, Form interactions
Info::
TikTok Pixel (Advertising)
Detected via script URL. Typically collects: Page views, Conversions, Ad targeting. Privacy policy: https://www.tiktok.com/legal/privacy-policy. Data Processing Agreement available.
Got: Category: Advertising | Data types: Page views, Conversions, Ad targeting
Info::
Cloudflare (CDN)
Detected via script URL. Typically collects: IP address (transient), Request metadata. Privacy policy: https://www.cloudflare.com/privacypolicy/. Data Processing Agreement available.
Got: Category: CDN | Data types: IP address (transient), Request metadata
Analytics (1)
Tag Management (1)
Advertising (2)
Session Recording (1)
CDN (1)
Google Analytics Analytics
Detected by: script URL
Data typically collected:
Page viewsUser behaviorDemographicsDevice infoIP address
Privacy policy → DPA available ✓
Google Tag Manager Tag Management
Detected by: script URL
Data typically collected:
Orchestrates other tracking scriptsPage views
Privacy policy → DPA available ✓
Facebook Pixel Advertising
Detected by: script URL
Data typically collected:
Page viewsConversionsUser behaviorAd targeting
Privacy policy → DPA available ✓
Hotjar Session Recording
Detected by: script URL
Data typically collected:
Session recordingsHeatmapsClick patternsForm interactions
Privacy policy → DPA available ✓
TikTok Pixel Advertising
Detected by: script URL
Data typically collected:
Page viewsConversionsAd targeting
Privacy policy → DPA available ✓
Cloudflare CDN
Detected by: script URL
Data typically collected:
IP address (transient)Request metadata
Privacy policy → DPA available ✓

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 Scores
1547 words, Flesch-Kincaid grade 11.8
INFO

Readability Analysis (Flesch-Kincaid)

Grade Level

11.8

Grade 12 (high school)

Reading Ease

47

Difficult

Words

1547

Sentences

76

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback