Skip to content
https://stomatology.in.ua/login

Compliance

· 23 checks — WCAG, consent & privacy, language, viewport, cookie inventory, and legal pages rolled into one auditable list.
SCORE
81
GRADE
B
FIX
1
REVIEW
4
PASS
15
INFO
3
Checks
23
15 PASS 4 REVIEW 1 FIX
D
GDPR Article 13 Disclosures
Action
0 / 8 Art. 13 categories matched in homepage body
FIX
0 / 8 Art. 13 categories matched in homepage body
Info::
GDPR Article 13 disclosures not assessed (policy language: uk-UA)
The privacy policy appears to be written in "uk-UA", which this check has no disclosure patterns for (currently English, French, German and Spanish). No conclusion is drawn about the policy's completeness, and this finding is excluded from the regulatory-risk estimate.
Got: 0/8, unassessed
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. Detection is by link URL and anchor text, in a limited set of languages, so this is an unconfirmed absence.
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.
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

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
2 known tracker(s) detected
PASS
2 known tracker(s) detected
Info::
2 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 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
1 hreflang issue(s) across 3 tag(s)
PASS
1 hreflang issue(s) across 3 tag(s)
Warning::
Hreflang cluster missing self-reference
This page (https://stomatology.in.ua/login) appears in no hreflang entry on itself. Per Google's spec, each page in a hreflang cluster must include its own URL with the appropriate hreflang code -- otherwise the cluster is incomplete and search engines may not index alternates correctly.
A+
Internationalization Extras
1 i18n signal(s) detected
PASS
1 i18n signal(s) detected
Info::
Language switcher detected (anchor tags carry `hreflang` attribute)
The page has anchor tags with `hreflang` attributes -- the standard semantic for language-switcher links. Search engines and screen readers use the hreflang attribute to know what language the linked page is in, even when the link text is in the source language (e.g. `<a hreflang="fr" href="/fr">Français</a>` on an English page).
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.0
width=device-width

Responsive layout enabled

initial-scale=1

Correct initial zoom level

User zooming allowed

Accessibility-friendly — users can zoom

A+
Third-Party Trackers
3 trackers detected
PASS
3 trackers detected
Info::
3 third-party trackers detected
Found 2 analytics, 0 advertising, 0 marketing, 1 tag manager, 0 session-replay, 0 heatmap trackers.
Got: 3 trackers
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
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)
Regulatory Indicators
1 regulatory indicator(s) detected
INFO
1 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

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
Third-Party Data Sharing
2 third-party service(s) detected
INFO
2 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::
2 third-party services across 2 categories
2 third-party services detected across 2 categories: Analytics (1), Tag Management (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
Analytics (1)
Tag Management (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 ✓

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
583 words, Flesch-Kincaid grade 21.7
INFO

Readability Analysis (Flesch-Kincaid)

Grade Level

21.7

Grade 22 (college+)

Reading Ease

55

Fairly Difficult

Words

583

Sentences

9

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

Send Feedback