Accessibility Statement

Summary

Pherox is built for tradespeople working in real conditions: bright sunlight on a rooftop, cold hands in a van at 7am, cracked screens, gloves. Accessibility matters for that audience and for everyone who uses the service.

We aim for WCAG 2.2 Level AA across our websites, the Pherox app, and the customer-facing PDFs we generate. We are not perfect, and we have not yet completed a formal accessibility audit. We have listed known limitations below and we will fix issues as we find them.

If something on Pherox does not work for you because of an accessibility barrier, please tell us at [email protected]. We will acknowledge your message within 5 business days and work to fix material issues without unreasonable delay.

1. Our commitment

We believe Pherox should work for every tradesperson, on the device they use, in the conditions they work in, regardless of disability or assistive technology in use.

We are committed to:

• Aiming for WCAG 2.2 Level AA conformance across the parts of Pherox you interact with
• Fixing accessibility issues when they are reported to us, without unreasonable delay
• Naming what does not work so people know what to expect
• Improving the product steadily rather than claiming perfection we have not yet earned

2. What this statement covers

This statement applies to:

• The Pherox marketing website at pherox.co.uk
• The Pherox application at app.pherox.co.uk
• PDF quotes and Bills of Quantities that Pherox generates and that the trade user sends to their customer

It does not cover:

• Third-party content embedded in our pages (for example videos hosted elsewhere, embedded analytics dashboards)
• The Stripe billing pages we redirect to for payment
• Email clients displaying our transactional emails (we do our part on the email side; how your inbox renders it is outside our control)

3. The standard we aim for

We aim for the Web Content Accessibility Guidelines (WCAG) version 2.2, Level AA.

WCAG 2.2 AA covers things like:

• Sufficient contrast between text and background
• Resizable text without loss of meaning
• Keyboard-only navigation through the application
• Clear focus indicators
• Compatibility with screen readers and other assistive technology
• Captions and transcripts for any video or audio content
• No reliance on colour alone to convey meaning
• Generous tap targets on mobile

We do not currently target WCAG AAA, the higher conformance level, because the cost-benefit trade-off for a launch-stage product does not justify it. We will reconsider as the product matures.

4. Where we are now

We are honest with you about this:

• We have not yet completed a formal independent accessibility audit. We plan to commission one within 6 months of launch.
• We have built the product with accessibility in mind, but we have not had every screen and flow tested with assistive technology by users who depend on it.
• We are a small team. Some issues may exist that we have not yet identified.

We are publishing this statement on day one so that people know what to expect, what to report, and how we will respond.

5. Known limitations

We will keep this list current. As we discover issues, we add them here; as we fix them, we move them to the changelog at the bottom of this page.

At launch, we know the following:

• No accessibility-focused user testing has been completed yet. This is a process gap, not a specific bug, but it means some issues may exist that we have not surfaced.
• PDF quotes: the PDFs we generate use real (selectable, copyable, screen-reader-readable) text, not flattened images. We have not yet tagged the PDFs with full structural metadata (headings, table semantics) that some screen readers use to navigate. We plan to add structural tagging within 3 months of launch.

If you find an issue not on this list, please tell us. We are not pretending to know what we have not tested.

6. Mobile-first design and accessibility

Pherox is built mobile-first because that is where tradespeople work. In practice this overlaps significantly with accessibility:

• Tap targets are sized for gloved fingers (44 pixel minimum, per WCAG 2.2 success criterion 2.5.8)
• Type sizes are generous; users can zoom in browser without breaking the layout
• Magic-link authentication removes the need to remember a password, which helps users with memory or motor difficulties
• The interface uses high-contrast text on light-mode and dark-mode equivalents

These are good baselines. They are not a substitute for testing with users who use assistive technology, and we do not claim that mobile-first design alone equals accessibility.

7. The customer-facing PDFs

When you generate a PDF in Pherox and send it to your customer, that PDF is read by a homeowner who may also have accessibility needs.

Our PDFs:

• Use real text (selectable, copyable, screen-reader-readable)
• Do not embed important content as images
• Use sufficient contrast between text and background
• Keep type sizes reasonable for print and screen
• Maintain consistent structure across documents

The structural tagging gap (see section 5) applies here. We plan to address it within 3 months of launch.

If your customer reports an accessibility issue with a Pherox-generated PDF, tell us at [email protected] and we will help.

8. How to report an accessibility issue

If something on Pherox does not work for you (or for your customer) because of an accessibility barrier, email [email protected] with "Accessibility" at the start of the subject line.

Tell us:

• What you were trying to do
• What happened (and what you expected)
• The page or screen where it happened
• The device, browser, and any assistive technology you were using
• (Optional) a screenshot or screen recording

You do not need to know technical terminology. "I could not get past the sign-in screen using my screen reader on iPhone" is more useful to us than a detailed WCAG citation.

9. What we will do when you report an issue

When you report an accessibility issue:

1. We acknowledge your message within 5 business days.
2. We assess whether the issue affects WCAG 2.2 AA conformance, the practical usability of the product, or both.
3. For issues that materially block a user from completing a task, we work on a fix as a priority.
4. For issues that are surface-level (visual polish, minor inconveniences), we add them to our backlog and address them in a reasonable timeframe.
5. We tell you what we have decided, and (where possible) when you can expect a fix.
6. When the fix ships, we update this statement to remove the issue from the "Known limitations" list.

If we decide we cannot fix something, we tell you why, and we suggest an alternative way to achieve what you were trying to do.

10. Compliance and legal context

This statement is voluntary. Pherox is a private-sector service, so we are not subject to the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018, which apply only to public sector bodies.

However:

• The Equality Act 2010 requires service providers (including SaaS) to make "reasonable adjustments" so that disabled people are not placed at substantial disadvantage. We take this seriously and treat it as the floor, not the ceiling.
• WCAG 2.2 AA is the widely accepted technical benchmark for what "reasonable adjustments" looks like in practice for a website or app.

If you believe Pherox has failed to make a reasonable adjustment for you, please contact us first (see section 8) so we have a chance to put it right. If you remain dissatisfied, you can contact the Equality Advisory and Support Service at equalityadvisoryservice.com or 0808 800 0082.

11. Reviews and continuous improvement

We review this statement at least every 12 months, and earlier if:

• We commission a formal accessibility audit (planned within 6 months of launch)
• We ship a significant new feature
• A user report uncovers an issue that affects multiple users
• A change in law or guidance requires it

Each revision is dated in the changelog below.

12. Changelog

6 June 2026: First published.

13. How to contact us

Accessibility issues: [email protected] (subject "Accessibility")

General questions: [email protected]

Post: Pherox Technologies Ltd, 195 Manchester Road, London E14 3DR

For independent advice on disability and accessibility matters: Equality Advisory and Support Service (equalityadvisoryservice.com / 0808 800 0082)