Om Concepts wants everyone to be able to read this site, use its forms, and reach us without friction. We build toward WCAG 2.2 Level AA. We are a single-operator practice and we have not paid for a third-party audit, so this page describes what is actually in place, what is not, and how to tell us when something fails for you.
What is implemented
- A skip link at the top of every page jumps keyboard and screen reader users straight to the main content.
- Semantic headings and landmarks structure every page, so assistive technology can navigate by section.
- Primary buttons, footer links, and other key controls meet a 44px minimum tap target.
- Contact and guide form inputs render at 16px on small screens, which keeps mobile browsers from zooming when a field gets focus.
- Animations across the site respect the reduced-motion setting in your operating system. Scroll effects, marquees, and button motion are simplified or removed when it is on.
- Cookie and analytics consent uses plain buttons with a real decline path. No tracking runs until you choose.
- Visible focus styles are applied consistently to links, buttons, and form fields.
Known limitations
- Some pages use decorative WebGL surfaces, like the animated dot field on the homepage. These are hidden from assistive technology and freeze to a static frame under reduced motion, but they remain purely visual.
- Some interactive demonstrations, like the agent visualizations on service pages, are visual by nature. Each one carries a text alternative or a caption, and no information is available only through the animation.
- The voice agent on /voice is an optional path. The contact form and calendar booking work fully without it.
Report an issue
If any part of this site is hard to use with a keyboard, a screen reader, magnification, or any other assistive setup, email alex@omconcepts.net. Tell us the page, what you were trying to do, and the technology you were using. Screenshots or recordings help but are not required.
What happens next
A human reads every report. We reply within two business days, and we prioritize fixes by how badly the issue blocks real use. When a fix ships, we update this page and the “Last updated” date at the top.