Accessibility Statement

The standard we build to

Policy Monster aims to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA, across the marketing site, the product, and the policy pages we host for customers.

These are also the reference standard for the Americans with Disabilities Act as applied to websites, for Section 508 of the Rehabilitation Act, and for the European Accessibility Act. We build to one standard rather than to whichever is locally enforceable.

What that means in practice

Accessibility is written into the design system as a set of rules that a component is not allowed to break, rather than as a review at the end. Specifically:

• Every interactive element is reachable and operable by keyboard, and the focus indicator is restyled but never removed.
• Colour is never the only carrier of meaning — a status shows a word or an icon as well as a colour.
• Text and interface colours are chosen to meet the AA contrast ratios, and body text is set at a comfortable size and line height rather than at the smallest size that fits.
• Each page has exactly one h1 and heading levels are never skipped, so the document outline is usable by a screen reader.
• Motion respects the prefers-reduced-motion setting; animation is reduced to nothing rather than merely shortened.
• Tap targets are at least 44 by 44 pixels.
• Form fields have real labels, errors are announced rather than only recoloured, and validation messages say what to do rather than only that something is wrong.
• Wide content such as a table scrolls inside its own region, which is itself keyboard-reachable, instead of forcing the whole page sideways.
• Pages are readable when zoomed to 200% and at 320px width, and reflow rather than requiring horizontal scrolling.

The accessibility button

Every page of this site, including the signed-in product, has an Accessibility button in the bottom-right corner. It opens a panel that changes how pages look in your browser: text size (up to 200%), line height, letter and word spacing, a readable font (Atkinson Hyperlegible), left-aligned text, high contrast, a dark theme, grayscale, highlighted links and headings, a larger cursor, a reading guide, stopped animations, and hidden images. It works with a keyboard — Tab, Enter or Space, and Escape to close.

Your choices are saved in this browser under the name policy-monster-a11yand applied before each page is drawn. That storage is not a cookie and is never sent to us. Reset in the panel, or clearing this site's data, removes it.

The button changes presentation only. It does not rewrite pages, describe images, or repair forms, and it is not how we meet the standard above — the site is built to be usable without it, and it works alongside your browser's zoom and your operating system's contrast and reduced-motion settings rather than replacing them.

It is not on the policy pages we host for customers. Those pages load no script at all (see below), so browser zoom and system settings apply to them directly.

Generated and hosted documents

Documents produced by the Service are semantic HTML — real headings, real lists, real links — with no layout tables, no images of text, and no scripts required to read them. Hosted policy pages load no third-party code at all, which removes an entire class of accessibility regression that neither we nor the customer would control.

PDF export is a rendering of the same document. We generate tagged PDFs where the renderer supports it, but PDF is a weaker format for assistive technology than HTML, and the HTML version at your hosted URL should be treated as the accessible original.

Known limitations

We are also aware that:

• Content you enter into a document — a heading you write, a link you add — is outside our control, and a document is only as accessible as the text put into it.
• The Cloudflare Turnstile challenge on sign-in is a third-party component. It is designed to be non-interactive and accessible, but we do not control its implementation. If it blocks you, email us and we will help you get in another way.
• Complex product surfaces such as the questionnaire and the rights-request queue get less assistive-technology testing than the marketing site, simply because they are newer.

Where we know about a barrier we would rather say so than let you find it. If you find one we have not listed, please tell us.

Telling us about a barrier

Email accessibility@policy.monster with the page, what you were trying to do, and the assistive technology and browser you were using if you know them.

We acknowledge within two business days and tell you what we are going to do about it. Where a fix will take time, we will offer a way to complete the task in the meantime — a person doing it for you if that is what it takes. Nobody should be unable to buy a clause or export a document because of an interface defect of ours.

If our response does not resolve the problem, say so and it will be escalated. There is no formal appeal process to navigate; there is one mailbox and a commitment to fix things.

How we assess this

We use a combination of automated checks in continuous integration, manual keyboard-only testing, and screen reader spot checks. The design system documents the rules above as non-negotiable, so a new component that breaks one is a defect rather than a trade-off. This statement is reviewed whenever the product changes materially, and was last reviewed on the date at the top of this page.