ReviseOnline is working towards Web Content Accessibility Guidelines (WCAG) 2.2 Level AA across the platform. We haven't completed a formal conformance evaluation, so this reflects the accessibility work we do today rather than a certified level of conformance - the full detail is in our Accessibility Statement.
- The standards we align to
- What we already do
- Known limitations
- How to report an accessibility issue
Standards we align to
WCAG 2.2 Level AA, the Disability Discrimination Act 1992 (Cth) - consistent with Australian Human Rights Commission guidance - and the accessibility and inclusion criterion in the Australian Government Digital Service Standard for public-facing pages and school procurement flows.
What we already do
Automated WCAG 2.1 Level AA checks run on every change to the public site, sign-in flow, and student and teacher dashboards, in both light and dark themes - a change that introduces a violation doesn't ship. We use semantic HTML5 with ARIA only where needed, full keyboard navigation with a skip-to-content link on public and sign-in pages, visible focus states, 4.5:1 text contrast on the surfaces our automated checks cover, labelled form inputs with error messaging shown in text rather than colour alone, and captioned video where we publish it, with transcripts available on request.
Known limitations
We don't yet run a routine assistive-technology testing programme - automated checks can't catch everything, and regular screen-reader, magnification or voice-control testing is work we intend to take on. No independent audit has been commissioned, so we can't yet supply a third-party conformance report. Our automated checks cover a defined set of pages; surfaces like the admin panel and less-travelled dashboard routes aren't yet gated. User-uploaded images without a supplied description are exposed as decorative to assistive technology - we're working with teachers to add an alt-text prompt at upload. Some legacy assessment items don't yet have a keyboard equivalent for every drag-and-drop interaction, with replacements rolling out term by term. Third-party integrations such as Stripe checkout and Learnosity question players follow their own vendor accessibility conformance. PDF exports are tagged for screen readers, but complex tables and mathematical notation may still need manual review.
Reporting an issue
If you hit a barrier we haven't caught, email support@reviseonline.com - we track and prioritise every report.
Read the full Accessibility Statement.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article