Skip to content
https://www.pathofexile.com

Compliance

· 23 checks — WCAG, consent & privacy, language, viewport, cookie inventory, and legal pages rolled into one auditable list.
SCORE
67
GRADE
D
FIX
3
REVIEW
3
PASS
14
INFO
3
Checks
23
14 PASS 3 REVIEW 3 FIX
F
Viewport Configuration
Action
No viewport meta tag
FIX
No viewport meta tag
Critical::
No viewport meta tag found
Without a viewport meta tag, the page will not render correctly on mobile devices.
Expected: width=device-width, initial-scale=1
Viewport Configuration Missing

No viewport meta tag found. Mobile devices will render at desktop width.

Suggested viewport tag <meta name="viewport" content="width=device-width, initial-scale=1">

Without a viewport meta tag, the page will not render correctly on mobile devices.

Why this matters

No viewport meta means mobile browsers render at desktop width and shrink — unusable on phones, fails WCAG reflow.

Learn more ▾

Mobile browsers default to a 980px viewport for legacy desktop layouts. Setting `<meta name="viewport" content="width=device-width, initial-scale=1">` opts into responsive rendering. Without it, the page renders zoomed out and users have to pinch-zoom to interact.

Source: MDN Viewport / WCAG 1.4.10

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 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: this scan does not fetch the privacy policy sub-page; if Article 13 disclosures live there, they are not visible to this check.
Got: 0/8
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.
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

6 link(s) have empty or generic text

Screen reader users navigating by link list

Images without alt text

Screen reader users cannot understand 2 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
No known trackers detected on this page
PASS
No known trackers detected on this page
Info::
No known trackers detected on this page
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 10 hreflang tag(s) look correct
PASS
All 10 hreflang tag(s) look correct
Info::
All 10 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+
Third-Party Trackers
No third-party trackers detected
PASS
No third-party trackers detected
Info::
No third-party trackers detected
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)
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
0 regulatory indicator(s) detected
INFO
0 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::
No specific regulatory indicators detected
No strong signals for GDPR, CCPA, ADA, PCI, HIPAA, or COPPA were found. This does not mean these regulations don't apply — it means we didn't detect common technical indicators.

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 Sharing
0 third-party service(s) detected
INFO
0 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::
No recognized third-party data-sharing services detected
This page does not appear to load external tracking, analytics, or advertising scripts.

No recognized data-sharing services detected.

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
354 words, Flesch-Kincaid grade 15.7
INFO

Readability Analysis (Flesch-Kincaid)

Grade Level

15.7

Grade 16 (college+)

Reading Ease

45

Difficult

Words

354

Sentences

10

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

Send Feedback