Core USPWCAG 2.2 AA · Section 508

Accessibility is not a setting.
It is enforced like security.

In most platforms accessibility is a best-effort afterthought. In Amzaa it sits at the same level as authentication and tenant isolation. Where a tenant's regulatory profile requires it, whether that is a federal agency, a public body, or anyone whose obligations say so, the standard is locked on from the backend and nobody in that tenant can switch it off, not even an administrator under deadline. Every other tenant gets the same engine with the controls available to enable. It is in the foundation, not the backlog.

Why it belongs in the foundation

The same level as JWT and row-level security.

Accessibility that lives in the interface can be skipped, forgotten, or turned off under deadline, which is exactly when it matters. Amzaa moves the decision out of the interface: when a tenant's obligations require a standard, it is enforced from the backend and the tenant has no switch for it, the same way it has no switch for data isolation. Where it is not required, it remains available rather than absent.

Fourteen accessibility standards are supported, platform-base and country-specific, derived automatically per tenant from where they operate.

If it can be switched off under pressure, it is not a guarantee. So this one cannot.

Enforced, not optional
WCAG 2.2 AAevery tenant, cannot disable
Section 508forced on for federal
EN 301 549European public sector
ADA · AODA · EAAUS, Canada, EU
14 standardsauto-derived per tenant
Accessibility you can switch off under a deadline
is not accessibility.
What it unlocks

It opens the doors procurement closes.

Federal, without a retrofit

Section 508 is a hard requirement to sell to government. For a federal tenant it is locked on from the backend rather than set in the interface, so nobody inside the tenant can switch it off and the box is ticked before the procurement question is asked.

Legal risk, lowered

Accessibility lawsuits target enterprises whose software excludes users. Building the standard into the platform rather than leaving it to each screen removes a class of exposure that most GRC tools quietly carry.

Per-user, not one-size

Each user carries their own accessibility preferences, including how they receive notifications, so the platform adapts to the person, not the other way round.

Design partner programme

Bring us the question your regulator is going to ask.

A small cohort across banking, fintech, insurance, healthcare, technology, private equity and the public sector. Early access, real influence, pricing that holds.

We are pre-launch and we will not dress it up. There are no logos on this page because there are none to show. Come and try to break the chain.