Compliance
· 23 checks — WCAG, consent & privacy, language, viewport, cookie inventory, and legal pages rolled into one auditable list.FGDPR Article 13 DisclosuresAction0 / 8 Art. 13 categories matched in homepage bodyFIX
FThird-Party TrackersAction8 trackers detectedFIX
FLegal Page EcosystemAction0 of 7 expected legal pages detectedFIX
CViewport ConfigurationActionViewport prevents zoomingREVIEW
Responsive layout enabled
Correct initial zoom level
User zooming BLOCKED
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.
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
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
Images without alt text
Screen reader users cannot understand 18 image(s)
~8M screen reader users in the US
Links with unclear purpose
1 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
ACookie Consent & PrivacyNo consent signals detectedPASS
Pre-consent Cookies
This is an automated check, not legal advice. Consult a privacy professional for GDPR/CCPA compliance.
No privacy-policy link was found in the rendered page, but https://jaga.id/privacy responded. Verify the page is real and link it from the footer -- an unlinked policy is hard for visitors to find, and a scanner cannot confirm one exists from the URL alone.
A privacy-policy URL responded, but no link to it was found on the page.
Learn more ▾ ▴
GDPR Article 12 expects the notice to be easily accessible. An unlinked policy fails that even when the page exists. Add a footer link. The URL was checked with a HEAD request only, so verify it renders the policy rather than a catch-all app shell.
Source: GDPR Article 12
These cookies could not be matched to a known tracker or to a known essential-cookie family, so the scanner cannot tell whether consent was required. Verify each is strictly necessary; if any is analytics or advertising, it needs consent first. Unrecognized (treated as non-essential): session_id
Cookies the scanner could not identify were set before any consent UI existed -- verify each is strictly necessary.
Learn more ▾ ▴
These cookies matched neither a known tracker nor a known essential-cookie family, so this is a prompt to check, not a finding of violation. Name each cookie's purpose: session, CSRF, load-balancer affinity and locale are exempt under ePrivacy Art 5(3); analytics and advertising are not and must wait for consent. Renaming cookies to something recognizable also helps every other scanner your customers run.
Source: ePrivacy Directive Art 5(3)
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 Inventory5 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+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
A+Copyright Notice© 2026 Komisi Pemberantasan KorupsiPASS
© 2026 Komisi Pemberantasan Korupsi
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 Sharing4 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 Scores392 words, Flesch-Kincaid grade 30.2INFO
Readability Analysis (Flesch-Kincaid)
Grade Level
30.2
Grade 30 (college+)
Reading Ease
-58
Very Difficult
Words
392
Sentences
11