Accessibility
Last updated 16 September 2026
Slighe is built and maintained by a single developer, and accessibility is something we care about and actively work on, not something we've had formally audited or certified. This page is a good-faith statement of where we stand, not a conformance claim.
Our standard
We aim for Level AA of the Web Content Accessibility Guidelines (WCAG) 2.1. In practice that means, among other things: labelled form fields, keyboard-operable controls and dialogs, visible focus states, sufficient color contrast, and interface elements that work with screen readers.
Known limitations
Some parts of Slighe, particularly data-heavy views like charts and the expense ledger, have not been fully tested with assistive technology, and we haven't run a full audit against every WCAG success criterion. If you hit a barrier, we would genuinely like to know about it and fix it.
Reporting an issue
If any part of Slighe is hard to use with a keyboard, screen reader or other assistive technology, tell us through the Help page. Please include the page you were on and, if you can, what technology you were using. It helps us reproduce and fix the problem.