Accessibility statement.
Where we stand against WCAG 2.1 Level AA, including the parts we have not fixed yet.
Our commitment
Last reviewed
Storatix is used by people doing their job — renting units, chasing payments, signing leases. That work should not depend on being able to use a mouse, see fine detail, or perceive colour.
We are working to make this site and the Storatix application usable by as many people as possible, and we would rather tell you where we currently fall short than imply we have finished.
The standard we hold ourselves to
We measure this site against WCAG 2.1 Level AA. Current status: Partially conformant.
Partially conformant, in the W3C's sense of the term: most of the standard is met, but some parts are not. The specific gaps we know about are listed below.
This is a self-assessment. We have not commissioned an external audit or published a VPAT. When we do, we will say so here and date it.
What we have done
- Pages are built from semantic landmarks — a single main region, sections labelled by their headings, and one h1 per page — so screen-reader users can navigate by structure rather than reading top to bottom.
- Every section heading is programmatically associated with its section, and in-page anchors move focus to the right place rather than only scrolling the viewport.
- Interactive controls are real buttons and links, so they are reachable and operable from the keyboard without custom key handling.
- Images that carry no information are hidden from assistive technology instead of being announced as unlabelled graphics.
- Accessibility is part of code review for new marketing pages, and the test suite queries the interface by role and accessible name — a control with no accessible name fails the build rather than shipping.
Known limitations
These are real and current. We are not listing them to be thorough for its own sake — each one can block somebody, and each is on the list to fix.
JavaScript is required
The site is rendered in the browser, so it will not display at all with JavaScript disabled or blocked. This also means the initial paint depends on the script loading successfully over your connection.
Server-side rendering would resolve it and is not currently planned.
Reports and charts in the application
Inside the signed-in application, some reporting views present data as charts without an equivalent table or text summary, so the information they convey is only available visually.
Not yet reviewed against the standard. Ask us and we will get you the underlying numbers directly.
Third-party screens
Card payment is handled by Stripe and lease signing by DocuSign, on pages those companies host and control. Their accessibility is theirs to state, not ours, and we cannot fix issues there ourselves — though we will raise anything you report to us with them.
Outside our control; we will still act as your route in.
No external audit
Nothing here has been verified by an accessibility specialist or tested end to end with a screen reader by a daily screen-reader user. Our own testing catches structural problems, not every barrier.
An audit is something we will commission before claiming full conformance.
What the site expects of your browser
- A current version of Chrome, Edge, Firefox, or Safari, updated within roughly the last two years.
- JavaScript enabled, for the reason given above.
- Cookies enabled if you are signing in — the session cookie is how the application knows who you are. No cookie is used to track you across other sites.
Applicable standards and law
WCAG 2.1 Level AA is the technical baseline referenced by the Americans with Disabilities Act in US practice, by Section 508 for federal procurement, and by EN 301 549 in the EU and UK.
We are not claiming a formal legal determination of compliance under any of these. We are telling you which standard we measure against and where we currently sit against it.
Tell us when something blocks you
If any part of this site or the Storatix application stops you from doing something, we want to know — including the parts already listed above, because knowing something blocks a real person changes how we prioritise it.
[email protected]We aim to acknowledge within five business days and to tell you either when it will be fixed or, honestly, that it will not be soon.
If the thing blocking you is urgent and operational — you cannot complete a move-in, or take a payment — say so in the subject line, and we will get the task done for you while the underlying barrier is fixed.