Skip to main content
Muse Collectivity

Accessibility Statement

Last reviewed: February 2026

Our Commitment

We are committed to making Muse Collectivity accessible to all users, including people with disabilities. We believe that everyone should be able to discover, collaborate on, and share music — regardless of ability.

We recognise our obligations under the Disability Discrimination Act 1992 (Cth) and the Australian Human Rights Commission's guidelines on web accessibility. We are working to ensure our platform meets or exceeds accessibility standards so that all users can participate fully.

Conformance Target

Muse Collectivity aims to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. These guidelines are developed by the World Wide Web Consortium (W3C) and are the internationally recognised standard for web accessibility.

WCAG 2.2 Level AA conformance means that our platform strives to be:

  • Perceivable: Information and interface components are presented in ways that all users can perceive
  • Operable: Interface components and navigation are operable by all users
  • Understandable: Information and interface operation are understandable
  • Robust: Content is robust enough to be interpreted by a wide range of user agents, including assistive technologies

Measures We Have Taken

We have implemented the following accessibility features and practices across Muse Collectivity:

Design and Interface

  • Colour contrast ratios that meet or exceed WCAG 2.2 AA requirements (minimum 4.5:1 for normal text, 3:1 for large text)
  • Consistent and predictable navigation across all pages
  • Clear visual focus indicators for keyboard users
  • Minimum touch target sizes of 44x44 pixels for interactive elements
  • Responsive design that works across screen sizes and zoom levels up to 200%

Semantic Structure

  • Proper HTML heading hierarchy (h1 through h6) on all pages
  • Semantic HTML elements (nav, main, article, section, aside, footer) for clear document structure
  • ARIA labels and roles where semantic HTML alone is insufficient
  • Skip-to-content links for keyboard navigation
  • Descriptive page titles that reflect the current page content

Forms and Interaction

  • All form inputs have associated labels
  • Error messages are clearly associated with the relevant form fields
  • Status messages and notifications are announced to screen readers using ARIA live regions
  • All interactive elements are fully operable via keyboard
  • No content requires interaction that depends solely on a specific type of motion (such as shaking or tilting)

Media and Content

  • Audio players include visible playback controls that are keyboard accessible
  • Images include meaningful alternative text where appropriate
  • Decorative images are marked as such and hidden from assistive technologies
  • No content flashes more than three times per second

Development Practices

  • Regular automated accessibility testing during development
  • Manual keyboard-only and screen reader testing of key user flows
  • Accessibility considerations are part of our design and code review processes

Known Limitations

While we strive for full accessibility, we are aware of the following limitations that we are actively working to address:

  • Audio waveform visualisations: Audio waveform displays are currently decorative and do not convey information to screen readers. Playback controls and time indicators are accessible alternatives.
  • User-uploaded content: We cannot guarantee that all content uploaded by users (such as images or portfolio descriptions) meets accessibility standards. We encourage users to provide descriptive alt text for uploaded images.
  • Third-party integrations: Some embedded content from third-party services (such as payment forms from Stripe) may have accessibility limitations outside our direct control. We work with providers who prioritise accessibility.

We are committed to improving these areas and welcome your feedback on any accessibility barriers you encounter.

Assistive Technology Compatibility

Muse Collectivity is designed to be compatible with the following assistive technologies:

  • Screen readers (VoiceOver on macOS/iOS, NVDA and JAWS on Windows, TalkBack on Android)
  • Screen magnification software
  • Voice recognition software
  • Keyboard-only navigation
  • Switch access devices

The platform is tested against the latest stable versions of Chrome, Firefox, Safari, and Edge browsers.

Feedback and Contact

We welcome your feedback on the accessibility of Muse Collectivity. If you encounter any accessibility barriers, have difficulty using any part of the platform, or have suggestions for improvement, please let us know:

Email: accessibility@musecollectivity.com
Business: Muse Collectivity

When contacting us about an accessibility issue, it is helpful to include:

  • A description of the issue you experienced
  • The page or feature where the issue occurred
  • The browser and assistive technology you were using (if applicable)
  • Any steps to reproduce the issue

We aim to respond to all accessibility feedback within 5 business days. For urgent access issues that prevent you from using a core feature of the platform, please indicate this in your message and we will prioritise your request.

Formal Complaints

If you are not satisfied with our response to an accessibility concern, you have the right to lodge a complaint with the Australian Human Rights Commission (AHRC) under the Disability Discrimination Act 1992. You can contact the AHRC at humanrights.gov.au.

Review Schedule

This accessibility statement was last reviewed in February 2026. We review our accessibility practices and update this statement at least once every 12 months, or whenever significant changes are made to the platform.