Accessibility Statement

1. Our commitment

OpBot is used by coaches, the teams that sell for them, and the people who apply to work with them. We want all of them, including people who use a screen reader, a keyboard alone, magnification, or who ask their device for less motion, to be able to complete what they came to do. The standard we build against is the Web Content Accessibility Guidelines (WCAG) 2.1, level AA, the level referenced by the Americans with Disabilities Act guidance, the European Accessibility Act and the UK Equality Act.

2. What this statement covers

Three surfaces, all built and served by OpBot:

• This website (opbot.io): the marketing pages and the legal pages.
• The OpBot app: the dashboard, the funnel editor, the inbox, settings and billing that a coach and their team sign in to.
• Funnel pages: the landing pages, application forms, booking calendars, checkouts and thank-you pages OpBot generates for a coach and serves under the coach’s name.

It does not cover what a coach adds to their pages (their copy, images, video and uploaded HTML), a coach’s own website where they embed an OpBot form, or the third-party services a page hands off to (a Stripe payment form, a YouTube or Vimeo player, a Zoom or Google Meet call). Section 5 says what those depend on.

3. Conformance status

OpBot is partially conformant with WCAG 2.1 level AA: most of the product meets the guidelines, and the parts that do not are listed in section 6. This is our own assessment. No independent third-party audit has been carried out yet. We will update this page when one has.

4. What is built in

• Structure. Pages use headings, landmarks and lists so a screen reader can move by section. Navigation regions are named, and every page under our control declares its language.
• Keyboard. Every control can be reached and operated with a keyboard. A visible focus indicator is drawn on every interactive element, in both the light and the dark theme, and it appears the moment focus lands rather than fading in. Dialogs keep focus inside them and close on Escape. A Skip to content link is the first thing the Tab key reaches on the app, on this site and on every funnel page, so nobody has to tab through a sidebar or a navigation bar on every screen.
• Forms. Every field has a visible label or an accessible name. Choices are exposed as radio and checkbox groups rather than as bare buttons. When a submission fails, the message is announced to assistive technology, and an inline field error is attached to the field it concerns.
• Colour and contrast. Text and controls are checked against the AA ratios (4.5:1 for text, 3:1 for graphics and focus rings) in both themes with an automated audit that runs on every screen we change, and a check in our build pipeline refuses the muted text shades that fail on a light surface. When a coach’s brand colour is used as text on their funnel pages, OpBot adjusts it to a readable shade automatically.
• Motion. When a visitor’s device asks for reduced motion, animations and transitions collapse to their end state, smooth scrolling becomes instant, and the assistant’s animated character shows a still image instead. This applies to the app, this site and every funnel page, including pages built before it shipped.
• Target size. The same audit flags any control smaller than the 24×24 pixel minimum.
• Status messages. Confirmations and notices in the app are announced politely without stealing focus.
• Themes. The app offers a light and a dark theme and remembers the choice.
• Media. A video on a funnel page starts from a real button named “Play video” and then plays in the visitor’s player with that player’s own controls. Purely decorative icons are hidden from assistive technology; a coach’s logo and photo carry the business or coach name as their alternative text.

5. What depends on the coach

A funnel page is the coach’s page. OpBot gives it an accessible frame; the content inside that frame is theirs, and its accessibility depends on:

• Alternative text for the images they add. The page editor adds it on request.
• Captions or a transcript for their video, which live with the video on the platform that hosts it.
• Colour choices inside HTML they upload themselves, which OpBot serves as written.
• Uploaded documents and course material (PDFs, slides, recordings), which are delivered as the coach supplied them.
• Plain, well-structured copy: the AI writes with headings and short sections, and the coach can edit anything.

Our Terms of Service (section 10, “Accessibility”) set out the coach’s responsibility for their published pages under the laws that apply to their business.

6. Known limitations

• No independent audit yet. Everything above is our own assessment.
• Charts. The graphs on the dashboard are not described to a screen reader beyond the numbers shown as text beside them.
• Pointing in the editor. A few editor tools pick out a part of a page by pointing at it, for example choosing an image to replace. The same change can be asked for as text in the chat editor.
• Language of funnel pages. Every funnel page is declared to be in English, including one a coach writes in another language.
• Uploaded HTML. A page a coach uploads receives the skip link and the reduced-motion behaviour, and is otherwise served as uploaded.
• Third-party components. The Stripe payment form, embedded video players and the calendar and meeting tools a page hands off to follow their providers’ accessibility, not ours.

7. Feedback and contact

If something on OpBot, or on a page OpBot serves, stops you from completing a task, tell us: email support@opbot.io with the page address, what you were trying to do and the assistive technology you use, or use the Feedback button in the app. We reply to every accessibility report, and a barrier that blocks someone from completing a task is treated as a priority. If the barrier is on a coach’s page, we will also pass it to the coach.

8. How we assess it

OpBot is built with HTML, CSS, JavaScript and WAI-ARIA, and relies on them for the behaviour described above. Our assessment is a self-evaluation: automated checks for contrast, focus visibility, form labels, heading structure and target size on each screen we change, and a manual keyboard review of new screens. This statement is reviewed when the product changes materially, and at least once a year.