Accessibility

Students are the people who spend the most time in RTO Grow, and they arrive with every kind of device, connection and access need. Making the platform usable for them is part of building it, not a project we will get to later.

This statement sets out where we actually stand against the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA — including what we have not done yet.

The RTO Grow public website meets WCAG 2.1 Level AA on all automated testing, with no outstanding issues.

We describe the site as substantially conformant rather than fully conformant, because automated testing alone cannot establish full conformance. The scope and limits of that testing are set out below.

Last reviewed: 8 August 2026.

We test with axe-core against the WCAG 2.1 A and AA rule sets, across thirteen public pages: home, pricing, about, team, security, integrations, contact, book a demo, this page, service commitments, blog, FAQs and AVETMISS reporting.

Every one of those pages returns zero violations. That covers page structure and headings, landmark regions, form labelling, text alternatives for images, link purpose, language of page, keyboard focus order and colour contrast.

On 8 August 2026 our audit found 172 colour contrast failures across the site — text that was legible for most people but fell below the 4.5:1 ratio the standard requires for normal-size text.

All 172 were corrected the same day: the white text on our green buttons, the muted descriptions in the footer, the section labels on several pages, the pale text inside the highlighted pricing card, and the buttons on our cookie consent banner. Each replacement colour was calculated against the standard rather than judged by eye, and the site re-tested to zero.

We are recording this rather than quietly fixing it, because a statement that only ever describes success is not much use to you.

We want to be straight about the scope of that testing rather than let an automated pass stand in for a complete one.

Automated testing catches only part of what the standard covers — commonly estimated at around a third of issues. It does not judge whether alternative text is meaningful, whether a workflow can be completed with a keyboard alone, or how a screen reader announces a complex screen.

We have not yet commissioned an independent accessibility audit, we have not published a VPAT or Accessibility Conformance Report, and we have not completed structured manual testing with assistive technology across the signed-in student and trainer experience. Those are our next steps, and we would rather tell you that than imply a level of assurance we have not earned.

If any part of RTO Grow is difficult or impossible for you to use, we want to know — including on behalf of a student.

Email hello@rtogrow.com.au with the page or screen, what you were trying to do, and the assistive technology you were using if any. We respond the same business day during Australian business hours.

If you need information from the platform in a different format, ask us and we will provide it.

We re-run this testing when we make significant changes to the public site or the student experience, and at least twice a year. This page is updated with the result each time, including anything still outstanding.

Prepared 8 August 2026. Next scheduled review: February 2027.