Designed to be used by everyone.
We target WCAG 2.2 AA across the platform. This page tells you where we are now, where the gaps are, when we’ll close them, and how to tell us when we miss something. Updated quarterly.
What we’re aiming at.
We’re committed to making MingleIn usable by people with the widest possible range of abilities, including people who use assistive technologies (screen readers, voice control, switch control, magnifiers), people with low vision or colour-vision differences, people with motor impairments, people who are deaf or hard of hearing, and people with cognitive or learning differences.
Our standard is WCAG 2.2 Level AA, the most current Web Content Accessibility Guidelines standard at the time of writing. We test against it on every release. We also follow Australia’s Disability Discrimination Act 1992 and the Australian Government’s Digital Service Standard accessibility guidance.
Accessibility is owned by Kira on our team. She doesn’t only do accessibility, but the buck stops with her on it.
The plain-language state of play.
Below is what’s in good shape, what’s partial, and what’s a known gap. We’d rather be honest about gaps than pretend we’re fully compliant when we’re not.
Doing well
Partial, in progress
Known gaps
Accessibility roadmap, publicly dated.
Every line below is in our internal sprint plan. If we miss a date we’ll update this page within five business days and explain why.
Hit a barrier? Report it.
If something on MingleIn is hard or impossible to use because of an accessibility issue, please tell us. Every report goes to a real person on our ops team and we acknowledge inside two business days.
Include: the page or feature, what you were trying to do, what assistive technology you use (if any), and what happened. Screenshots or a screen recording help.
access@minglein.com.auAcknowledged < 2 business daysIf you’d prefer to talk it through, we can call you back. Mention “call please” in the email and the best time and number to use. We pay the call.
What we test on, what we don’t.
We aim for the platform to work with the assistive technologies most commonly used in Australia and to follow accepted browser-support targets.
Tested combinations
- NVDA + Firefox latest, on Windows 11
- VoiceOver + Safari latest, on macOS Sonoma and Ventura
- VoiceOver + Safari, on iOS 17 and iOS 18 (iPhone)
- TalkBack + Chrome latest, on Android 14
- Dragon NaturallySpeaking on Windows for voice control of forms
- Browser zoom up to 400%, OS-level text scaling up to 200%
- Both light and dark colour schemes
Not yet tested
- JAWS (we use NVDA as the primary Windows screen reader for testing). JAWS testing planned Q3 2026.
- Switch control (iOS) for navigation. Coverage planned Q4 2026 with users from a partner organisation.
- Refreshable Braille display compatibility, scheduled for the Q1 2027 audit.
If you use a combination not listed and something doesn’t work, that’s exactly the kind of report we want at access@minglein.com.au.
If we don’t fix it, here’s how to escalate.
Most accessibility reports are resolved through email with our ops team. If you don’t get a response inside 10 business days, or you’re not satisfied with the resolution, you have two further options.
- Email legal@minglein.com.au for a formal review by MingleIn’s legal contact. We acknowledge inside 24 hours and respond inside 14 calendar days.
- Contact the Australian Human Rights Commission, which administers the Disability Discrimination Act 1992 and accepts disability discrimination complaints relating to digital services.
We won’t ask you to sign a non-disclosure agreement as a condition of fixing an accessibility issue. Ever.