Accessibility statement

Version 1.0 · Effective 25 September 2026 · Omvora Media & Automation

1. Our commitment

Omvora Media & Automation wants everyone to be able to use omvoramedia.com, including people who use a screen reader, a keyboard instead of a mouse, magnification, their own colours or text spacing, or who are sensitive to motion.

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA. That also covers WCAG 2.1 Level AA, the level that India’s ICT accessibility standard IS 17802 (Part 1): 2021 is aligned with for web content, and the level used for websites under the Rights of Persons with Disabilities Act, 2016, the Americans with Disabilities Act and the European Accessibility Act.

2. Conformance status

This website is partially conformant with WCAG 2.2 Level AA: most of the standard is met, and the parts that are not yet fully met are listed in section 5 with the way around each. The Accessibility Conformance Report below sets out every success criterion, its status and how it was checked. It is also published in machine-readable form at /accessibility/acr.json.

3. What you can do on this site

  • Use a keyboard for everything. The first Tab stop is “Skip to content”. Every link, button and form field can be reached and used with the keyboard; the menu opens with Enter and closes with Escape.
  • Turn the text animation off. On the About, Contact, Pricing and policy pages, the “Animation” switch in the bottom-right corner shows all text at once, with no word-by-word reveal, and remembers your choice. On every page, if your device is set to reduce motion, the site shows everything without motion and lays the home page’s story out as plain sections. The text animation only moves as you scroll; nothing moves on its own for more than a moment.
  • Use a screen reader or a braille display. Every sentence is read whole, not word by word, by VoiceOver (iPhone, iPad, Mac), TalkBack (Android), NVDA, JAWS and Narrator, and a refreshable braille display connected to any of them shows the same whole sentences. Each page declares its language, and passages in another language declare theirs, so your device picks the right voice and braille table.
  • See the text while a screen reader reads it. Some text appears as you scroll. If you want every word on screen at once, turn on Reduce Motion (iPhone and iPad: Settings › Accessibility › Motion › Reduce Motion; Android: Settings › Accessibility › Remove animations; Windows: Settings › Accessibility › Visual effects › Animation effects off; Mac: System Settings › Accessibility › Display › Reduce motion). The site then shows all text at once.
  • Use your device’s own settings. The site follows Increase Contrast (secondary text takes full contrast and lines strengthen), Reduce Transparency (no frosted-glass panels), Smart Invert and Classic Invert (photographs and video keep their true colours), Windows contrast themes (highlights keep a system highlight colour), and your browser’s text size and zoom. Voice Control and Voice Access can use every link and button by its visible name, and Switch Control and Full Keyboard Access reach everything a keyboard can.
  • Turn the sounds off. The sound button in the header switches off the short interface sounds. No sound plays on its own for more than a moment.
  • Zoom and resize. Pages work at 200 % zoom and on screens 320 px wide without scrolling sideways, and the site never stops you from zooming.
  • Use your own text spacing and colours. Text stays readable with larger line, letter and word spacing (with the one exception in section 5).
  • Read every image. Every picture that carries meaning has a text alternative; decorative ones are hidden from screen readers.

4. How we check

Every release of this site is tested before it goes live, and the results are kept:

  • an automated audit of every page with axe-core against all WCAG 2.2 A and AA rules, at desktop and phone widths;
  • a keyboard-only walk of every page: focus order, a visible focus indicator, nothing hidden behind the fixed header, no keyboard traps, the skip link and the menu;
  • text spacing, 320 px reflow, 200 % zoom, target size, headings, landmarks, language of parts, forms and motion checks on every page;
  • a check that every animated sentence reaches screen readers and braille displays as one whole sentence, and that highlights and switches are announced plainly;
  • the site’s own release suite in the Chromium, WebKit (Safari) and Firefox engines.

We do not use accessibility overlay widgets.

5. Known limitations

  • The home page story with your own text spacing, on short screens. Each of the five story chapters on the home page is held to one screen while you scroll. On a short screen (for example a laptop showing 640 px of page height), with much larger line or letter spacing applied, some of a chapter’s text can be cut off. Every chapter has a button to its own service page, which carries the same content in full and meets this requirement; with reduced motion on, the chapters also appear as ordinary sections.
  • Screen readers on real devices. We review what screen readers are given on every release — every page’s accessibility tree in the engines behind Chrome and Safari, and a check that every animated sentence is read as one sentence. On 25 September 2026 a test with VoiceOver on an iPhone found that the animated headings and paragraphs were read one word at a time; this was fixed the same day. A repeat of that test, and passes with TalkBack and NVDA, are still to be completed; until they are, we treat screen reader and braille support as partially verified.
  • Security checks by our network provider. Very rarely our network provider (Cloudflare) may show a browser check page before the site loads. That page is provided by them, not by us.

6. Tell us about a barrier

If anything on this site is hard for you to use, or you need content in another format, please write to hello@omvoramedia.com with the page address and what happened. We acknowledge within 2 working days and tell you what we will do and by when. There is no charge for an accessible alternative.

If you are not satisfied with our response, in India you may approach the Chief Commissioner for Persons with Disabilities or the State Commissioner for your state, who handle complaints under the Rights of Persons with Disabilities Act, 2016.

7. Technical information

This site is built with HTML, CSS and JavaScript and relies on them for accessibility. It has been tested in the current engines behind Chrome and Edge (Chromium), Safari (WebKit) and Firefox, at desktop and phone sizes.

This statement and the conformance report were prepared by Omvora on 25 September 2026 with AI-assisted testing (the tests described above); they have not yet been reviewed by an independent accessibility professional. They are reviewed with every release of the site that changes its pages.

Accessibility Conformance Report

WCAG 2.2 Level A and AA (covers WCAG 2.1 AA, the level IS 17802 (Part 1): 2021 is aligned with for web content). Report dated 2026-09-29, from the audit of 17 pages. Summary: Supports 42 · Partially supports 1 · Does not support 0 · Not applicable 12 · Not evaluated 0. Reviewed by: Omvora, with AI-assisted testing: the automated audit, a keyboard walk, and a review of the accessibility tree screen readers read, in Chromium and WebKit (25 Sep 2026). Not reviewed by an independent certified accessibility professional. Still to come: A repeat of the owner's VoiceOver (iPhone) test after the OM-60 fix, and passes with TalkBack (Android) and NVDA (Windows); Review by an independent accessibility professional before the RPwD (Amendment) Rules take effect. Machine-readable: acr.json.

CriterionLevelStatusRemarks
1.1.1 Non-text ContentASupportsEvery image has an alt attribute; meaningful images are described, decorative ones are empty or hidden; icon-only buttons are named.
1.2.1 Audio-only and Video-only (Prerecorded)ANot applicableThe site has no audio or video content. The short interface sounds carry no information.
1.2.2 Captions (Prerecorded)ANot applicableNo prerecorded video with audio.
1.2.3 Audio Description or Media Alternative (Prerecorded)ANot applicableNo prerecorded video.
1.2.4 Captions (Live)AANot applicableNo live media.
1.2.5 Audio Description (Prerecorded)AANot applicableNo prerecorded video.
1.3.1 Info and RelationshipsASupportsHeadings, landmarks, lists and form labels are marked up; tables keep their table semantics inside a labelled scroll region.
1.3.2 Meaningful SequenceASupportsThe reading and focus order follow the visual order.
1.3.3 Sensory CharacteristicsASupportsNo instruction relies on shape, colour, size, position or sound alone.
1.3.4 OrientationAASupportsPages work in portrait and landscape; a landscape layout is provided for short screens.
1.3.5 Identify Input PurposeAASupportsPersonal fields in the contact form carry autocomplete values.
1.4.1 Use of ColorASupportsLinks in running text are underlined; highlighted phrases are emphasis, not the only carrier of information.
1.4.2 Audio ControlASupportsOnly brief interface sounds, each under three seconds and started by the reader; a header button turns them off.
1.4.3 Contrast (Minimum)AASupportsText at rest meets 4.5:1 (large text 3:1). Words being revealed by the scroll animation pass through lower contrast for a moment by design; the text is present for assistive technology throughout and shown whole with reduced motion or the Animation switch. Measured at rest on 13 devices in three engines. The demonstration phones on the home page are pictures of WhatsApp and Telegram screens in those apps' own colours, hidden from screen readers; their text is incidental under this criterion (part of an inactive user interface and of a picture) and is reported, not hidden, in the device matrix.
1.4.4 Resize TextAASupportsPages work at 200 % zoom without loss; zoom is never blocked.
1.4.5 Images of TextAASupportsThe only image of text is the Omvora wordmark, a logotype (exempt).
1.4.10 ReflowAASupportsNo horizontal scrolling at 320 CSS px.
1.4.11 Non-text ContrastAASupportsForm field edges and focus indicators meet 3:1. The checkboxes are the browser's own controls (only their tint is set), which 1.4.11 exempts.
1.4.12 Text SpacingAAPartially supportsNo text is lost with WCAG text-spacing overrides, except in the home page story chapters on short screens (measured: 1366 × 640), which are pinned to one screen; each chapter links to its service page, which carries the same content and passes (conforming alternate version), and reduced motion lays the chapters out as plain sections.
1.4.13 Content on Hover or FocusAASupportsNo custom tooltip or hover content; the one title attribute is shown by the browser.
2.1.1 KeyboardASupportsEvery control can be reached and used with the keyboard, including the menu and the scrollable tables.
2.1.2 No Keyboard TrapASupportsFocus never gets stuck.
2.1.4 Character Key ShortcutsANot applicableThe site defines no single-key shortcuts.
2.2.1 Timing AdjustableANot applicableNothing on the site has a time limit.
2.2.2 Pause, Stop, HideASupportsNothing moves by itself for more than five seconds: the text animation follows the reader's scrolling; reduced motion and the Animation switch show everything at rest.
2.3.1 Three Flashes or Below ThresholdASupportsNothing flashes; the slowest glow cycles once every 2.6 seconds.
2.4.1 Bypass BlocksASupports"Skip to content" is the first focus stop on every page and moves focus to the main content.
2.4.2 Page TitledASupportsEvery page has a unique, descriptive title.
2.4.3 Focus OrderASupportsFocus moves in a meaningful order; the menu returns focus to its button when closed.
2.4.4 Link Purpose (In Context)ASupportsEvery link has a name that states its purpose in context.
2.4.5 Multiple WaysAASupportsEvery page is reachable from the menu, the footer links and the sitemap.
2.4.6 Headings and LabelsAASupportsOne h1 per page, no skipped levels; every field has a descriptive label.
2.4.7 Focus VisibleAASupportsEvery focusable element shows a visible focus indicator.
2.4.11 Focus Not Obscured (Minimum)AASupportsA focused element is never hidden behind the fixed header or the chapter dock (scroll padding); the dock leaves the tab order while it is off screen.
2.5.1 Pointer GesturesASupportsNo multipoint or path-based gestures; scrolling is ordinary scrolling.
2.5.2 Pointer CancellationASupportsStandard links and buttons act on release.
2.5.3 Label in NameASupportsThe accessible name of every visible link and button contains its visible words, so Voice Control and Voice Access users can say what they see.
2.5.4 Motion ActuationANot applicableNo function is operated by device motion.
2.5.7 Dragging MovementsAANot applicableNo dragging is required.
2.5.8 Target Size (Minimum)AASupportsTargets are at least 24 × 24 CSS px, or spaced so a 24 px circle on each touches no other; links in sentences are exempt.
3.1.1 Language of PageASupportsEvery page declares lang="en".
3.1.2 Language of PartsAASupportsText in another script carries its own lang.
3.2.1 On FocusASupportsFocusing an element never changes the page or navigates.
3.2.2 On InputASupportsChanging a form field never submits or navigates on its own.
3.2.3 Consistent NavigationAASupportsThe header, menu and footer are the same on every page (one layout).
3.2.4 Consistent IdentificationAASupportsThe same functions carry the same names on every page.
3.2.6 Consistent HelpASupportsContact details and "Talk to us" are in the same place on every page.
3.3.1 Error IdentificationASupportsEvery field with a problem is marked invalid and named in an announced message.
3.3.2 Labels or InstructionsASupportsEvery field is labelled; required fields say so.
3.3.3 Error SuggestionAASupportsThe message says what to change in each field.
3.3.4 Error Prevention (Legal, Financial, Data)AANot applicableThe site takes no legal commitment, payment or data change; the enquiry form only sends a message.
3.3.7 Redundant EntryANot applicableThere is no multi-step process.
3.3.8 Accessible Authentication (Minimum)AANot applicableThere is no sign-in.
4.1.2 Name, Role, ValueASupportsControls expose their name, role and state (the menu, the switches, the sound button — its state in aria-pressed only). Every animated sentence reaches screen readers and braille displays as one sentence (an iPhone VoiceOver test on 25 Sep 2026 found word-by-word reading; fixed and now checked on every page). The accessibility tree was reviewed in Chromium and WebKit: text reads as whole sentences, highlights are not announced as marked text, the decorative scroll hint is hidden, the phone demonstrations are hidden (their content is in the copy). A real-device pass is pending.
4.1.3 Status MessagesAASupportsForm errors are announced (role="alert"), and the form's progress note is a polite live region.