Access arrangements are engine-level
An entitlement that only works on one platform is not an entitlement. Extra time, rest breaks and presentation arrangements are granted on the account and applied by the engine, so every shell honours them without having been told about them.
Extra time is a share of the paper
Extra time is granted as a percentage — 25% means the candidate sits 125% of the time — because that is how awarding bodies write it, and because a percentage stays correct when the paper's length is later changed. A flat number of extra seconds can be added on top; the percentage is floored to a whole second first, so the result cannot depend on the order the two were granted in.
It is applied by returning a longer session configuration, not by patching a timer. The consequence is that the countdown, the expiry, resuming on a different device and the replayed event log all honour it for free — and the arithmetic is integer, so two devices compute the same deadline to the second. That last property is what makes a contested deadline reproducible at appeal.
Rest breaks stop the clock
Supervised rest breaks are stopped-clock time, not extra time: the exam clock pauses, so none of the break can be spent answering. The allowance remaining is derived from the pause and resume events already in the log — wall-clock time minus working time — rather than tallied in a second counter that could disagree with the first. It survives a resume on another device for the same reason.
Presentation
- Text size — the whole layout scales, not just the letters, so padding, line height and the on-screen keyboard's caps move with it.
- High contrast — a fourth palette, not a filter. A filter would flatten the distinction between a correct and an incorrect answer, which is the one distinction on the screen that must survive.
- Reduced motion — transitions and animated feedback are suppressed.
- Screen-reader layout — each question is presented as one linear document in reading order, rather than a card that repaints underneath the reader's cursor.
On Android, text size is deliberately not re-implemented: the system font scale is already honoured, and a candidate who has set their phone up to be readable should not have to say so again inside one app.
Granted once, on the account
Arrangements are stored as ordinary settings rows, so they sync to every device the candidate signs in on, and nobody re-enters "25% extra time" per exam — or forgets to. They resolve against the person and the device only, never the pack: authoring an exam must not be able to withdraw what a candidate is owed. For the same reason the phone shows them read-only.
Accessibility statement
Zayeed's interfaces are built to WCAG 2.2 AA as a target: semantic structure, visible focus, keyboard operability throughout, contrast tokens chosen against measured ratios rather than by eye, and no reliance on colour alone to convey a mark.
A full independent WCAG 2.2 AA audit has not yet been carried out. That is stated here rather than implied away, and it is on the plan. If you rely on an assistive technology and something is in your way, tell us — that is worth more to this page than an audit certificate.
Still deciding?
The fastest way to judge a marker is to try to break it. Run a paper, answer it badly on purpose, and read the reason next to every mark.