Accessibility statement

What this covers

This statement covers the Mendlet website (this site, mendlet.com), the office app, the tenant portal, the contractor portal and the operator console. It is run by Mendlet Ltd.

We want everyone who uses Mendlet to be able to use it — including tenants reporting a repair at home, contractors on site with one hand free, and office staff who use a screen reader, magnification or only a keyboard. Our aim is that you can:

• zoom to 200% without the text spilling off the screen;
• use every part of the website with a keyboard alone, and see where you are;
• use the tenant portal in English or 21 other languages, including right-to-left ones;
• use the website with the text at the size your device is set to.

How accessible it is

Our target is the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. Mendlet partially meets that target: most of it does, and the parts that do not yet are listed below. We check new work against it, and our test suite opens the pages in a real browser to check contrast, sideways scrolling on a phone and a visible keyboard focus.

What we know is not right yet

These come from our own review of the apps. We are working through them, and this list is updated when each one is fixed.

• Moving a map pin. In the office app, the pin on the Google map is placed by dragging it, which needs a pointer. The address fields beside the map are the keyboard alternative: an address saved without a pin still gives the contractor directions. (WCAG 2.5.7)
• The map itself. The small maps in the office app and the contractor portal are Google’s own embedded map, and how well it works with a screen reader is up to Google. The address is always written out in words beside it.
• PDF documents. The job sheets and reports Mendlet creates as PDF files are not yet tagged for screen readers. The same information is on screen in the apps. (WCAG 1.3.1)
• Outside audit. The fixes above were checked by our own review and our automated browser tests, not yet by an outside specialist, so there may be problems we have not found.
• Calendar chips. On the office calendar on a touch screen, the individual job chips are smaller than 44 by 44 pixels; the whole day cell, which opens the same jobs, is the larger target. (WCAG 2.5.8)
• Rows that open a job. In the office app, a job’s row in the Jobs list, its card on the Board and a day on the calendar each open when pressed, and also hold buttons of their own. A screen reader may announce the row as one button and then the buttons inside it. Everything the row offers is also on the job’s own screen. (WCAG 4.1.2)

The website itself (the pages you are reading) has no known failures against the target. If you find one, please tell us.

Reporting a problem

If something on Mendlet is hard or impossible for you to use, or you need information from it in a different format, please tell us. Email info@mendlet.com or use the contact form, and say which page or screen it was, what you were trying to do and, if you can, the device and any assistive technology you use. We usually reply the same working day.

If you are a tenant or a contractor and the problem is about a repair rather than the software, contact your landlord, managing agent or the company that sent you the job: we make the software they use, and we cannot book or change work ourselves. We will still fix anything about the portal itself.

If you are not happy with our reply

We are a private company rather than a public sector body, so the Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018 do not apply to Mendlet. The Equality Act 2010 does. If you are not satisfied with how we respond, you can contact the Equality Advisory and Support Service (EASS).

Preparation of this statement

This statement was prepared on 2 October 2026. It is based on our own review of the interface of the website and the apps (September 2026), in a desktop browser and at phone width, with the operating system in both light and dark mode; on an automated accessibility check (axe-core) of every website page and every screen of the apps (2 October 2026); and on the automated browser checks in our test suite. It has not yet been audited by an outside specialist. It will be reviewed whenever the list above changes, and at least once a year.