Skip to content

Legal & policies

Accessibility

Education software that a learner cannot use is education software that excludes them. This is where we are, stated honestly, including where we fall short.

Last updated 18 August 2026

Our commitment

We build Pallara to be usable by everyone who needs it, including people using screen readers, keyboard-only navigation, magnification, or reduced-motion settings. We target WCAG 2.1 Level AA.

Current status

Pallara is partially conformant with WCAG 2.1 Level AA. Partially conformant means most of the platform meets the standard, and some parts do not yet. We have not commissioned an independent accessibility audit, and we will say so plainly until we have.

What is in place

  • Semantic HTML with real headings, landmarks, lists and buttons — interactive elements are buttons and links, not styled containers.
  • A visible focus indicator on every interactive element, and full keyboard operability.
  • Text and interface colour combinations checked against the AA contrast ratio, in both the light and dark interfaces.
  • Accessible names on icon-only controls, and status regions announced to assistive technology.
  • prefers-reduced-motion is honoured throughout — all animation is disabled when the operating system asks for it.
  • Text resizes and reflows without loss of content down to a 320-pixel-wide viewport.
  • Course content authoring includes an accessibility checker that flags missing alternative text, skipped heading levels, tables without headers and unclear link text, and drafts alternative text for review.

Known limitations

  • Some dense data tables and the timetable grid are difficult to navigate with a screen reader, and are being reworked.
  • Charts and analytics visualisations convey information graphically. The underlying figures are available, but not always as an equivalent accessible table.
  • Content uploaded by an institution — PDFs, videos, slide decks — is under that institution's control. We provide the checker; we cannot make an inaccessible upload accessible.
  • Third-party embedded content, such as a payment form, follows its provider's accessibility.
  • The mobile application has had less assistive-technology testing than the web portals.

Tell us about a barrier

If any part of Pallara stops you doing something, email [email protected]. Tell us the page, what you were trying to do, and what assistive technology you use if that is relevant. We acknowledge within two business days and will tell you what we can do and when.

If you are a learner, you can also raise it with your institution, who can escalate it to us directly.

For procurement

If your institution needs an accessibility conformance report or a VPAT for a procurement process, email [email protected] and tell us the deadline. We will give you an accurate statement of where we are rather than a template.