NaazhiAccessibility
Made to be used by everyone.
We want Naazhi to work whether you use a mouse, a keyboard, a screen reader or a phone in one hand. Here is what we do, where we fall short, and how to tell us.
What we do
Built in, not bolted on.
Keyboard first
Buttons and links are real controls with visible focus, and dialogs and menus can be used without a mouse.
Screen readers
Headings, labels and landmarks describe each page, and icons that carry meaning have text alternatives.
Reduced motion
Animations stop if your device asks for less motion, and the app has its own Reduce motion setting.
Small screens
Every page is designed to work at phone width, with no sideways scrolling.
Readable text
Text is real text that scales with your browser settings, set in a clear typeface with strong contrast.
No time pressure
Nothing on these pages disappears or expires while you are reading it.
Our aim
We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2, level AA. We check new pages by keyboard and at phone width before they go live. We have not had an independent accessibility audit yet, so we do not claim full conformance.
Known gaps
- Some app screens, such as the graph view, are mainly visual and have limited alternatives.
- Screenshots on this site are pictures of the app, described in text nearby rather than in full.
- The Android and iOS apps follow each system’s accessibility features, and may differ from the website.
Found a barrier? Tell us.
Email info@setups.works with the page or screen, what you were trying to do, and the device, browser or assistive technology you use. We reply within 3 working days and tell you what we will do.
Last updated 13 November 2026.