Last updated 1 August 2026
This statement sets out how accessible the Seisin application and this website currently are, measured against the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA, and what is known not to meet that standard yet. It is written to be useful rather than reassuring, so the limitations are stated as plainly as the commitments.
Seisin is partially conformant with WCAG 2.2 Level AA. Partially conformant means that most of the standard is met, but some parts of the product are not yet, and those parts are named below. This assessment is a self-assessment carried out by the developer. It has not been audited by a third party, and we would rather say so than imply a certification we do not hold.
Text and interface colours are chosen for contrast, and the application derives a readable text colour automatically against whichever accent colour you pick, so a custom accent cannot produce unreadable text. Light, dark and midnight themes let you choose a comfortable contrast level. The interface honours your operating system's "reduce motion" setting and suppresses animation when it is set. The website uses semantic HTML, works with browser zoom, and adapts to small screens.
On this website, the stage list running down the side of the home page is ordinary navigation: every entry is a link, reachable by keyboard, and the one you are currently reading is marked for screen readers rather than by colour alone. The screenshots enlarge on click, and that view can be closed with the Escape key or the close button, with keyboard focus kept inside it while it is open and returned to the screenshot you came from when it closes. If you have asked your system to reduce motion, the page stops animating and jumps straight to each section instead.
The data-dense charts on the Analytics page and the interactive application map are not yet fully usable with a screen reader, and some of their content is conveyed visually without an equivalent text alternative. Keyboard-only navigation works throughout the main interface but is not yet complete in those same two areas. The reason is straightforward: they are the newest and most complex parts of the application and the accessibility work on them is not finished. It is planned, not abandoned.
If you encounter an accessibility barrier in Seisin, please report it to [email protected], or open an issue on GitHub. Please describe what you were trying to do and what assistive technology you were using, as that is usually enough to reproduce the problem. We aim to acknowledge reports within five working days.
If you are not satisfied with our response, you may raise the matter with the accessibility enforcement body in your country. Within the European Union, each member state designates its own authority under the European Accessibility Act.