---
title: "Accessibility | Omphalis"
description: "How Omphalis approaches accessibility: the standard we aim for (WCAG 2.2 Level AA), what we do to meet it, what we know is not covered, and how to report a problem."
canonical: "https://omphalis.ai/accessibility"
source: "https://omphalis.ai/accessibility"
---

# Accessibility

**Last updated:** August 2026

This statement covers omphalis.ai (this marketing site) and the Omphalis app.

## Our commitment

Omphalis aims for WCAG 2.2 Level AA conformance across the marketing site and the app. Accessibility is part of how the product is built, not a pass applied at the end.

## What we do

Pages are built on semantic HTML, so headings, landmarks, and lists carry their meaning to assistive technology rather than depending on how things look. Every interactive control is reachable and usable by keyboard, and focus states are visible rather than suppressed. Color comes from semantic design tokens with a dark mode, so contrast is a property of the system rather than of individual pages.

Automated accessibility checks run in CI on every change. This site scores 100/100 on automated Lighthouse accessibility checks.

## Known limitations

Automated checks do not cover everything. They cannot judge whether alt text is accurate, whether a reading order makes sense, or whether an interaction is understandable, only whether certain rules hold. Some third-party embeds, such as video players, are outside our control and may not fully conform.

Where the site or the app falls short, we treat it as a defect, not as feedback to consider.

## Feedback

If you run into an accessibility problem, or something here is inaccurate, write to us at [hello@omphalis.ai](mailto:hello@omphalis.ai) and include “Accessibility” in the subject. Tell us the page, what you were trying to do, and what happened. Accessibility reports go into the same bug queue as everything else.

Written by [Stanly Thomas](https://omphalis.ai/about#founder) · Last updated 17 August 2026