Accessibility

1. Our commitment

We are working to make every part of Managrie usable by everyone, and we treat an accessibility barrier as a defect rather than a feature request. If something in our product prevents you from doing what you came to do, that is a bug and we want to know.

We will not claim to be fully conformant while we are still working on it. This page is written to be accurate rather than reassuring, because a statement that overstates where we are is worse than none: it tells you to expect something we cannot yet deliver.

2. The standard we measure against

We measure our work against the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. That is the level most commonly referenced by accessibility regulation, and it is the target we build and review against.

We are partially conformant with WCAG 2.1 AA: most of the product meets it and some parts do not yet. We are working through the gaps rather than waiting for a single moment to declare ourselves finished.

3. What we have built in

Accessibility in Managrie is a property of the interface itself rather than something layered on top of it. In practice that means:

• Skip to main content. The first thing your keyboard reaches on any page is a link straight past the navigation, so you are not tabbing through the same menu on every screen.
• Keyboard navigation. We build every control to be reachable and operable with a keyboard, with the focused element visibly marked so you can see where you are. Where we have found gaps we list them below.
• Real semantics. Buttons are buttons, headings describe structure, and form fields carry labels that assistive technology can read, so your screen reader is given something meaningful to announce.
• Errors that speak. When something you submit fails, the reason is announced rather than only shown, and your place on the page is kept so you can correct it.
• Dialogs that behave. When a dialog opens it takes focus, keeps it while open, and returns it to where you were when it closes.
• Reduced motion. If you have asked your operating system to minimise animation, we honour that: decorative movement stops and only genuine progress indicators keep moving.
• Light and dark themes built on a shared colour system, chosen for contrast rather than only for appearance.
• One shared component library. Every Managrie app draws its interface from the same components, so an accessibility fix lands everywhere at once instead of in one place and not another.

4. Known gaps

We would rather name these than let you discover them:

• Listing photos have short descriptions. A photo on a unit listing is labelled with the property and unit but not described, so it tells you less than it should about the place itself.
• Some colour combinations are still being adjusted. We have reworked our colours for contrast in both the light and dark themes, and we are still checking individual screens against that work.
• The background on our sign in pages cannot be paused. It stops if you have asked your system to minimise animation, but there is no control on the page itself yet.
• We have not completed a full external audit. Our review so far is internal, so this list describes what we have found rather than everything that exists.

This list will change as we fix things and as we find more. If you hit something that is not on it, that is exactly the report we need.

5. Why we do not use an accessibility widget

You may have seen sites with a floating accessibility button offering to change contrast or text size. We have deliberately not added one.

Those tools, usually called overlays, try to correct a page in the browser after it has loaded. Disability rights organisations including the National Federation of the Blind and the American Council of the Blind have opposed them, because they frequently interfere with the screen readers people already rely on rather than helping. In the United States, a significant share of digital accessibility complaints now name the overlay itself as the barrier.

We think a widget on top of an inaccessible page is a claim rather than a fix. We would rather spend the same effort making the underlying pages work with the assistive technology you already use and have already configured.

6. Using your own assistive technology

Managrie is built to work with the tools already on your device, which are more capable than anything we could bolt on:

• Screen readers such as VoiceOver on Mac and iPhone, TalkBack on Android, and NVDA or JAWS on Windows.
• Zoom and text size. Your browser and operating system can enlarge the page, and our layouts are built to reflow rather than break when you do.
• Dark mode and contrast settings. Managrie follows your system preference automatically, and you can also set it yourself in Settings.

7. Reporting a barrier

If any part of Managrie is difficult or impossible for you to use, please tell us at support@managrie.com.

It helps, but is not required, if you can tell us:

• The page or screen where it happened
• What you were trying to do
• The assistive technology, browser, or device you were using

We aim to acknowledge accessibility reports within two business days and to tell you what we are doing about it, including our best estimate of when. If a fix will take time, we will try to offer another way to get the same thing done in the meantime.