Accessibility statement
PROVISIONAL TEXT
- This text was written by the engineering team to describe what the site does at this revision. It has not been reviewed by counsel — that review is an open decision (D-105) — and it is not legal advice.
- A fact the owner still has to supply is marked [owner to confirm]. Where you see it, nobody has decided yet, and nothing has been invented to fill the gap.
- This document is available in English only until its translation has been reviewed.
- Revision 2026-09-24.1, issued 24 September 2026.
WHAT THIS STATEMENT COVERS
- This statement applies to the public SiaSol site — every page under this address, including the catalogue and the legal set.
- It does not cover the staff console, which is a separate application behind a sign-in. It does not cover a demonstration of an application either: a demo’s own accessibility is the application’s, stated with it where it is offered.
THE TARGET
- This site aims to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. That means, among other things: everything works from a keyboard, focus is always visible, pages have a clear heading structure and landmarks, text can be enlarged to 200% and reflowed to a narrow screen without sideways scrolling, colour is never the only carrier of meaning, and motion respects the reduced-motion setting of your system.
CONFORMANCE STATUS
- No conformance claim is made at this revision.
- Conformance with WCAG is decided by evaluating every page against every success criterion, much of which a machine cannot judge — whether alternative text is useful, whether an error message is helpful, whether a reading order makes sense. That evaluation has not been done here, so this site is described as aiming at WCAG 2.2 AA rather than as meeting it.
WHAT HAS BEEN MEASURED: NOTHING, AT THIS REVISION
- An earlier version of this statement listed a suite of automated checks that ran before every release and blocked it on failure: axe-core scans across eight kinds of page, keyboard checks, a 320-pixel reflow check, a reduced-motion check, a heading-structure check.
- That suite was deleted in September 2026 when this site was rebuilt as a baked three-dimensional world and the application it belonged to was removed. The release pipeline still runs those checks — against the staff console, which is a different application. No automated accessibility check runs against this site today.
- This is stated rather than left out because the absence is the single most important fact on this page, and because a statement citing measurements that no longer happen is worse than a statement admitting there are none.
- The date by which automated checks are restored for this site: [owner to confirm].
KNOWN LIMITATIONS
- These are known gaps rather than known failures: nobody has looked, so nobody can say they are fine.
- No manual audit. No accessibility specialist has evaluated this site, and no page has been tested against WCAG 2.2 criterion by criterion.
- The date and scope of the first manual audit: [owner to confirm].
- No testing with assistive technology. The site has not been used end to end with a screen reader, magnification, speech input or a switch device by anyone who relies on one.
- The home page is a real-time three-dimensional scene, and it is the main way into the catalogue. It is navigated by dragging, scrolling and clicking points in a rendered world. Whether every destination reachable by pointing in that world is also reachable from a keyboard has not been verified, and the honest position is that some may not be. Every application in the catalogue is also reachable as an ordinary list at /applications, which is the route to use if the world does not work for you.
- That scene’s motion has not been assessed for whether it is uncomfortable for a viewer with a vestibular disorder who has not set a reduced-motion preference, and whether it honours that preference at all has not been re-verified since the rebuild.
- Criteria a mechanical check cannot reach. Among others: whether link text makes sense out of context, whether the reading and focus order match the visual order on every page, and whether any instruction depends on shape, size or position.
- Two languages, unevenly. The legal set — this statement included — is published in English only until its translation has been reviewed.
REPORTING A BARRIER
- If something on this site is hard or impossible for you to use, please say so: write to support@siasol.ai. Reports are read by the people who build the site, and a report about accessibility is treated as a defect report, not as feedback.
- It helps to include, as far as you can: the address of the page and what you were trying to do; what happened instead, and where you got stuck; the browser and any assistive technology you were using, with versions if you know them.
- No telephone number is published, because none has been supplied, and inventing one would mean reports going nowhere.
- The response time for accessibility reports, and any formal complaint or enforcement route the applicable law provides: [owner to confirm].
HOW THIS STATEMENT WAS PREPARED
- Written by the engineering team that builds the site, from what that team could verify about it on 24 September 2026. It was not prepared by an external evaluator.
- It is reviewed whenever what it describes changes — a statement that outlives what it describes is worse than none.