Compliance Foundations

The running list behind what Olite is checking.

Olite is not trying to flatten compliance into one vague score. The scanner is built around observable foundations across accessibility, privacy, consent, and basic security.

This page is the public summary. The fuller internal working document stays in the repository docs.

Accessibility

Foundations Olite can verify well

• Page title and html language signals
• Main landmark and heading structure warnings
• Alt text coverage, labels, and accessible names
• Placeholder-only fields, iframe titles, and positive tabindex warnings
• Rendered checks such as hidden focusables, skip-link failures, and early keyboard progression

Privacy

Foundations Olite is using for public-page review

• Privacy-policy visibility and destination verification
• Cookie wording and reject or manage controls for EU-inclusive reviews
• Rights-request paths, opt-out cues, and GPC visibility for US-only reviews
• Tracking detections, email capture transparency, and baseline security headers
• A path toward deeper runtime consent and browser-signal verification in desktop workflows

Method

How the product is separating strong checks from softer guidance

• Static DOM checks for markup and semantics
• Rendered checks for post-hydration state and interaction behavior
• Network and browser checks later for stronger privacy verification
• Clear limitation messaging when a rule is advisory or partial