Skip to content
https://nanajacqueline.com

Compliance

· 23 checks — WCAG, consent & privacy, language, viewport, cookie inventory, and legal pages rolled into one auditable list.
SCORE
63
GRADE
D
FIX
3
REVIEW
5
PASS
12
INFO
3
Checks
23
12 PASS 5 REVIEW 3 FIX
F
GDPR Article 13 Disclosures
Action
0 / 8 Art. 13 categories matched in homepage body
FIX
0 / 8 Art. 13 categories matched in homepage body
Warning::
GDPR Article 13 disclosure coverage: 0 / 8 categories
Scanned the homepage body text AND the linked /privacy page for GDPR Article 13 disclosures. Matched 0 of 8 categories: . Missing: Data Protection Officer contact (where applicable), Data retention period, Data subject rights (access, erasure, rectification, etc.), Identity / contact details of the data controller, International data transfers, Legal basis for processing, Recipients of personal data, Right to lodge a complaint with a supervisory authority. Note: only the FIRST same-origin privacy-policy link is followed; deeper sub-pages (e.g. /legal/data-subject-rights) are not fetched.
Got: 0/8
D
Third-Party Trackers
Action
11 trackers detected
FIX
11 trackers detected
Info::
11 third-party trackers detected
Found 5 analytics, 1 advertising, 4 marketing, 1 tag manager, 0 session-replay, 0 heatmap trackers.
Got: 11 trackers
Warning::
1 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 11 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.
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.0, maximum-scale=1.0, viewport-fit=cover Expected: width=device-width, initial-scale=1 (without zoom restrictions)
Viewport Configuration Problem
Content
width=device-width, initial-scale=1.0, maximum-scale=1.0, viewport-fit=cover
width=device-width

Responsive layout enabled

initial-scale=1

Correct initial zoom level

maximum-scale=1.0

Restricts zoom — set to 5.0 or higher, or remove entirely

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

B
Beacon Tracking (sendBeacon)
1 sendBeacon call site(s) in inline scripts
REVIEW
1 sendBeacon call site(s) in inline scripts
Info::
1 navigator.sendBeacon call site(s) in inline scripts
navigator.sendBeacon() fires fire-and-forget POSTs in the background after page-unload -- typically used for last-second analytics (read-time, scroll depth, exit-intent). Ad-blockers' XHR/fetch interception often misses them (different API path); DevTools shows beacon requests typed as "ping" instead of "fetch", which is easy to overlook in privacy reviews. Audit each call site: what data is being sent? Is the recipient disclosed in the privacy policy? Is the call gated behind cookie-banner consent? Does the user have a way to opt out of the page-unload tracking specifically (separate from in-session analytics)? Detection is limited to inline scripts -- beacons in external SDKs aren't visible to this static scan.
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

32 link(s) have empty or generic text

Screen reader users navigating by link list

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+
Tracker Inventory
2 known tracker(s) detected
PASS
2 known tracker(s) detected
Info::
2 known tracker(s) detected
Inventory of trackers loaded by the page (matched against a curated SDK URL registry): analytics: Google Analytics 4 | marketing: Meta Pixel Each entry maps a script URL pattern to a known vendor SDK. This is purely informational -- consent posture / pre-consent firing is graded by the consent analyzer.
A+
Language & i18n
Lang attribute + Content-Language header
PASS
Lang attribute + Content-Language header
Info::
<html lang> attribute is present
Info::
<html lang> value is valid
Info::
Content-Language header is set
Got: en-US
Info::
Language signals are consistent
Page Language DetectedContent-Language Header en-USConsistent Yes
A+
Hreflang Configuration
All 6 hreflang tag(s) look correct
PASS
All 6 hreflang tag(s) look correct
Info::
All 6 hreflang tag(s) look correct
A+
Internationalization Extras
No additional i18n signals detected
PASS
No additional i18n signals detected
Info::
No additional i18n signals detected
A+
Readability & Typography
Font sizes and tap targets checked
PASS
Font sizes and tap targets checked
A
Accessibility Statement
Statement found, no conformance level
PASS
Statement found, no conformance level
Info::
Accessibility statement found but lacks WCAG conformance level
Mature accessibility statements declare a target conformance level (e.g., WCAG 2.1 AA). Without a stated level, users and reviewers cannot tell what the statement actually commits to.
Got: /pages/accessibility-statement
A+
Tracking Pixel Inventory
No tracking pixels detected
PASS
No tracking pixels detected
Info::
No tracking pixels detected
A+
Browser Fingerprinting
No browser-fingerprinting libraries detected
PASS
No browser-fingerprinting libraries detected
Info::
No browser-fingerprinting libraries detected
A+
Cross-Site Cookies (SameSite=None)
No SameSite=None cookies -- no cross-site travel surface
PASS
No SameSite=None cookies -- no cross-site travel surface
Info::
No cookies opted in to cross-site travel (SameSite=None)
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::
ADA indicators detected (moderate confidence)
Indicators suggesting ADA may be relevant: Accessibility statement page found. Americans with Disabilities Act / Section 508 — requires digital accessibility for people with disabilities.
Got: 1 indicators: Accessibility statement 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.

ADA Moderate

Americans with Disabilities Act / Section 508 — requires digital accessibility for people with disabilities.

Indicators detected

  • Accessibility statement page found
Third-Party Data Sharing
3 third-party service(s) detected
INFO
3 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::
3 third-party services across 3 categories
3 third-party services detected across 3 categories: Analytics (1), Advertising (1), Customer Support (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::
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::
Zendesk (Customer Support)
Detected via script URL. Typically collects: Support tickets, Chat transcripts, User identity. Privacy policy: https://www.zendesk.com/company/agreements-and-terms/privacy-policy/. Data Processing Agreement available.
Got: Category: Customer Support | Data types: Support tickets, Chat transcripts, User identity
Analytics (1)
Advertising (1)
Customer Support (1)
Google Analytics Analytics
Detected by: script URL
Data typically collected:
Page viewsUser behaviorDemographicsDevice infoIP address
Privacy policy → DPA available ✓
Facebook Pixel Advertising
Detected by: script URL
Data typically collected:
Page viewsConversionsUser behaviorAd targeting
Privacy policy → DPA available ✓
Zendesk Customer Support
Detected by: script URL
Data typically collected:
Support ticketsChat transcriptsUser identity
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
1290 words, Flesch-Kincaid grade 72.7
INFO

Readability Analysis (Flesch-Kincaid)

Grade Level

72.7

Grade 73 (college+)

Reading Ease

-423

Very Difficult

Words

1290

Sentences

766

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

Send Feedback