Accessibility Statement

1. Our Commitment

ProPolicyForge is committed to making its website and platform accessible to the widest possible audience, including people with disabilities. We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA as our target standard.

This statement applies to the ProPolicyForge website and platform at propolicyforge.com and propolicyforge.co.uk.

2. Compliance Status

ProPolicyForge is partially compliant with WCAG 2.1 Level AA. We have implemented the following accessibility features:

Responsive design — the platform is fully responsive and usable on mobile, tablet and desktop devices. Colour contrast — text and background colour combinations have been selected to meet or exceed WCAG 2.1 AA contrast ratio requirements of 4.5:1 for normal text. Font sizing — base font sizes are set using relative units to respect user browser font size preferences. Keyboard navigation — core platform functions are accessible via keyboard navigation. Alternative text — images include descriptive alternative text. Focus indicators — interactive elements display visible focus indicators.

We have not yet conducted a formal independent WCAG 2.1 audit of the full platform. This is planned as part of our ongoing accessibility improvement programme.

3. Known Limitations

We are aware of the following accessibility limitations and are working to address them:

Document preview modal — the full-screen document preview panel has limited keyboard navigation support in some browsers. PDF download — generated PDF documents may not be fully accessible to screen readers. We recommend downloading the Word (.docx) version for the best accessibility experience with assistive technologies. Complex data tables — some comparison tables on the pricing page may not be fully optimised for screen reader navigation.

We are actively working to address these limitations. If you encounter an accessibility barrier not listed here, please contact us.

4. Technical Specifications

ProPolicyForge relies on the following technologies for accessibility:

HTML5, CSS3, JavaScript (React/Next.js). ARIA landmarks and labels are used where appropriate to improve screen reader navigation.

The platform has been tested on the following combinations:

Chrome and Edge on Windows 10 and 11. Safari on macOS. Chrome and Safari on iOS. Chrome on Android.

We have not yet conducted formal testing with screen readers including JAWS, NVDA or VoiceOver. This is planned as part of our accessibility improvement programme.

5. How to Request Accessible Content

If you need information from ProPolicyForge in an alternative format — for example, large print, audio or a different file format — please contact us at support@propolicyforge.com. We will respond within 10 working days to discuss how we can best assist you.

If you are a user with a disability who needs support using the platform, please contact us and we will do our best to assist you directly.

6. Reporting Accessibility Issues

We welcome feedback on the accessibility of ProPolicyForge. If you experience any accessibility barriers, please contact us:

Email: support@propolicyforge.com Subject line: Accessibility Issue

Please include a description of the accessibility barrier, the page or feature affected, the assistive technology or browser you are using, and your contact details so we can respond.

We aim to acknowledge all accessibility reports within 5 working days and to provide a response or resolution within 20 working days.

7. Enforcement

If you are not satisfied with our response to an accessibility complaint, you may contact the Equality and Human Rights Commission (EHRC) at equalityhumanrights.com, or in Northern Ireland, the Equality Commission for Northern Ireland at equalityni.org.

8. Review

This accessibility statement was prepared on 29 April 2026. It will be reviewed annually and updated to reflect changes to the platform and improvements to our accessibility provision.

ProPolicyForge is committed to ongoing accessibility improvement. As a sole trader operation, we are working to systematically address known limitations as part of each development cycle.