Signature Tool Create a signature

Accessibility statement

This statement applies to Signature Tool at https://signature-tool.mashreeves.com/.

We want as many people as possible to be able to use this service. That means you should be able to:

  • use the whole service with a keyboard alone
  • see clearly where the keyboard focus is at all times
  • read every piece of text at the contrast levels the standard requires
  • use it with a screen reader

How accessible this service is

This service is partially compliant with the Web Content Accessibility Guidelines version 2.2 AA standard, because of the issues listed below.

Non-accessible content

Known barriers

  • The live signature preview puts a lot of links in the keyboard path. The preview shows your signature as it will appear, and the links inside it — website, social icons and so on — are all reachable by keyboard even though the preview is there to be looked at rather than used. Tabbing past it takes around twenty presses. We have added a "Skip to main content" link, and we are looking at taking the preview's contents out of the keyboard path without breaking the select-and-copy fallback that some people rely on. This does not clearly fail a single success criterion, and we are listing it rather than arguing about scope.
  • Parts of the service have not been tested. Everything behind sign-in — the administration area for managing templates, banners and users — has not been assessed yet. We are not claiming it is accessible or that it is not.

Not yet assessed

  • Screen reader use. We have not run the service through a screen reader. We have checked the things a screen reader depends on — every control has a name, headings are in order, the page has landmarks, images have text alternatives, tables have captions and proper headers — but that is not the same as listening to it.
  • Resizing and reflow. We have not confirmed the service works at 400% zoom or at a 320-pixel-wide window, which the standard requires under 1.4.10 (Reflow) and 1.4.4 (Resize Text). The layout is built to adapt, but built to and confirmed to are different things.

Reporting an accessibility problem

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

Enforcement procedure

The Equality and Human Rights Commission (EHRC) enforces the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018. If you are unhappy with how we respond to your complaint, contact the Equality Advisory and Support Service (EASS).

What we are doing to improve accessibility

The service is built to WCAG 2.2 AA as a floor rather than assessed against it afterwards: semantic HTML before ARIA, a visible keyboard focus indicator, and no use of colour as the only way of conveying meaning. The help panel is a standard dialog pattern so that it can be opened by keyboard, closed with Escape, and returns focus to the button that opened it.

The two items under "not yet assessed" above are the next work, and this statement will be updated with what they find rather than quietly dropped.

How we tested this service

Tested in August 2026 by the development team, covering the public part of the service: the signature builder, the sign-in and password reset screens, and this notice and the privacy notice.

The testing was:

  • Keyboard only — tabbing the whole of the builder, checking focus was visible at every stop, that focus order followed the visible order, that nothing trapped focus, and that the help panel opened, closed on Escape and returned focus correctly.
  • Automated checks in the browser for the mechanical failures — missing accessible names, missing alternative text, heading order, landmarks, duplicate identifiers, ARIA attributes pointing at elements that do not exist, and text contrast measured against computed background colours.

Automated checking finds roughly a third of accessibility problems and cannot tell whether something makes sense, so we treat it as a floor rather than a pass. It also produced several false alarms here — text on a gradient background, which it could not measure — which were checked by hand and were fine.

Preparation of this statement

This statement was prepared on 31 August 2026.
It was last reviewed on 31 August 2026.
The service was last tested on 31 August 2026.

Help

Common questions

For step-by-step instructions, see the user guide.

My signature looks wrong in Outlook

Outlook renders HTML with Word, not a browser engine, so it ignores a lot of modern CSS. If a signature looks right here and wrong there, the cause is almost always spacing or layout that relies on CSS the Word engine does not support. Tell whoever maintains the template rather than editing the pasted copy - a fix in the template fixes it for everyone.

Do I need an account?

Not to create a signature - the builder is open to anyone unless your organisation has turned that off. Accounts exist for administering templates, banners and users.

Is what I type saved anywhere?

No. Your name, job title and contact details are used to render the signature and are not stored. Regenerating it later means filling the form in again.

How do I paste it into my mail client?

Use "Copy signature", then paste into your mail client's own signature setting - Outlook: File › Options › Mail › Signatures. Gmail: Settings › See all settings › Signature. Apple Mail: Settings › Signatures. If pasting loses the formatting, use "Download .htm" and import the file instead.