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

Compliance

· 23 checks — WCAG, consent & privacy, language, viewport, cookie inventory, and legal pages rolled into one auditable list.
SCORE
67
GRADE
D
FIX
1
REVIEW
6
PASS
13
INFO
3
Checks
23
13 PASS 6 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 for GDPR Article 13 disclosures. Matched 1 of 8 categories: Legal basis for processing. 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, 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: 1/8
B
Third-Party Trackers
7 trackers detected
REVIEW
7 trackers detected
Info::
7 third-party trackers detected
Found 4 analytics, 2 advertising, 0 marketing, 1 tag manager, 0 session-replay, 0 heatmap trackers.
Got: 7 trackers
Warning::
2 advertising/retargeting trackers detected
Advertising trackers collect user data for ad targeting. Under GDPR, these typically require explicit consent.
B
Cross-Site Cookies (SameSite=None)
2 cross-site cookie(s) (2 tracking-shaped, 0 essential)
REVIEW
2 cross-site cookie(s) (2 tracking-shaped, 0 essential)
Info::
2 tracking-shaped cross-site cookie(s): nyt-a, nyt-traceid
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
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.
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

Links with unclear purpose

19 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
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 9 hreflang tag(s) look correct
PASS
All 9 hreflang tag(s) look correct
Info::
All 9 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+
Viewport Configuration
Viewport properly configured
PASS
Viewport properly configured
Info::
Viewport meta tag is present
Info::
width=device-width is set
Info::
User zooming is allowed
Viewport Configuration Good
Content
width=device-width, initial-scale=1
width=device-width

Responsive layout enabled

initial-scale=1

Correct initial zoom level

User zooming allowed

Accessibility-friendly — users can zoom

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: https://help.nytimes.com/hc/en-us/articles/115015727108-Accessibility
A+
Tracking Pixel Inventory
No image data to inspect for tracking pixels
PASS
No image data to inspect for tracking pixels
Info::
No image data to inspect for tracking pixels
A+
Browser Fingerprinting
No browser-fingerprinting libraries detected
PASS
No browser-fingerprinting libraries detected
Info::
No browser-fingerprinting libraries detected
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 (strong confidence)
Indicators suggesting GDPR may be relevant: European TLD detected: .de; Privacy policy page found. EU General Data Protection Regulation — governs collection and processing of personal data of EU residents.
Got: 2 indicators: European TLD detected: .de, Privacy policy page found
Info::
ADA indicators detected (moderate confidence)
Indicators suggesting ADA may be relevant: Accessibility link found: Accessibility. Americans with Disabilities Act / Section 508 — requires digital accessibility for people with disabilities.
Got: 1 indicators: Accessibility link found: Accessibility

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 Strong

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

Indicators detected

  • European TLD detected: .de
  • Privacy policy page found
ADA Moderate

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

Indicators detected

  • Accessibility link found: Accessibility
Third-Party Data Sharing
1 third-party service(s) detected
INFO
1 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::
1 third-party services across 1 categories
1 third-party services detected across 1 categories: Tag Management (1). Each of these services receives some user data from your site visitors.
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
Tag Management (1)
Google Tag Manager Tag Management
Detected by: script URL
Data typically collected:
Orchestrates other tracking scriptsPage views
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
6036 words, Flesch-Kincaid grade 15.4
INFO

Readability Analysis (Flesch-Kincaid)

Grade Level

15.4

Grade 15 (college+)

Reading Ease

28

Very Difficult

Words

6036

Sentences

249

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

Send Feedback