Capability
Your brand throughout. No 'powered by' anywhere.
Every button, heading and field label is renameable, because there is no hardcoded copy anywhere in the interface. Set your logo and your font, and then let each individual choose from the themes you allow, including several built specifically for accessibility.
A design baseline, applied to every theme.
Contrast minimums
Applied to every theme, not only the ones labelled accessible.
Visible keyboard focus
Every interactive element is operable and visibly focused without a mouse.
Reduced motion honoured
If the operating system asks for less movement, it gets less movement.
44 by 44 pixel targets
Minimum touch target size throughout, per WCAG 2.5.5.
Fluid typography
Scales with browser zoom rather than breaking at it.
Status by glyph as well as colour
Colour is never the only carrier of meaning.
Four clocks, and each of them is right.
Storing everything in UTC is only half the job; the screens were the other half. A tenant in Sydney reading a consent captured at 09:40 on Tuesday should not see yesterday's date with no zone named. So there is a tenant time zone, a personal time zone for each member of staff stored on their role record rather than in the session, resolution in the order person then tenant then UTC, and every rendered instant labelled with the zone it is in.
The customer portal renders in the reader's own device zone, because a data subject has no staff record to hang a setting on, and asking somebody to configure a time zone before reading their own consent history would be absurd.
- An audit instant is always UTC
- A ledger posting date uses the tenant's local day
- A campaign send resolves through the tenant's zone at scheduling time and is fixed then, so the send's idempotency key cannot move
- A booking uses the resource's own local date and zone — a global tenancy's books can legitimately contain events dated by several calendars at once
Questions about branding
How much can I actually rename?
Every label across the admin record form, the customer preference portal, the tenant login page, password sign-in and the setup-link panel. There is zero hardcoded copy, and a structural test fails the build if any is introduced. The only deliberate exceptions are the team and API-key administration screens, which are internal tooling rather than a tenant-branded surface.
Can I use my own font?
Yes — a Google font family or your own hosted file, set per tenancy. In email, a brand font can be registered from your asset library with a mandatory fallback stack and served through token-gated routes.
When do branding changes take effect?
Immediately on save, applying at the next page load across your whole tenancy.
Is the platform WCAG certified?
No, and we will not say otherwise. WCAG 2.1 AA is the design baseline applied to every theme, with the specific measures listed above. There has been no formal conformance audit, no screen-reader testing and no accessibility conformance report, so 'certified' would be untrue.
Related capabilities
We will show you the platform wearing them, including the accessibility themes your own users will thank you for leaving switched on.