Accessibility statement
Origin Pixel Solutions, Chennai, Tamil Nadu, India · Last reviewed 31 October 2026
We want everyone to be able to use the Origin Platform: the client app, the Owner Console, the public pages, and the chat widget, booking page, help centre and privacy portal that our clients put in front of their own customers.
Conformance status
Partially conformant with the Web Content Accessibility Guidelines (WCAG) 2.2 (opens in a new tab) level AA. Automated WCAG 2.2 AA checks and keyboard-only journeys pass on every page we test. We call it partial until a full manual screen-reader review is done and the known limits below are closed.
The full report, criterion by criterion, with the matching EN 301 549 clauses, is our Accessibility Conformance Report (VPAT 2.5 format). Ask for a copy at hariprathish@originpixel.in.
Standards and laws we follow
- WCAG 2.2 level AA: the target for every page and the embeddable widget.
- EN 301 549 v3.2.1: the European standard behind the European Accessibility Act (Directive (EU) 2019/882), clauses 9 (web), 10 (documents) and 11.7 / 12 (user preferences and documentation).
- Americans with Disabilities Act (ADA) and Section 508: we use WCAG 2.2 AA as the measure; our ACR uses the VPAT 2.5 format.
- India: Rights of Persons with Disabilities Act 2016 and GIGW 3.0: WCAG 2.1 AA is the basis of IS 17802 and GIGW; we meet it as part of WCAG 2.2 AA. A GIGW checklist is prepared for government clients on request.
- UK Equality Act 2010: reasonable adjustments, including other formats on request.
What you can expect
- Every task works with a keyboard alone. A “Skip to content” link is the first thing on every page.
- Dialogs, the phone menu, the product tour and Copilot keep focus inside while open, close with Esc and return you to where you were.
- Streaming answers, notifications and live call transcripts are announced to screen readers without reading every word twice.
- Day and Night themes both meet contrast AA; the app follows your device setting for dark mode and reduced motion.
- Charts come with a data table. Call recordings come with a timestamped transcript you can search and download.
- Text in other languages is marked with its language, and Arabic and Urdu read right to left. The app itself is available in several languages.
- Pages work at 390 px wide and at 400% zoom without sideways scrolling; buttons and links are at least 24 by 24 px.
- Voice agents always offer a keypad option and a transfer to a person.
Known limits
We know about these gaps and are working on them:
- Manual screen-reader review: a full pass with NVDA and VoiceOver of chat, booking, the privacy portal and checkout is planned; automated tests cannot find every problem.
- Payment pages: card and UPI entry happens on Razorpay's or Stripe's hosted checkout, which we do not control.
- Sign-in with other services: Google, Microsoft, Meta and other connection screens are run by those companies.
- Content our clients add: images, documents, brand colours and knowledge articles come from each business. We pick readable text colours on brand colours automatically and warn in the widget settings when a colour is too light, but cannot check everything a business uploads.
- Voice calls: calls are audio. Callers can use the keypad and ask for a person at any time, and businesses get a full transcript. Callers using a TTY or relay service should ask for a person (the agent does not yet detect TTY tones).
- PDF and CSV exports: invoices print from an accessible web page; downloaded exports are plain data files without document structure.
How we test
- Automated checks with axe-core (WCAG 2.0, 2.1 and 2.2 A and AA rules) on every page, in Day and Night themes and at phone width, on every release.
- Scripted keyboard-only journeys: sign in, Copilot, command palette, phone menu, booking, chat widget, privacy request and checkout.
- Checks for page language, skip links, visible focus and reduced motion, and a contrast test of every colour pair in both themes.
- Manual checks with NVDA on Windows and VoiceOver on macOS and iOS before major releases (the first full pass is still to do, see Known limits).
Report a barrier or ask for another format
If something does not work for you, or you need information in another format (large print, plain text, audio, a call back), tell us. We reply within 5 working days and aim to fix or offer an alternative within 30 days.
- Email: hariprathish@originpixel.in (subject “Accessibility”)
- Post: Origin Pixel Solutions, Chennai, Tamil Nadu, India
- Signed in? Use Support in the app menu and choose “Question”.
If you are a customer of a business that uses the Origin Platform (its chat, booking page or help centre), you can contact that business or us; we will work with them to fix it.
If you are not happy with our reply
- European Union: contact the market surveillance authority for the European Accessibility Act in your country.
- India: the Grievance Redressal Officer named in our privacy notice, then the Chief Commissioner (or State Commissioner) for Persons with Disabilities under the RPwD Act 2016.
- United Kingdom: the Equality Advisory and Support Service (EASS).
- United States: the U.S. Department of Justice ADA information line.