What Olite Checks
The public list of issues Olite is isolating today.
Olite is a lightweight verification scanner for public websites. It is designed to isolate concrete accessibility, privacy, consent, and basic security issues that teams can review and act on quickly.
This page is the public issue catalog. It is meant to show what the product actually surfaces today, and it also gives us a clear starting point for future explainers and blog articles.
The fuller internal framing lives in the repository docs: issue catalogand compliance foundations.
Method
How Olite isolates issues
- Static DOM review for markup, labels, titles, and semantics
- Visible public-page review for privacy, policy, and consent cues
- Rendered browser checks in desktop reviews for keyboard and skip-link behavior
- Lightweight evidence such as selectors, snippets, and page-level location summaries
This is an automation-oriented review workflow, not legal advice, not certification, and not a guarantee that every issue on a site has been found.
Accessibility
Current static accessibility issues
These are the current accessibility issues Olite can isolate directly from markup and document structure.
- Missing page title
- Missing html lang attribute
- Missing main landmark
- Multiple h1 headings detected
- Images missing alt text
- Placeholder-only form fields
- Inputs missing visible or programmatic labels
- Weak heading structure signals
- Buttons without accessible names
- Links without accessible names
- Potential focus order override from positive tabindex
- Iframes missing title attributes
Rendered Accessibility
Current desktop-only rendered checks
These checks currently come from the local desktop workflow, where Olite can inspect the page after render and sample early keyboard movement.
- Focusable elements hidden from view after render
- Rendered skip link target missing
- Skip link did not change focus or route after activation
- Keyboard tab progression could not be established after render
- Keyboard focus appears stalled during early tab progression
Privacy
Current public-page privacy issues
These issues focus on visible policy, rights, opt-out, cookie, and tracking signals that can be observed from a public page.
- Privacy policy link could not be verified
- Tracking signals without visible cookie wording
- Cookie banner without obvious reject or manage controls
- No obvious privacy rights request path detected
- No obvious sale or sharing opt-out path detected
- Limited visible US privacy rights cues
- No visible Global Privacy Control cue detected
- No obvious privacy or cookie policy links detected
- Email capture without visible privacy cues
Consent
Current consent issue
Consent coverage is intentionally narrow in the current product and focuses on visible email capture cues.
- Email capture without visible consent signals
Security
Current baseline security issues
These are lightweight public-web checks, not a full security audit. They are included because they often reveal obvious weaknesses quickly.
- Limited security header coverage
- Page is not served over HTTPS
- Forms submit to insecure HTTP targets
Article Backlog
Natural explainers we can build from this list
- Why a privacy policy link can fail verification even when a footer link exists
- Why placeholder-only fields still create accessibility problems
- Why skip links break after render on modern websites
- What visible US privacy rights cues look like
- Why GPC and browser-based opt-out language matter
- What baseline security-header coverage does and does not tell you