Oppermind Back

Accessibility Statement

Last updated: 25 May 2026  |  Effective: 25 May 2026  |  Statement reviewed: 25 May 2026

Oppermind Pty Ltd (ABN 89 689 605 918) ("Oppermind", "we", "us", or "our") is committed to making the Oppermind platform (the "Service") usable by the widest possible audience. This Accessibility Statement explains our conformance target, our current progress, known limitations, the channels we provide for feedback, and the cadence at which we review and update both the Service and this statement.

An honest position. The Service is under active development. We are working towards conformance with the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA, but we do not yet claim full conformance, and we describe the gaps in Section 5 below. We will update this statement as our position changes.

Contents

  1. Our commitment
  2. Conformance target and standard
  3. Scope of this statement
  4. Measures we take
  5. Known limitations
  6. Third-party content and dependencies
  7. Compatibility with assistive technology
  8. Feedback and contact
  9. Formal complaints and enforcement
  10. Remediation commitment and cadence
  11. Approval and review
  12. Related documents

1. Our commitment

We believe that AI productivity tools should be available to everyone, including people with disabilities, older users, and people who use the web in non-default ways (for example, with high contrast, larger text, voice control, switch devices, keyboard only, or assistive software). We are committed to identifying and removing barriers in the Service on an ongoing basis.

We will not knowingly publish or maintain features that make the Service less accessible than the version they replace, and we will not use this statement as a substitute for substantive improvement.

2. Conformance target and standard

Our aspirational conformance target is the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA, published by the World Wide Web Consortium (W3C) and recognised internationally as a reasonable benchmark for digital accessibility. Where compliance with WCAG 2.2 is straightforward, we adopt it as a matter of good practice without claiming formal conformance.

This target reflects the standards referenced (in whole or in substantial part) by, among others:

  • The Disability Discrimination Act 1992 (Cth) and the Australian Human Rights Commission's World Wide Web Access: Disability Discrimination Act Advisory Notes;
  • The European Accessibility Act (Directive (EU) 2019/882), implementing legislation in EU/EEA Member States, and the harmonised standard EN 301 549;
  • The United Kingdom Equality Act 2010 and the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018, as applied to private-sector best practice;
  • Title III of the United States Americans with Disabilities Act (ADA) and Section 508 of the Rehabilitation Act (29 U.S.C. § 794d), as well as state laws including California's Unruh Civil Rights Act;
  • The Accessibility for Ontarians with Disabilities Act (AODA) and the Accessible Canada Act.

This statement is provided for transparency and does not constitute a representation of legal compliance in any jurisdiction. References to laws above are illustrative of the standards we use to inform our practice; whether a particular law applies to you is a matter for that law.

3. Scope of this statement

This statement applies to the Oppermind web platform at oppermind.com and to associated subdomains operated by Oppermind, including the marketing, sign-in, dashboard, workspace, and legal-document surfaces. It does not apply to:

  • Content authored by users and stored within or shared through the Service;
  • Third-party services we integrate with (for example, payment processing or external email providers) other than as described in Section 6;
  • Documents, files, images, audio, video, or other media generated by Lato 1 (Oppermind's AI model, also referred to as oppermind-lato-1) in response to user prompts, the accessibility of which depends substantially on the user's input.

4. Measures we take

To support accessibility, we take measures that include the following:

  • Using semantic HTML and ARIA roles where appropriate so that assistive technology can interpret the interface;
  • Designing for sufficient text contrast and offering a dark-mode theme that maintains contrast targets;
  • Supporting keyboard navigation across primary user flows;
  • Designing primary tap targets to be at least the size recommended by WCAG 2.5.5;
  • Avoiding content that flashes more than three times per second;
  • Reviewing new features for accessibility regressions before release where practicable;
  • Inviting feedback through the channels described in Section 8.

5. Known limitations

We are aware of the following areas of the Service that may not yet meet WCAG 2.1 Level AA. We are publishing this list in good faith and in the spirit of transparency; the list is not exhaustive, and we will update it as we identify additional issues or as remediations land. If you encounter a barrier not listed here, please contact us using the channels in Section 8.

Area Known limitation Workaround (interim)
AI chat and conversation panels Streaming responses are appended dynamically. Some screen readers may not announce streamed token updates predictably, and the typewriter cadence on demonstration pages may not respect reduced-motion preferences in all browsers. Wait for the full response to render before re-reading the message. Use your screen reader's "read all" or "read from cursor" command to re-read in full.
Document and code editor surfaces Rich-text and code editor components rely on contenteditable regions whose announcement, caret behaviour, and selection model may not match the conventions of all screen reader and braille display combinations. For long-form writing, drafting in a screen-reader-friendly editor and pasting into Oppermind remains supported.
Image, video, and audio generation AI-generated media does not yet ship with automatically generated alternative text or transcripts in all cases. Users are responsible for adding their own alternative text and captions where they share or publish generated media. Use the description or caption field where provided, or add alternative text manually before sharing.
Drag-and-drop interactions Some tile layout and workspace reordering interactions rely on drag-and-drop and may not yet expose a fully equivalent keyboard alternative. Use the layout reset or per-tile preference controls to achieve the desired layout without drag-and-drop, where exposed.
Embedded third-party widgets Payment, video, map, and similar embedded widgets are controlled by their providers and may inherit accessibility issues from those providers. Where a third-party widget is inaccessible to you, please contact us; we will assist you to complete the task through an accessible alternative.
PDF and document exports Generated PDF and document exports may not always be tagged for accessibility (semantic structure, reading order, alternative text). Export to HTML or plain text as an interim measure where appropriate.

We do not currently claim WCAG 2.1 Level AA conformance for the Service as a whole. We are reluctant to make claims that we cannot evidence through audit, and we believe an accurate statement of known limitations is more useful to disabled users than an aspirational claim of compliance.

6. Third-party content and dependencies

The Service uses third-party services for functions such as payments (Stripe, Inc.), abuse prevention, and infrastructure. We take reasonable steps when selecting and configuring these services, but their accessibility ultimately depends on the provider. Where a third-party component creates a barrier you cannot overcome, please contact us and we will assist you to complete the task through an accessible alternative wherever practicable.

7. Compatibility with assistive technology

The Service is designed to be compatible with current versions of major browsers, paired with current versions of the main commercial and built-in assistive technologies (including but not limited to VoiceOver on macOS and iOS, TalkBack on Android, Narrator on Windows, NVDA, JAWS, ZoomText, Dragon, Switch Control, and built-in OS magnification, contrast, and font-scaling settings). We do not formally test against every combination, and our reference combinations are subject to change as those products evolve.

8. Feedback and contact

We welcome your feedback on the accessibility of the Service. If you encounter accessibility barriers, please tell us:

  • Email: enquiry@oppermind.com
  • Location: Perth, Western Australia, Australia

To help us investigate, please include (where you can):

  • The page or feature where you encountered the barrier (a link is ideal);
  • A description of the barrier and what you were trying to do;
  • The assistive technology, browser, and operating system you were using.

We aim to acknowledge accessibility feedback within five (5) business days of receipt and to provide a substantive response (including, where applicable, a workaround or a target remediation window) within twenty-one (21) days. These timelines are targets only; they are not a contractual commitment or an admission of any obligation in any jurisdiction.

9. Formal complaints and enforcement

If you are not satisfied with our response, depending on where you are located, you may have additional routes available, including:

  • Australia: the Australian Human Rights Commission — humanrights.gov.au;
  • European Union / EEA: the enforcement body designated under the European Accessibility Act in your country of residence;
  • United Kingdom: the Equality Advisory and Support Service — equalityadvisoryservice.com;
  • United States: the U.S. Department of Justice ADA Information Line — ada.gov;
  • Canada: the Accessibility Commissioner under the Accessible Canada Act, or the relevant provincial body in Ontario (under the AODA) or your province.

Nothing in this Accessibility Statement limits or waives any right you may have under applicable law to file a complaint with a regulator or to commence proceedings.

10. Remediation commitment and cadence

We will:

  • Triage accessibility feedback within five (5) business days of receipt;
  • Track confirmed accessibility issues in our internal backlog and prioritise them based on severity, frequency, and the availability of workarounds;
  • Review this Accessibility Statement at least every twelve (12) months, and sooner if there is a material change in the Service, in applicable standards, or in our known-limitations list;
  • Update the "Last updated" and "Statement reviewed" dates at the top of this document on each review;
  • Where we discover a serious accessibility regression in a release, take reasonable steps to either roll back the regression or publish an interim workaround.

11. Approval and review

This statement was approved on 25 May 2026 by Oppermind. It was last reviewed on the same date. We will review it at the cadence described in Section 10. Earlier versions of this statement are not maintained publicly; however, the contact in Section 8 can request a copy of a prior version for the period required by applicable record-keeping laws.

12. Related documents

  • Privacy Policy
  • Terms & Conditions
  • Data Processing Addendum
  • Cookie Policy
  • Acceptable Use Policy
  • Children's Privacy Policy
  • Refund Policy

© 2026 Oppermind Pty Ltd. All rights reserved.
Terms Privacy AUP DPA Cookies Refunds Accessibility Children's Privacy Withdraw consent