Accessibility Statement

PolicifyAI, operated by L. Bone trading as PolicifyAI, is committed to making its website and web application usable by as many people as possible, including people who use screen readers, magnification, speech recognition, keyboard-only navigation, or other assistive technology.

We treat accessibility as an ongoing obligation rather than a finished project. This statement is written to be honest about where we currently are, because a statement that overclaims helps nobody - least of all a disabled user deciding whether our product will work for them.

This statement applies to the website and web application at policifyai.com.

The Web Content Accessibility Guidelines (WCAG) define requirements for making web content more accessible. Our target is WCAG 2.2 level AA.

PolicifyAI is partially conformant with WCAG 2.2 level AA."Partially conformant" means some parts of the content do not fully conform to the standard. The specific areas we know about are listed in section 4.

We have not commissioned an independent third-party accessibility audit. Our assessment is a self-assessment, and it is therefore likely to be incomplete - there will be barriers we have not yet found. Section 7 explains how to tell us about one.

The following accessibility measures are implemented across the site today:

• Semantic structure and landmarks. Pages use semantic HTML with heading hierarchies, list markup, and landmark regions so assistive technology can navigate them.
• Accessible names. Interactive controls, icon-only buttons, and navigation regions carry explicit accessible names, and decorative graphics are hidden from assistive technology.
• Visible focus indicators. Keyboard focus is styled explicitly so the focused element is always identifiable.
• Reduced motion. Animation and transitions are suppressed for users whose system requests reduced motion.
• Language and direction. The page language and text direction are set on every page and follow the selected locale, including right-to-left languages.
• Responsive layout. The interface reflows for zoom and small viewports without requiring horizontal scrolling for body content.
• Light and dark themes, so users can pick the contrast that suits them.

We know about the following problems. We are listing them plainly rather than burying them, and we are working through them.

• No skip-to-content link. Keyboard and screen reader users must move through the full navigation on every page before reaching the main content. This fails WCAG 2.4.1 (Bypass Blocks). This is our highest priority fix.
• No independent audit. The site has not been tested by an external accessibility specialist, and has not been comprehensively tested with every major screen reader and assistive technology combination. There will be issues we have not identified.
• Complex interactive components. The policy generator wizard, the consent management platform, the cookie scanner, and the dashboard data tables are rich interactive interfaces whose keyboard operation and status announcements have not been fully verified against WCAG 2.2 AA.
• Colour contrast. Some secondary and tertiary text, placeholder text, and disabled states may not meet the 4.5:1 contrast ratio required by WCAG 1.4.3, particularly in dark theme.
• Status messages. Some asynchronous updates - generation progress, validation errors, save confirmations - may not be announced reliably to screen reader users, which can fail WCAG 4.1.3.
• Text alternatives. Some illustrative images, diagrams, and charts in marketing and blog content may lack adequate text alternatives, which can fail WCAG 1.1.1.
• Older blog and documentation content. Archived articles may contain tables, embeds, or formatting that predate our current standards.

This list will change as we fix items and discover others. We review it whenever this statement is updated.

Some parts of the experience are provided by third parties, and we do not control their accessibility. These include our payment and checkout provider, the bot-protection challenge on our forms, third-party sign-in flows, and embedded content in blog posts and documentation.

We raise accessibility problems with these providers when we find them, and we will help you complete any affected task another way - see section 8. If a third-party component is blocking you, tell us and we will find a route around it.

Documents produced by PolicifyAI are delivered as structured HTML with heading hierarchy, and as exports in other formats.

We do not guarantee that an exported document is accessible, and exported files have not been tested against WCAG. If you publish a document generated by PolicifyAI on your own website, you - not we - are responsible for its accessibility on your site, including its contrast, heading structure, and reading order once your own styling is applied.

This matters commercially as well as ethically: if you are subject to the Equality Act 2010, the Americans with Disabilities Act, the European Accessibility Act, or public sector accessibility regulations, publishing an inaccessible policy page does not discharge your obligations. Check the output on your own site.

If you encounter a barrier, or you need something from us in a different format, please tell us. Reports from users are the fastest way we find real problems.

Email: [email protected]
Or use our support page.

It helps if you can tell us:

• The page address where you hit the problem.
• What you were trying to do.
• What assistive technology, browser, and operating system you were using, if you know.

Our commitment to you: we aim to acknowledge every accessibility report within 5 business days, give you an assessment and a plan within 15 business days, and in the meantime provide the information or complete the task for you by another route at no cost.

If part of the Service is not usable for you, we will not leave you stuck behind it. Contact us and we will, free of charge:

• Provide any page or document in an alternative accessible format.
• Walk you through generating a document over email, or generate it for you from details you give us.
• Handle account, billing, and subscription changes on your behalf.
• Take a data subject request or a support request by email rather than a form.

This statement was prepared on 8 August 2026 using a self-assessment of the PolicifyAI website and web application against WCAG 2.2 level AA, carried out internally. It has not been independently reviewed.

We review this statement at least annually, and whenever we ship a significant change to the interface or resolve a listed limitation.

If you contact us about an accessibility problem and you are not satisfied with our response, you can escalate.

10.1 United Kingdom. The Equality Act 2010 requires service providers to make reasonable adjustments for disabled people. If you are unhappy with how we have responded, you can contact the Equality Advisory and Support Service (EASS).

10.2 European Union. The European Accessibility Act and its national implementations may apply to our service. You can complain to the market surveillance or enforcement authority designated in your member state.

10.3 United States. If you believe you have been discriminated against on the basis of disability, you may contact the U.S. Department of Justice Civil Rights Division.

We would much rather fix the problem than have you escalate, so please give us the chance first.

This statement is a good-faith description of the current accessibility of the Service. It is not a warranty or a contractual commitment that the Service conforms to any particular standard, and the disclaimers in our Disclaimer of Warranties apply to it.

Nothing in this statement, and nothing in our Terms of Service, excludes or limits any duty we owe you under the Equality Act 2010, the Americans with Disabilities Act, the European Accessibility Act, or equivalent legislation - those duties cannot be contracted out of, and we do not attempt to do so.