Accessibility

Our commitment

RTOAiVoX is used by educators and adult learners, including people who use screen readers, keyboard-only navigation, magnification and other assistive technology. We treat an access barrier as a defect, not a feature request.

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. We want to be straight with you about where we are against that aim: we have not yet completed a formal audit, so we do not claim conformance. The sections below describe what we have actually done and what we know is outstanding.

What we have done

• Semantic HTML throughout: headings in order, real buttons and links, lists marked up as lists, so assistive technology reads the structure we intended.
• Every form field has a visible, associated label. We do not rely on placeholder text to say what a field is for.
• Results that update without a page load announce themselves, so a screen-reader user is not left waiting on a change they cannot see.
• Colour is never the only way information is conveyed. Status and meaning are always also carried in text.
• Pages work at increased browser zoom and on small screens without content being cut off or requiring horizontal scrolling.
• Documents we generate use real heading structures and table markup rather than visual formatting alone, so what you download is navigable too.

What we know is not right yet

Listing these is deliberate. If you hit one of them, you will know it is known and that reporting it still helps us prioritise.

• No formal audit. We have not had an independent WCAG 2.1 AA assessment. Until we do, treat our conformance as untested rather than achieved.
• Colour contrast has not been measured everywhere. Some secondary text and borders may fall below the required ratios.
• Some complex controls need work. Multi-step forms and filter controls have not all been tested with a screen reader end to end.
• Generated documents vary. DOCX and PPTX files are structured, but we do not yet check every generated file for alternative text on images.
• Third-party content. Where we link out to training.gov.au, a provider website or a supplier, we do not control that site’s accessibility.

Tell us about a barrier

If something stops you using RTOAiVoX, we want to know, even if it is listed above. Knowing that a specific barrier affects a real person changes what we fix first.

Email info@rtoaivox.com.au or use the help and contact page. It helps if you can tell us the page, what you were trying to do, and what assistive technology and browser you were using, but please report it either way rather than not reporting it.

We aim to acknowledge accessibility reports within two business days and to tell you what we are going to do about it, including if the answer is “not soon”.

If you need something in another format

If you cannot access a document the platform generated, contact us and we will provide the content in an alternative format. There is no charge for this.