LEGAL · ACCESSIBILITY
Built to WCAG 2.2 AA. Not checked by anyone but us.
This site is built to the WCAG 2.2 AA target — keyboard-complete navigation, a visible focus outline, honored reduced-motion preferences, and full right-to-left layout for the Arabic and Hebrew locales it ships. No third-party accessibility audit has been run, so this page does not claim conformance without one. Below is what the build actually does, and the honest gap that remains.
What the build already does.
- Every page opens with a skip-to-content link as the first focusable element, and every interactive element carries a visible two-pixel focus outline that is never removed.
- Motion honors your device's reduced-motion preference: with it set, animation stops and transitions resolve instantly to their end state rather than being skipped and left broken.
- Layout is written in logical CSS properties throughout — start and end, never left and right — so the Arabic and Hebrew locales mirror the same layout instead of needing a second, separately maintained one.
What has not been checked.
Nobody outside this team has run a systematic pass with a screen reader or an automated conformance tool against the live site yet. The list above describes what the source code does; it is not a substitute for that pass, and this page will not borrow its authority.
A dedicated route for reporting an accessibility barrier is not published yet. Until it is, please treat any route named on the company page as the closest available channel, not a purpose-built one.
What is still missing.
This page depends on an accessibility conformance audit and a dedicated barrier-reporting route, and the register has no row for either — because neither has been commissioned or published yet. The mechanisms above are real and checkable in the source; a systematic third-party pass is not.
The register holds 17 live · 2 partial · 2 planned · 5 not yet.
2 of the 2 capabilities this page depends on have no row in the register yet, so this page will not print a state for them. They are named rather than dropped, because a slice that silently shortens itself is the same defect as a claim with no receipt.
- accessibility-conformance-audit
- barrier-reporting-route
The register route serves, but it carries no row for these yet. List what it does carry:
curl -s https://id.orbis.id/api/site/register | jq -r '.entries[].slug'A target you have not measured is a plan, not a claim.
Straight answers.
- Is this site accessibility certified?
- No. No third-party audit has been run, and this page will not claim conformance without one.
- Does it work with a keyboard alone?
- It is built to — skip link, visible focus, no keyboard trap by design — but that has not been verified by anyone outside this team yet. Read it as the target we build to, not a certified result.
Do not trust us. Check us.