Legal
Accessibility statement
This statement covers this website only. It is not a statement about the solutions we build for clients — those are covered separately, in the accessibility statement delivered with each one. The two make different claims and should not be read as one.
This website
It is a static site. There is no application, no login, and no interactive component beyond a contact form. That makes accessibility easier here than in most places, and it would be misleading to present it as an achievement.
What we have done
- Semantic HTML with a single
h1per page and headings in order. - Colour contrast checked against WCAG 2.2 AA for every text and interface pair in the palette.
- Visible focus indicators, never removed.
- Meaning never carried by colour alone.
- Text that reflows to 400% zoom without horizontal scrolling.
- A contact form whose errors name the field they belong to.
What we know is imperfect
This list is deliberately specific. A statement that claims no known problems is either untested or untrue.
- No independent audit. This site has been checked by us, using our own tooling and a keyboard. It has not been tested by a disabled user or by an external auditor, and those find things we do not.
- No screen-reader testing across the range. We have not tested with JAWS, NVDA and VoiceOver systematically.
- Automated checks reach a fraction of WCAG. Ours reach roughly a fifth of AA, and it is the easy fifth. Reading order, focus order, and whether a label actually means anything are not machine-checkable, and we do not pretend otherwise.
What we claim about client work — and what we do not
We build to WCAG 2.2 AA as a floor, and accessibility is gated in our build pipeline rather than reviewed at the end.
We do not claim that a solution we deliver is WCAG 2.2 AA compliant. That claim would require testing we have not done, on an app that has been built. What we claim is narrower and true: accessibility is designed in, checked automatically where a machine can check it, and everything the automation cannot reach is stated in writing with each delivery.
Where the Power Platform itself cannot meet a criterion, we say so before the price is agreed rather than after the build. Microsoft's own conformance reporting records parts of the runtime as not evaluated, and we do not fill that silence with a claim of our own.
If you are a public body
The Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations place the duty on you, not on us. Our job is to give you accurate facts, in writing, in time for your own published statement — including anything not met. We do not make, sign, or advise on a disproportionate burden assessment. That decision and its accountability are yours.
Telling us about a problem
If something on this site is difficult or impossible to use, please tell us at [email protected]. We will reply within five working days. We have no formal enforcement route to offer you — this is a private company website, not a public sector one — but we would rather know.
Who prepared this statement
Prepared by AI ORBIS CONSULTING LIMITED, registered in England & Wales, company number 17422807, registered office 5th Floor, 167-169 Great Portland Street, London, W1W 5PF.