EdPayU familyFamily homeEdPayU+ — you are hereEdPayU · the school app →
Accessibility

A gate in your tender.
A requirement in our build.

S.O. 3962(E) makes accessibility conformance a condition of government procurement of software. Most vendors in this market have not noticed yet. We are building for the gate before it is enforced, not after.

In the product today

Practices, not
a settings toggle.

Operable

  • Keyboard reachability as a review requirement, not an afterthought
  • Visible focus indication throughout — no hover-only affordances
  • No flashing content; motion never carries meaning alone

Perceivable

  • Reduced-motion preference honoured — animated surfaces ship a complete static alternative
  • Screen-reader semantics: labelled controls, transcripts for animated content
  • Contrast held against WCAG targets in the design system itself

For every family

  • Regional-language parent messaging — accessibility includes language
  • Low-bandwidth tolerance: the parent app assumes 2G days happen
  • Print and PDF outputs remain readable without colour

What a tender asks for

How the accessibility conformance report is producedOne audit against the published standard produces both the human-readable and machine-readable conformance reports a tender asks for, so the two cannot disagree.One auditagainst the standardHuman-readable reportthe document a committee readsMachine-readable reportthe file a portal ingestsSame findings, same dates — one source, two shapes
The procurement gate wants a conformance report in two formats. Both are produced from the same audit, so they cannot drift apart.

The procurement fact

From 2026, government buyers must ask. We intend to be the easy answer.

S.O. 3962(E) — issued under the Rights of Persons with Disabilities Act — makes accessibility conformance a condition of government procurement of ICT, with a dual-format Accessibility Conformance Report as the evidence. For education software this changes who can sell to government and aided institutions at all: a vendor without conformance reporting is not cheaper or slower, it is ineligible. The eighteen-month compliance clock is running for the whole industry.

Our position is stated plainly: accessibility is being engineered into the platform as a requirement with the ACR as its output, and conformance documentation is prepared for tender processes on request. Where a criterion is not yet met, the report says so — an ACR that hides its gaps fails the audit that follows the tender, and we would rather lose a tender than a customer. If your procurement needs the current documentation, ask for it in the demo session and it comes with its date on it.

Tendering?

Conformance reporting, dated, with its gaps stated — the way an auditor wants it.

Chat with us