Accessibility Statement

MisarSEO's conformance target under WCAG 2.2 AA, the accessibility work in the current product, known limitations, and how to report an accessibility issue.

Last reviewed: July 21, 2026

Misar AI Technology Private Limited ("Company", "MisarSEO") is committed to making its public marketing site (https://misarseo.com/) and its hosted Service (https://seo.misar.io/) usable for the widest possible audience, including people who rely on assistive technologies.

Conformance target

MisarSEO targets Web Content Accessibility Guidelines (WCAG) 2.2 at conformance level AA across both the marketing site and the hosted Service. That is our development standard: new UI is designed and reviewed against WCAG 2.2 AA success criteria, and regressions found in review or in production are treated as bugs.

We aim to also meet Level AAA where it does not degrade the experience for other users, but AAA conformance is not claimed for the Service as a whole.

What we do

  • Structure and hierarchy: pages use a single H1 followed by a logical H2 → H3 outline (WCAG 2.2 SC 1.3.1 Info and Relationships).
  • Colour and contrast: text/background pairs in both light and dark themes are checked against WCAG 2.2 AA contrast thresholds.
  • Keyboard access: interactive controls are reachable and operable by keyboard alone, with a visible focus indicator.
  • Reduced motion: transitions, animations, and smooth scrolling respect the OS-level prefers-reduced-motion preference (WCAG 2.2 SC 2.3.3).
  • Assistive-technology semantics: interactive components ship with the ARIA roles, states, and labels they need to be understandable via screen readers.
  • Forms: inputs are associated with visible or programmatically-linked labels; error messages are announced next to the input they relate to.

Known limitations

We track accessibility gaps openly rather than claiming full conformance before it is real. Known limitations at the time of the last review include:

  • Some third-party embeds and marketing/demo widgets have not yet been audited to the same standard as first-party UI.
  • Charts and data-heavy tables in the hosted Service currently rely primarily on visual encoding; a fuller text-alternative / screen-reader summary layer is in progress.
  • Colour is used as one signal in a small number of status badges; a text or icon signal is always present alongside it, but the specific colour palette in dark mode is still being fine-tuned for people with low vision.
  • The consent banner and cookie preferences use the shared @misar/ui CookieConsent component, which is being audited across the Misar suite; issues identified there are fixed upstream and rolled into MisarSEO.

If you find an accessibility barrier that is not listed above, please report it — see "Report an issue" below.

Compatibility

MisarSEO is developed and tested to work with recent versions of the major desktop and mobile browsers (Chrome, Edge, Firefox, Safari) and their built-in assistive-technology stacks (VoiceOver on macOS/iOS, TalkBack on Android, Narrator on Windows, and — for third-party — NVDA and JAWS on Windows).

Some very old or heavily-restricted browsers may render parts of the Service without all interactive features. Where that happens, we aim to degrade gracefully so that content remains readable.

Report an issue

If you encounter an accessibility barrier on the marketing site or in the hosted Service, or if any part of the product is not usable for you with the assistive technology you use, please contact us and we will treat it as a priority:

Please include:

  1. the URL of the page or the name of the screen in the Service;
  2. a short description of what did not work; and
  3. the browser, operating system, and assistive technology (if any) you were using.

We aim to acknowledge accessibility reports within 5 business days and to describe a remediation timeline once we have investigated.

Formal complaints

If you have raised an accessibility issue with us and are not satisfied with our response, you may escalate the issue to the supervisory authority responsible for accessibility in your jurisdiction.

Review cadence

This statement is reviewed at least once every 12 months, and updated whenever there is a material change to the Service's accessibility posture (for example, a significant redesign, or a new known limitation). The date at the top of this page reflects the most recent review.