Accessibility Statement

1.1We do not claim conformance with WCAG 2.1, WCAG 2.2 or any other standard, at any level. No accessibility audit has been carried out on Khata by us or by anyone else.

1.2Publishing a conformance claim we have not tested would tell a disabled person the product will work for them. If it then did not, they would have relied on our assurance to waste their time. We would rather describe what is actually there.

2.1On this website:

• A skip-to-content link, so keyboard users do not tab through the whole navigation on every page.
• Semantic headings, lists and landmarks rather than styled containers, so a screen reader can navigate structurally.
• Visible focus indicators on interactive elements.
• Animation is disabled when your system asks for reduced motion.
• Illustrations carry text alternatives, and decorative ones are hidden from assistive technology rather than announced as meaningless images.
• Fonts are self-hosted with size metrics reserved, so text does not move under the cursor while a page loads.
• Pages are also published as plain markdown at the same address with .md added, which some readers find easier than the rendered page.

2.2Text can be resized by your browser, and the site is built to reflow rather than to a fixed width.

3.1Stated plainly rather than omitted:

• No formal audit, and no testing with users of assistive technology.
• The mobile app has not been tested with TalkBack or VoiceOver, and we do not currently know how well it performs with either.
• Colour contrast has been designed for but not systematically measured across every state.
• The web dashboard contains dense data grids that have not been evaluated for keyboard-only use.
• Some illustrations carry meaning in their layout that the text alternative summarises rather than fully conveys.

3.2This list is what we know about. It is not a guarantee that nothing else is wrong.

4.1Write to support@lacspace.com, or use lskhata.com/contact. Tell us what you were trying to do, what assistive technology you use if any, and what happened.

4.2We treat an accessibility barrier as a bug rather than a feature request. That means it goes into the same queue as anything else that stops the product working, not into a separate list of things to consider later.

4.3If you need information from this site in another format in order to use it, ask and we will provide it.

5.1This statement is versioned. When the position changes — an audit performed, a gap closed, a new gap found — the version and date change with it, and the history below records what moved.