Skip to content
https://www.rsea.com.au

Compliance

· 23 checks — WCAG, consent & privacy, language, viewport, cookie inventory, and legal pages rolled into one auditable list.
SCORE
63
GRADE
D
FIX
1
REVIEW
7
PASS
12
INFO
3
Checks
23
12 PASS 7 REVIEW 1 FIX
F
GDPR Article 13 Disclosures
Action
1 / 8 Art. 13 categories matched in homepage body
FIX
1 / 8 Art. 13 categories matched in homepage body
Warning::
GDPR Article 13 disclosure coverage: 1 / 8 categories
Scanned the homepage body text AND the linked /privacy page for GDPR Article 13 disclosures. Matched 1 of 8 categories: Recipients of personal data. 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, 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: 1/8
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, maximum-scale=1.0 Expected: width=device-width, initial-scale=1 (without zoom restrictions)
Viewport Configuration Problem
Content
width=device-width, initial-scale=1, maximum-scale=1.0
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
Accessibility Statement
No accessibility statement detected
REVIEW
No accessibility statement detected
Warning::
No accessibility statement detected
Sites are increasingly expected to publish an accessibility statement. Required by EU Web Accessibility Directive 2016/2102 for public-sector bodies; recommended best practice elsewhere. Common URLs: /accessibility, /accessibility-statement, /a11y.
B
Third-Party Trackers
10 trackers detected
REVIEW
10 trackers detected
Info::
10 third-party trackers detected
Found 6 analytics, 0 advertising, 2 marketing, 1 tag manager, 1 session-replay, 0 heatmap trackers.
Got: 10 trackers
Warning::
1 session-replay tool(s) detected (Inspectlet)
Session-replay tools record what users type, click, and scroll. Under GDPR these are high-risk processing requiring explicit consent and (per UK ICO and French CNIL guidance) often a Data Protection Impact Assessment. Mask sensitive form fields and gate firing on user consent.
B
Cross-Site Cookies (SameSite=None)
2 cross-site cookie(s) (1 tracking-shaped, 1 essential)
REVIEW
2 cross-site cookie(s) (1 tracking-shaped, 1 essential)
Info::
1 tracking-shaped cross-site cookie(s): dynamicServiceSessionId
Cookies with SameSite=None travel in cross-site contexts (third-party iframes, cross-origin POSTs, embedded widgets). With third-party cookies dying in Chrome/Firefox, the legitimate use cases narrowed to SSO + payment widgets + federated auth. Each tracking-shaped cookie surfaced here is a cross-site analytics or ad-tech surface that needs explicit privacy-policy disclosure beyond basic cookie banner consent. Audit each: is it conditional on consent? Does the privacy policy name the recipient + purpose? Switching to SameSite=Lax disables the cross-site travel without breaking same-site analytics.
B
Compliance Badges
1 compliance badge(s) detected
REVIEW
1 compliance badge(s) detected
Info::
TRUSTe / TrustArc badge detected
Found via body text: 'truste'. Note: the presence of a badge does not verify the certification is current or valid.
Got: Detected by: body text
SOC 2
ISO 27001
PCI DSS
GDPR Certified
HIPAA Compliant
Better Business Bureau
TRUSTe / TrustArc detected

Detected by: body text

Evidence: truste

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

Form controls without labels

Assistive technology cannot identify 27 input(s)

Screen reader and voice-control users

Images without alt text

Screen reader users cannot understand 3 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+
Tracker Inventory
6 known tracker(s) detected
PASS
6 known tracker(s) detected
Info::
6 known tracker(s) detected
Inventory of trackers loaded by the page (matched against a curated SDK URL registry): tag-manager: Google Tag Manager | analytics: Google Analytics 4 | marketing: LinkedIn Insight, TikTok Pixel, Meta Pixel | session-replay: Inspectlet 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 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+
Hreflang Configuration
All 4 hreflang tag(s) look correct
PASS
All 4 hreflang tag(s) look correct
Info::
All 4 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+
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+
Beacon Tracking (sendBeacon)
No navigator.sendBeacon usage detected in inline scripts
PASS
No navigator.sendBeacon usage detected in inline scripts
Info::
No navigator.sendBeacon usage detected in inline scripts
Regulatory Indicators
2 regulatory indicator(s) detected
INFO
2 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 (moderate confidence)
Indicators suggesting GDPR may be relevant: Privacy policy page found. EU General Data Protection Regulation — governs collection and processing of personal data of EU residents.
Got: 1 indicators: Privacy policy page found
Info::
PCI-DSS indicators detected (strong confidence)
Indicators suggesting PCI-DSS may be relevant: Payment processor detected: paypal.com; Payment processor detected: braintreegateway.com; Payment processor detected: braintreegateway.com. Payment Card Industry Data Security Standard — applies to organizations handling credit card data.
Got: 3 indicators: Payment processor detected: paypal.com, Payment processor detected: braintreegateway.com, Payment processo…

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 Moderate

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

Indicators detected

  • Privacy policy page found
PCI-DSS Strong

Payment Card Industry Data Security Standard — applies to organizations handling credit card data.

Indicators detected

  • Payment processor detected: paypal.com
  • Payment processor detected: braintreegateway.com
  • Payment processor detected: braintreegateway.com
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 4 categories
6 third-party services detected across 4 categories: Analytics (1), Tag Management (1), Advertising (3), Payment (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::
LinkedIn Insight (Advertising)
Detected via script URL. Typically collects: Page views, Conversions, Ad targeting, Professional demographics. Privacy policy: https://www.linkedin.com/legal/privacy-policy. Data Processing Agreement available.
Got: Category: Advertising | Data types: Page views, Conversions, Ad targeting, Professional demographics
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::
PayPal (Payment)
Detected via script URL. Typically collects: Payment data, Transaction details, User identity. Privacy policy: https://www.paypal.com/us/legalhub/privacy-full. Data Processing Agreement available.
Got: Category: Payment | Data types: Payment data, Transaction details, User identity
Analytics (1)
Tag Management (1)
Advertising (3)
Payment (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 ✓
LinkedIn Insight Advertising
Detected by: script URL
Data typically collected:
Page viewsConversionsAd targetingProfessional demographics
Privacy policy → DPA available ✓
TikTok Pixel Advertising
Detected by: script URL
Data typically collected:
Page viewsConversionsAd targeting
Privacy policy → DPA available ✓
PayPal Payment
Detected by: script URL
Data typically collected:
Payment dataTransaction detailsUser 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
3132 words, Flesch-Kincaid grade 19.1
INFO

Readability Analysis (Flesch-Kincaid)

Grade Level

19.1

Grade 19 (college+)

Reading Ease

25

Very Difficult

Words

3132

Sentences

83

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

Send Feedback