Skip to main content
Accessibility

Accessibility Statement

Effective 12 September 2026 · Last updated 12 September 2026 · Version 2.0 · ACADEMYSHIP PTY LTD · ACN 698 283 448 · ABN 89 698 283 448

#01Our commitment

ACADEMYSHIP PTY LTD (ACN 698 283 448, ABN 89 698 283 448) is committed to making its products usable by as many people as possible, including people with disability. We treat accessibility as an ongoing part of how we design, build and maintain the ACADEMYSHIP platform, its portals, generated documents and marketing website.

#02Target standard

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA as our target standard. This is a design and development target that we work towards; it is not a claim that every page or feature currently conforms in full. Where we identify gaps, we prioritise and address them as described below. We do not currently publish a claim of full WCAG conformance, because we do not yet hold a current independent audit covering that scope.

#03What this covers

This statement covers the ACADEMYSHIP web application and administrator experience, the student and guardian portals, documents generated by the platform, the mobile and responsive experiences, and our marketing website at academyship.com.au. Different areas may be at different stages of accessibility maturity; where a distinction matters, we note it in this statement.

#04Measures we take

Academyship incorporates accessibility into product design, development, testing and maintenance. Our current accessibility practices include:

  • semantic structure and logical headings;
  • keyboard operability;
  • visible focus;
  • programmatic labels and instructions;
  • accessible error identification;
  • colour contrast;
  • zoom and reflow;
  • reduced-motion support;
  • common screen-reader compatibility;
  • accessible names for controls;
  • accessible tables;
  • accessible authentication; and
  • accessible status and validation messages.

These practices support our WCAG 2.2 Level AA target. They do not constitute a claim that every page, module or generated document fully conforms.

Where an Institution selects custom colours, logos, templates or other white-label branding, the Institution is responsible for ensuring those selections maintain adequate contrast, readability and accessibility. Academyship may restrict branding configurations that materially reduce accessibility.

#05Student and guardian portals

Student and guardian portals are used by a wide range of people, including children and family members who may use assistive technology. We give particular attention to the accessibility of these portals and to plain, clear language. Institutions can help by using clear content and by providing information in alternative formats where a student or family needs it.

#06Testing and review approach

Academyship's accessibility testing program combines automated accessibility checks, manual keyboard testing, zoom and reflow testing, screen-reader testing and review of user feedback. Automated testing is included in the development and quality-assurance process, but is not treated as a substitute for manual testing.

Test results are recorded, prioritised according to user impact and tracked through remediation. Material new interfaces and substantial redesigns are reviewed before production release. The scope and outcome of any independent assessment are reported separately in Section 13.

#07Assistive technology

Academyship tests with current versions of widely used browsers and representative assistive technologies across desktop and mobile. Compatibility can vary between browser, operating-system and assistive-technology combinations. If a User encounters an issue, Academyship will investigate the reported combination and provide a reasonable workaround or alternative where available.

Where available, Razi voice typing may provide an additional input method for supported fields and editors. It uses speech recognition supplied by the User’s browser, operating system or device; Razi is not an Amazon Bedrock generative-AI feature. Academyship does not receive or store raw audio through Razi, and receives and processes only the resulting text after it is inserted into an Academyship field, in the same way as manually entered Customer Data. The applicable provider may process speech under its own privacy terms and technical configuration. Razi does not make decisions or perform autonomous actions, and is not guaranteed to meet every accessibility need or work with every browser, device, language, permission setting or network condition. Users should review the resulting text before saving it, and should use another input method where Razi is not suitable.

#08Known limitations

We publish known limitations honestly rather than implying a perfect status. Areas we are actively working to improve include: accessible names on some complex interactive controls (for example, certain sliders and toggles); full reduced-motion coverage for all animated elements; and the accessibility of some complex data tables and generated documents. If you rely on a feature that is not yet fully accessible, contact us and we will provide a workaround or alternative where we can.

#09Third-party content and integrations

Some content or functionality may come from third-party services that an institution chooses to connect, or from content that institutions and users create. We do not control the accessibility of third-party services or user-created content, though we encourage accessible content and will help where we reasonably can.

#10Generated documents

Academyship supports generation of documents such as letters, reports and certificates. Accessibility can depend on the selected template, the content entered by the Institution and the output format. Academyship provides accessible template and content practices and continues to improve generated-document accessibility.

An Institution or User who requires a document in an accessible or alternative format can contact accessibility@academyship.com.au.

#11Feedback and alternative formats

We welcome your feedback on the accessibility of Academyship, and we can provide our legal and support documents in an alternative format on request. Contact us at:

Please tell us the page or feature involved, the problem you experienced, and the assistive technology you were using, so we can respond effectively.

#12Response and remediation

We aim to acknowledge accessibility feedback promptly and to work with you on a resolution. We prioritise fixes based on severity and impact. We do not publish fixed remediation deadlines, because timeframes depend on the nature of the issue, but we will keep you informed of our approach for issues you raise.

#13Formal audit status

Academyship does not currently publish a completed independent Accessibility Conformance Report or VPAT covering the entire platform. Where an independent assessment has been completed for a specific scope, Academyship describes that scope accurately and makes appropriate procurement information available on request. We do not claim full WCAG conformance beyond the scope supported by current evidence. Procurement teams can contact accessibility@academyship.com.au to discuss current status.

#14Complaints and escalation

If you are not satisfied with our response to an accessibility issue, you can escalate to complaints@academyship.com.au. Individuals also have rights under the Disability Discrimination Act 1992 (Cth) and may contact the Australian Human Rights Commission (humanrights.gov.au). This statement is provided for information and does not limit any rights you have under law.

#15Changes and review

We review this statement at least annually, and out of cycle after a material product, design or assessment change. We update the "Last updated" date when we change it, and prior versions can be requested from legal@academyship.com.au.

#16Change history

Version history for this Accessibility Statement.
VersionDateSummary of changes
2.012 September 2026Published the Accessibility Statement for Academyship’s production launch, including its coverage of the platform, portals, generated documents, feedback, known limitations, testing, audit status and escalation.

#17Related documents