#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. Our WCAG 2.2 Level AA target is not a certification, and nothing in this statement should be read as one.
#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.
Where an Institution uses them, this statement also covers these journeys: electronic consent and signing; payment pages, including card payments and PayTo payment agreements; booking calendars and time-slot selection; event calendars, lists and tables; payroll documents such as pay slips; certificate, letter and card builders; and public credential verification pages. Not every journey is available to every Institution. Some steps in these journeys take place in services Academyship does not provide, such as Stripe-hosted payment pages or the payer's own banking app; Section 9 explains how those are handled, and Section 8 describes the limitations and alternatives that apply.
#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 will test accessibility using a combination of automated accessibility checks, manual keyboard testing, zoom and reflow testing, screen-reader testing and review of user feedback. Automated checks will form part of the development and quality-assurance process, but will not be treated as a substitute for manual testing.
Academyship will record accessibility test results, prioritise them according to user impact and track them through remediation, and will review material new interfaces and substantial redesigns for accessibility before production release. This statement does not claim that every page, module, journey or generated document has been tested with each of these methods, or with every browser and assistive-technology combination. The scope and outcome of any independent assessment are reported separately in Section 13.
#07Assistive technology
Academyship will test 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.
Journeys that need particular care
Some journeys include steps that can be hard for some people to complete. The table below describes those steps and what you can ask for. Where an alternative depends on the document, the payment method or the Institution's own process, the Institution decides whether it can offer that alternative. Academyship will work with you and the Institution to find a workable option where one is available. You can contact accessibility@academyship.com.au about any of them.
| Journey | What can be difficult | What you can ask for |
|---|---|---|
| Electronic consent and signing | Drawing a signature with a mouse, finger or stylus; signing invitations or pages that expire; documents shown as images or PDFs. | Ask the person or Institution that sent the document for another way to sign or respond — for example, a typed signature where the signing process offers one, help to sign, more time or a new invitation, or the document in an accessible or paper format before you sign. Whether an alternative is suitable can depend on the document and the law that applies to it. |
| One-time codes, CAPTCHA and time limits | Where these are used — for example, at sign-in or on a time-limited link — a code or link may expire before you can use it, or a check may rely on sight, hearing or memory. | Tell us or your Institution if a code, check or time limit stops you from finishing a task. We will look for another way for you to complete it, such as a new code or link, more time, or help from your Institution, where one is available. |
| Payments, including PayTo | Card entry, confirmation steps and any time limits, and steps completed outside Academyship on a Stripe-hosted page or in your banking app. | Ask the Institution that is charging you about another way to pay or for help completing the payment. Tell us about barriers on Academyship's own pages; for barriers on a provider's page, see Section 9. |
| Booking calendars | Calendar grids and time-slot pickers, and temporary holds on a place that can expire while you complete the booking. | Ask the Institution to make or hold the booking for you, or to give you the available times in another format. |
| Event calendars and tables | Large or complex tables and calendar views. | Ask for the information in another format, such as a list. |
| Payroll documents | Pay slips and other payroll documents or exports, which may be PDFs or spreadsheets without full accessibility structure. | Staff can ask their employer for a document in an accessible format. Employers can ask us for help. |
| Certificate, letter and card builders | Visual design tools that rely on dragging, positioning or a drawing canvas, and outputs that are images or PDFs. | Institution staff can ask us for help, or for another way to complete a design. People who receive a document can ask for an accessible version (see Section 10). |
| Public credential verification | Verification pages are used by people outside the Institution, such as employers, on any device or assistive technology. | Tell us about any barrier. You can also ask the issuing Institution to confirm a credential another way. |
A status (for example, paid, overdue, booked or full) may be shown with colour. Where colour is the only way a status is shown, please tell us; we treat that as an accessibility defect.
#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.
Some steps in a journey happen in services Academyship does not provide, such as Stripe-hosted payment pages, a bank's app used to approve a PayTo agreement, outside calendar services a person chooses to add an event to, and the email or SMS apps on a person's device. If a barrier is in one of those services, tell us: we will tell you what we can and cannot change, raise it with the provider where we reasonably can, and help you find another way to complete the task where one is available. Third-party services and Institution content do not reduce Academyship's own responsibility for the parts of a journey that Academyship provides.
#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.
Some generated documents — including certificates, cards, pay slips, signed documents and documents built in a visual designer — are PDFs or images and may not include full text structure, reading order or text alternatives. If you need to read or use one of these documents with assistive technology, you can ask for it in an accessible or alternative format.
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:
- Email: accessibility@academyship.com.au
- Phone: +61 481 810 181
- Post: Accessibility, ACADEMYSHIP PTY LTD, Unit 44, 3-7 Fetherstone Street, Bankstown NSW 2200, Australia
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 | Date | Summary of changes |
|---|---|---|
| 2.1 | 9 October 2026 | Extended the coverage to electronic consent and signing, payment and PayTo flows, booking calendars, event tables, payroll documents, certificate and card builders, and public credential verification. Added a table of journeys that need particular care and the alternatives a person can ask for, including for signature drawing, one-time codes, CAPTCHA, time limits, PDF and canvas-based documents and colour-only status. Restated the testing and assistive-technology descriptions in Sections 6 and 7 as commitments, and stated that this statement does not claim every area has been tested with every method. Clarified that the WCAG 2.2 Level AA target is not a certification. Expanded the third-party and generated-document sections. |
| 2.0 | 12 September 2026 | Published 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. |