Accessibility Statement

1. What Warsha aims for

Warsha aims to be usable by people who use a screen reader, need larger text, need higher contrast, or cannot use precise touch gestures.

This statement says what has been done and what has been checked. It distinguishes between the two, because a claim of accessibility that has not been tested with the people concerned is not worth much.

2. What is built in

Text scales with the system text-size setting.

Light, dark and follow-the-system appearance, with colour contrast checked across every role in both themes by an automated gate that runs on every change.

Screen headings are marked as headings, so a screen reader can navigate by them.

Interactive elements carry accessible labels and meet a minimum touch target size.

Full right-to-left support for Arabic, including layout direction, not only translated text.

Colour is never the only way information is conveyed.

3. What has been verified

Automated checks run on every change: colour contrast across all interface roles in both themes, and interface completeness in both languages.

These catch a real class of problems. They do not establish that the application is usable with a screen reader, which requires testing with a screen reader.

4. What has not been verified

No testing with assistive technology on a physical device has been carried out for this version. No conformance with WCAG or any other standard is claimed, at any level.

This is a gap, and it is stated as one. Warsha would rather record an untested area than publish a conformance claim it cannot support.

5. Telling us about a problem

If something is unusable for you, report it through the Help Centre or the Legal Contact route. Say what you were trying to do and what technology you were using.

Accessibility reports are treated as defects, not as feature requests.