Accessibility

What we are aiming for

We are working towards WCAG 2.2 Level AA. We have not been independently audited, so we describe this as a target we are building against rather than a certification we hold.

What has actually been tested

axe-core 4.10 was run against every page of this site and all four demo platforms, at WCAG 2.0, 2.1 and 2.2 level A and AA. Every one of them reports zero violations. That covers the homepage, /book, /contact, /privacy, /cookies, /accessibility, /data-request, /refunds, the 404, Ledgerly, Coverly, CrewFlow, the CrewFlow client portal and CounselCore.

Lighthouse was run on the marketing pages at mobile size and reports an accessibility score of 100 on each.

Both were run on 20 September 2026. Neither is a substitute for a person; see the section below.

What is in place

Body text meets a 4.5:1 contrast ratio and large text 3:1, measured against the surface actually behind it rather than against the page colour. The homepage changes colour as you scroll: modelled across 200 points of that transition, the worst case for both body and muted text is 4.52:1.

A skip-to-content link is the first item in the tab order on every page, and it moves focus to the main content rather than only scrolling to it.

Every focus indicator is measured against its own background and clears 3:1 — 4.62:1 on the marketing pages, and between 4.09:1 and 8.9:1 inside the demo platforms, each of which has its own palette.

Interactive elements are reachable by keyboard, including the clickable table rows, cards and chart columns inside the demos, which are not buttons and needed a tab stop, a name and Enter/Space adding by hand.

The date and time pickers on the booking page use arrow keys, Home and End inside each group, so choosing a slot is one tab stop rather than twenty-three.

The assistant panel is a modal dialog on a phone: Escape closes it, Tab stays inside it, and focus returns to the button that opened it.

Touch targets are at least 44 by 44 pixels on touch devices. The exception is a link inside a sentence, which WCAG exempts and which we leave inline rather than breaking the paragraph around it.

Pinch-zoom is not blocked. The page used to cap the viewport scale, which stops you enlarging the type — the reason people usually give for doing that is solved here by making form fields 16px on touch instead.

Motion is reduced or removed for anyone whose system asks for it, including the animated sequence on the homepage, which is skipped entirely rather than slowed.

Body text does not drop below 15 pixels on a phone on the marketing pages. The demo platforms are denser by design and hold a 12.5 pixel floor.

Tables wider than a phone scroll inside their own container rather than stretching the page sideways.

Form fields are tied to their labels, so tapping a label focuses its field and a screen reader announces what the field is for.

Links inside a paragraph are underlined, not only coloured.

Images are described or, where decorative, hidden from assistive technology. Icons drawn as symbols are hidden too, because a screen reader otherwise announces them by their Unicode names. The site uses no photography.

Where we fall short today

We have not tested with a screen reader. Everything above was verified by measuring the live page and by running automated tools, which is not the same as listening to what VoiceOver or NVDA announces. Automated tools catch perhaps a third of real accessibility problems; the rest need a person.

We have not tested on a real iPhone or Android handset. The measurements were taken in a desktop browser at handset dimensions, which does not reproduce the on-screen keyboard, the browser chrome, or how iOS Safari behaves at the edges of the viewport.

We have had no independent accessibility audit, and a clean axe run is not a conformance claim.

The signed-in areas — the client portal interior and Forge Admin — have not been tested with either tool, because that needs an account. Their sign-in pages are clean; what is behind them is not verified.

The demo platforms are dense, desktop-first interfaces. They are keyboard reachable, but reachable is not comfortable, and we have not checked that the reading order of every one of their several hundred screens makes sense.

A table that scrolls sideways is a workable answer on a phone, not a good one. Some of them would be better rebuilt as stacked cards.

Telling us about a problem

Email hello@forgesoftware.co with the page and what went wrong. We will reply within five working days and tell you honestly whether and when we can fix it.

If you need information from this site in another format, ask and we will send it to you directly.