Accessibility

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. We have not completed a formal third-party audit or published a conformance statement, so we describe this as our target rather than a certified result. When we complete an audit, we will publish what it found here, including the failures.

Accessibility is treated as part of building a feature, not a later cleanup pass. Where we fall short, we would rather hear about it and fix it than leave it undocumented.

• Keyboard navigation. Interactive controls are reachable and operable by keyboard, with visible focus indicators. Dialogs trap focus and close on Escape.
• Screen reader support. Semantic HTML, labelled buttons and inputs, accessible names on icon-only controls, and headings that reflect the actual structure of each page.
• Colour and contrast. Body text and interface colours are chosen against the WCAG AA contrast targets in both light and dark themes. Colour is not used as the only way to convey meaning — status and severity carry text labels too.
• Light, dark and system themes. Including respecting your operating system preference, which matters for light sensitivity and for low-light reading.
• Reduced motion. Animation is subtle by default, and we honour the system "reduce motion" preference.
• Text and zoom. Layouts use relative units so browser zoom and larger system text sizes reflow rather than clip.
• Mobile and touch. Mobile-first layouts with touch targets sized for real thumbs, and no horizontal scrolling traps.
• Alternatives to precise input. You can describe a location in words instead of placing a precise map pin, and file a report without using the camera.
• Low bandwidth. Images are served at appropriate sizes, content loads progressively, and the installed app keeps working when the connection drops.

Being straight about the current state:

• The map. An interactive map is inherently visual. Map content is also available as a list of nearby reports, but the map itself is not yet fully usable by screen reader alone.
• User-supplied media. We cannot guarantee that photos and videos posted by other people carry descriptive alternative text. We are working on prompting authors to describe their images.
• No formal audit yet. Our AA claim is a target validated by internal testing, not by an independent assessor.
• Translation coverage. Interface language coverage is still expanding, and community content appears in the language it was written in.

If any part of Xamseen is difficult or impossible for you to use, tell us — it is the fastest way for it to get fixed. Contact [to be provided before launch: general support and accessibility contact address].

Helpful details: the page or feature, what you were trying to do, and the device, browser and assistive technology you were using. We treat accessibility barriers as defects and prioritise them accordingly, and we will tell you what we plan to do about the specific issue you raised.