Accessibility

Our commitment to accessibility

We’re Sensortree Pty. Ltd, the company that builds Clovo. We want everyone to be able to use Clovo, whether they’re booking a class, running a studio or learning about us online. This statement explains the accessibility features in place, the areas we’re improving and how to contact us if you encounter a barrier.

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA across our products. WCAG is the international standard for digital accessibility, published by the World Wide Web Consortium (W3C), and is the same standard referenced by Australian, U.S., U.K., and EU public-sector procurement rules.

Scope of this statement

This statement applies to the digital experiences we build and operate:

The Clovo marketing website at clovo.au.

Clovo Studio, the studio-operator dashboard at studio.clovo.au.

Clovo Landing Pages, the studio-branded customer-facing pages we host on subdomains of clovo.au and on studios’ own domains.

The Clovo iOS app, available on the App Store.

The Clovo Android app, available on Google Play.

The Clovo WordPress Plugin and Clovo Live Activity widget.

It does not apply to content controlled by individual studios that use Clovo (covered separately under Studio-controlled content below) or to third-party services we integrate with (covered under Third-party content).

Conformance status

WCAG sets out requirements for making digital content accessible to people with disabilities. It has three levels: A, AA and AAA. Level AA is the standard we work towards.

Clovo partially conforms with WCAG 2.2 Level AA. Many accessibility features are in place across the platform, with recent improvements to screen-reader support, text scaling, contrast and keyboard access. Some areas still need improvement to meet the standard fully; these are outlined below.

The summaries below reflect reviews of the iOS and Android source code on 4 October 2026, Clovo Studio source code and internal test records on 12 September 2026, and the marketing website on 18 August 2026. These are internal reviews, with further testing using assistive technologies still to complete. An independent conformance audit has not yet been carried out. Recent app improvements may become available at different times as updates are released.

Clovo marketing website (clovo.au): substantially conforms with WCAG 2.2 Level AA. The current source includes a skip-to-main-content link, declared page language, visible keyboard-focus treatment, reduced-motion handling for site animation, and strong contrast for primary text. Known issues remain in the navigation mega-dropdown and a handful of secondary surfaces.

Clovo Studio dashboard (studio.clovo.au): partially conforms. Alongside skip links, visible keyboard focus, labelled forms and reduced-motion safeguards, recent work improves text, form-control and client-tag contrast in light and dark themes. Reports now provide expandable, keyboard-accessible data tables alongside charts, and multiple line and area series use different dash patterns. Focused automated checks found no accessibility violations on seven dashboard pages in both themes. Further manual testing is planned for the pages, interactions and assistive technologies outlined below.

Clovo iOS app: partially conforms, and recent work has substantially extended VoiceOver and Dynamic Type support. VoiceOver now describes the major cards and most booking, purchase, Member Shop, account and administration flows, identifies selected options, announces progress while a request is working, and gives the location behind every map. Class, membership, Member Shop and trial cards and the studio overview rearrange at the largest text sizes so names and prices stay readable. Text scaling, text and icon status cues, a single verification-code field, and decorative illustrations that respect Reduce Motion are all in place. We’re continuing to work on heading navigation, Live Activity text scaling and motion in other transitions.

Clovo Android app: partially conforms, and a recent accessibility pass has extended TalkBack support across the app. Tappable cards and rows are announced as buttons, loading indicators are labelled, sign-in, form and purchase errors are read out as they appear, single-choice options are grouped, and each verification-code digit is identified. Dark-mode fixes improve the visibility of plan prices, names and administration content, and decorative illustrations hold still when system animations are turned off. We’re continuing to work on touch targets, heading coverage, single-field code entry and contrast with studio-supplied colours.

We track accessibility improvements across the platform and use them to guide work in each release.

Standards we measure against

Web (clovo.au, Clovo Studio, Clovo Landing Pages): WCAG 2.2 Level AA.

iOS app: WCAG 2.2 Level AA, expressed through Apple’s Accessibility framework: VoiceOver, Dynamic Type, Reduce Motion, Reduce Transparency, Bold Text, and the Apple Human Interface Guidelines for Accessibility.

Android app: WCAG 2.2 Level AA, expressed through the Android Accessibility framework: TalkBack, font scaling, the Compose semantics modifier, the Material Design 3 accessibility guidance, and the Android Accessibility Developer Guidelines.

Compatibility with assistive technologies

Clovo is designed to work with recent versions of mainstream operating systems, browsers and assistive technologies. The combinations below guide our reviews. Compatibility testing is ongoing, and older configurations may work but are not actively supported.

Web: recent versions of Safari (macOS, iOS), Chrome (macOS, Windows, Android), Firefox (macOS, Windows), and Edge (Windows), reviewed with VoiceOver on macOS and iOS, NVDA on Windows, and TalkBack on Android.

iOS: supported versions of iOS as declared in the App Store listing, reviewed with VoiceOver, Dynamic Type, Reduce Motion, Reduce Transparency, Bold Text, Smart Invert, and external keyboards via Bluetooth.

Android: supported versions of Android as declared on the Google Play listing, reviewed with TalkBack, system font scaling, high-contrast text, colour inversion, Switch Access, and external keyboards.

Our compatibility support focuses on the current release and the two previous major versions.

Technical specifications

Accessibility of Clovo relies on the following technologies to work with the particular combination of web browser and any assistive technology or plugins installed on your device: HTML, CSS, JavaScript, JSON, ARIA, SVG, and platform-native APIs (UIKit/SwiftUI for iOS; Android View/Jetpack Compose for Android). These technologies are relied upon for conformance with the accessibility standards used.

Current improvements and limitations: Clovo marketing website

The website was rebuilt in 2025 and most pages have been reviewed against WCAG 2.2 AA. The following areas are part of our ongoing accessibility work:

The platform and company navigation dropdowns work with keyboard activation. Screen-reader support still needs improvement: the trigger does not announce whether the dropdown is expanded, and the dropdown has no explicit menu role. We plan to improve these announcements.

Some muted metadata and timestamps use a colour below the 4.5:1 contrast requirement. We’re reviewing where it appears so this text is easier to read.

Primary pages follow a logical heading order. A small number of article and case-study templates have skipped heading levels. We are addressing these as part of a broader template review.

Marketing video that auto-plays as a background asset is decorative, plays muted, and is paused under the user’s prefers-reduced-motion preference. We are reviewing whether to add an explicit pause control.

Current improvements and limitations: Clovo Studio dashboard

Recent work has improved contrast, keyboard access and report alternatives in Clovo Studio. We’re continuing with the following checks and improvements:

A shared 2-pixel focus ring helps keyboard users see which control is selected. We’re checking controls with their own focus styles to confirm they are equally clear and visible.

Shared action buttons now meet the WCAG 2.2 minimum target size in the current source. We’re checking specialised controls, native-looking controls and public-facing pages against the same 24×24 CSS-pixel minimum.

Shared transitions and site animations respect reduced-motion preferences. We’re checking JavaScript-driven transitions and individual components as well. The September review covered contrast, keyboard access and reflow in light and dark themes; further screen-reader testing and checks of pages with populated data, open controls and error states remain to be completed.

The heading hierarchy on a small number of admin pages skips levels (for example, jumping from h1 to h3). This is being corrected.

Current improvements and limitations: Clovo iOS app

Recent iOS improvements support VoiceOver, larger text sizes and reduced motion. Our current work includes:

The empty-state, trial, growth and payment-success illustrations respect the iOS Reduce Motion setting and are hidden from VoiceOver as decorative content. We’re reviewing other transitions, and haptic feedback, against device accessibility and feedback preferences.

The sign-in code field is a single field for VoiceOver, labelled “Verification code”, reading back what has been entered and announcing “Verifying code” while it checks; its six-character visual presentation is hidden from VoiceOver. We’re continuing to test it across validation, retry and one-time-code autofill.

Live Activity progress bars are labelled “Class progress” for VoiceOver. The lock-screen and Dynamic Island layouts use a mix of system text styles and fixed-size time text, and we’re testing how the time text scales and is spoken at the largest accessibility sizes.

Screen titles and list section headers are announced as headings by VoiceOver. We’re extending heading navigation to section titles in custom layouts, such as the class detail and account screens.

Current improvements and limitations: Clovo Android app

Recent Android improvements support TalkBack, clearer dark-mode text and reduced motion. Our current work includes:

Forms, closure notices, membership cancellation and class plans mark their section headings for TalkBack using the Compose semantics { heading() } annotation. We’re extending this to the Our Studio, booking, class detail, account and admin screens so every section title can be reached using heading navigation.

We’re raising the back button on detail screens (currently 36 dp) and a few icon-only controls and page indicators to Android’s recommended 48-dp minimum touch target.

The trial, empty-state, sign-in and purchase-success animations have been rebuilt as native illustrations that show their finished state when system animations are turned off, and TalkBack skips them as decoration. The device-tilt effect and the studio-selection icon stream also hold still. We’re continuing to test other transitions with system animations reduced or turned off.

Each box in the sign-in code field is announced with its position, for example “Verification code, digit 1 of 6”, and sign-in errors are read out as they appear. We’re working towards presenting the code to TalkBack as a single six-digit field.

Recent changes correct text colours in dark mode, including plan prices and administration content. We’re also checking chip and card backgrounds against studio-supplied colours in both themes.

Studio-controlled (user-generated) content

Studios create and manage much of the content their members see in Clovo. We provide the platform’s accessibility features, while studios help make their own text, imagery and branding accessible.

Studio-managed content includes the studio name; the studio logo and other uploaded imagery; brand primary and secondary colours used on customer-facing pages; class names, descriptions, and class-type icons; trainer names, photographs, biographies, and titles; location names and descriptions; membership plan, credit-pack, and trial offer names and descriptions; Member Shop product names, images, and descriptions; announcements and welcome-email copy; and liability waiver content.

Clovo’s structure, focus handling, text scaling, motion settings and screen-reader support help make studio content accessible. The content and branding a studio supplies also affect the experience. Areas to check include logos displayed without alternative text, brand colours with insufficient contrast, names that are difficult for screen readers to pronounce, and images that convey information missing from the accompanying text.

If you encounter a barrier on a studio-branded page, you can contact the studio or reach us using the details below. We can help identify the cause and work with the studio where needed.

Guidance for studio operators

These checks can help studio operators make their content easier for members to read, understand and use when booking and paying.

Brand colours: check that text has at least 4.5:1 contrast against its background. Clovo Studio’s branding settings show a live contrast indicator beside each colour picker, with Good (≥ 4.5:1), Fair (≥ 3:1) and Low (< 3:1) badges and ratios against white and dark backgrounds. Choose combinations rated Good for normal-sized text. The indicator does not compare primary and secondary colours or check text on branded chips and overlays; a WCAG contrast checker can help you check those combinations.

Logos: upload a logo with a transparent or solid background that doesn’t depend on a particular page colour to be readable. SVG and high-resolution PNG are best.

Imagery: use clear, well-lit trainer photos, class images and product photos. Include important information in the accompanying text so people using screen readers or magnification can access it too.

Class and product names: use clear, descriptive names such as “Reformer Pilates for beginners”. Sentence case is easier to read, and words help convey meaning that decorative characters or emoji may not communicate to a screen reader.

Descriptions: keep paragraphs short. Lead with what the class is and who it’s for. If the class has a duration, intensity level, or equipment requirement, state it in words rather than relying on icons alone.

Trainer bios: include the trainer’s name, qualifications and approach in the text alongside their photo.

Welcome emails and announcements: use link text that describes the destination, such as “Read our cancellation policy”, so members know what to expect.

Liability waivers: write waivers in plain language at a sensible reading level.

Your studio may have accessibility obligations that also apply to the content you share through Clovo. If you need help understanding the platform’s accessibility features or improving your content, please get in touch.

Third-party content

Clovo integrates with third-party services that publish their own accessibility information. We consider these services as part of the overall experience, although changes to their interfaces are managed by their providers.

Stripe: used for payment processing. Card-entry forms and Stripe-hosted checkout flows are governed by Stripe’s accessibility statement.

Apple Maps and Google Maps: used to display studio locations. Map content and pan/zoom interactions are governed by the underlying platform.

App Store and Google Play: used to distribute the Clovo iOS and Android apps. The store listings themselves are governed by Apple and Google.

Email and SMS providers: used to deliver booking notifications, password resets, and marketing communications.

Where a third-party service is essential, such as payment processing, we test the overall flow with a screen reader and keyboard. The provider remains responsible for accessibility within its own interface.

How we test and assess accessibility

Our accessibility work combines automated checks, manual testing and shared design standards.

Shared design standards: we document contrast, focus styles, typography and spacing so accessibility is considered when components are created or updated.

Automated checks: we use static analysis and accessibility linters during development and CI.

Manual review areas: keyboard-only navigation; screen-reader smoke tests with VoiceOver, NVDA, and TalkBack on critical flows (sign up, sign in, browse studios, book a class, manage a membership, take payment); zoom and reflow at 200% and at the largest accessibility text size each platform offers; reduce-motion and high-contrast modes. The reviews above cover selected areas, with broader testing across pages and devices ongoing.

External assessment: we have not yet commissioned an independent third-party accessibility conformance audit. We plan to arrange one after completing the current improvements outlined above.

This statement was prepared on 18 August 2026 and updated on 12 September and 4 October 2026 by Sensortree Pty. Ltd. The September update reflected a source-level review of Clovo Studio, iOS and Android changes and the recorded dashboard dark-mode accessibility checks. The October update reflects the accessibility improvements made to the iOS and Android apps in early October 2026.

Feedback and reporting a barrier

We welcome your feedback on the accessibility of Clovo. If you encounter a barrier, or if there’s an assistive technology or workflow we should be supporting better, please tell us.

Email: hello@clovo.au.

Web: contact form on clovo.au/support.

Postal: please request a postal address by email and we will provide one.

If you can, share the page or feature, what happened, and the device or assistive technology you were using. Screenshots or steps can help us investigate, but you’re welcome to contact us with whatever information you have.

We aim to acknowledge accessibility feedback within five business days and provide a substantive response within twenty business days. Where appropriate, this will include a plan to address the issue or a workaround. If a fix is going to take longer than that, we’ll tell you why and give you a realistic timeframe.

Formal complaints and enforcement

If you’re not satisfied with how we’ve responded to your accessibility feedback, you have the right to make a formal complaint to a regulatory authority.

In Australia, the Disability Discrimination Act 1992 (Cth) prohibits disability discrimination in the provision of goods, services, and facilities, including digital ones. Complaints can be lodged with the Australian Human Rights Commission at humanrights.gov.au.

If you’re based outside Australia, the equivalent body in your country may also be able to help: for example, the Equality and Human Rights Commission in the United Kingdom, the U.S. Department of Justice in the United States, or your national equality body in the European Union.

Continuous improvement

We review this statement at least every twelve months and whenever a major release materially changes accessibility across Clovo. We update the areas listed above as improvements are released and new needs are identified.

Accessibility is an ongoing part of how we develop Clovo. Your feedback helps us understand where further improvements will make a difference.