Accessibility statement

Prepared 7 October 2026. Last updated 18 October 2026.

This statement applies to Marketool at marketool.mashreeves.com.

I want as many people as possible to be able to use it. You should be able to:

sign in, make a banner and schedule a post using a keyboard alone
move and zoom a photo inside a banner with the arrow keys and the plus and minus keys
zoom the page without losing content, and turn off animation through your device's "reduce motion" setting
use the light or dark theme

How accessible this service is

Marketool is partially compliant with the Web Content Accessibility Guidelines version 2.2, level AA, because of the issues below. It hasn't yet had a full test against the guidelines, so there may be problems not listed here.

Known issues

The slideshow videos Marketool makes have no captions or text transcript. The text in a video is drawn onto the pictures, and the music is not described. This fails WCAG 1.2.1 (audio-only and video-only content). The same listing details are shown as text on the page next to the video.
Passkey sign-in hasn't been tested with a screen reader or with a real device from start to finish.

I haven't set dates for fixing these yet. This statement will be updated with dates when I do.

What you make with it

Banners are exported as images, and your agency chooses its own colours. When you post a banner, add a text description (alt text) where the platform allows it, and check that the text on your colours is easy to read. Marketool doesn't yet suggest alt text or warn about low-contrast brand colours.

Reporting an accessibility problem

If you find a problem that isn't listed here, or you need something in a different format, email hello@mashreeves.com. I aim to reply within five working days and will tell you what I can do and by when.

Enforcement procedure

Marketool is run by an individual, so it isn't covered by the Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018, and the Equality and Human Rights Commission doesn't enforce a complaint about it. What does apply is the Equality Act 2010 duty to make reasonable adjustments for disabled people. If you're unhappy with my reply, the Equality Advisory and Support Service (EASS) can advise you on your rights.

What I'm doing to improve accessibility

Marketool is built to WCAG 2.2 AA: proper headings and landmarks, labelled form fields, visible keyboard focus, a skip link on every page, messages announced to screen readers, and text colours measured to at least 4.5:1 in the light and dark themes. A high-contrast theme (Theme menu, High contrast) aims at 7:1 for text, and "System" follows your device's dark-mode and increased-contrast settings. You can also choose the font (Appearance, in the account menu): the default pairing, Inter, or your device's own.

How I tested this service

On 7 October 2026 I tested the sign-in page, the demo, the banner builder, the posting schedule, the staff and settings pages, and every public page, in Chrome at 375, 768 and 1280 pixels wide in the light and dark themes. The test used the keyboard only, with automated checks of text contrast, target size, headings, landmarks and page titles. Problems found then were fixed before this statement was published.

While building the service in September and October 2026 I also checked keyboard use of the banner builder's photo controls and measured every text and control colour in both themes.

On 18 October 2026 I checked the Music settings page and a video's "Post it" panel in Chrome at 375 and 768 pixels wide: no sideways scrolling, every field labelled, and no control below the minimum target size apart from inline text links. The same day, page changes started moving keyboard focus to the main content and announcing the new page title to screen readers.

There hasn't yet been a test with a screen reader, an automated axe scan, a check at 200% browser zoom, or a check in Windows high contrast mode. The video wizard wasn't part of either test.

Preparation of this statement

This statement was prepared on 7 October 2026 and last reviewed on 18 October 2026. The service was last tested on 18 October 2026 (the pages above).