Skip to content
https://tldp.org

Compliance

· 7 checks — WCAG, consent & privacy, language, viewport, cookie inventory, and legal pages rolled into one auditable list.
SCORE
67
GRADE
D
FIX
2
REVIEW
2
PASS
3
INFO
0
Checks
7
3 PASS 2 REVIEW 2 FIX
F
Language & i18n
Action
Missing <html lang>
FIX
Missing <html lang>
Warning::
<html lang> attribute is missing
The lang attribute on <html> is required for screen readers and WCAG 3.1.1 compliance.
Info::
No Content-Language HTTP header
Info::
Language signals are consistent
Page Language Content-Language Header Consistent Yes

The lang attribute on <html> is required for screen readers and WCAG 3.1.1 compliance.

Why this matters

Without a lang attribute, screen readers mispronounce every word on the page.

Learn more

An HTML element without lang="..." causes screen readers to fall back to the user's default voice — a French page read in English sounds like nonsense. Setting lang on the <html> element is a one-character fix that lets every assistive tool pronounce content correctly.

Source: W3C WCAG 2.1

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

C
Third-Party Trackers
Action
1 trackers detected
REVIEW
1 trackers detected
Info::
1 third-party trackers detected
Found 1 analytics, 0 advertising, 0 marketing, 0 tag manager trackers.
Got: 1 trackers
Warning::
Trackers detected but no cookie policy found
This page loads 1 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.
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

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+
Readability & Typography
Font sizes and tap targets checked
PASS
Font sizes and tap targets checked
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback