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 is in place

Body text meets a 4.5:1 contrast ratio, and large text 3:1, across the site. The homepage changes colour as you scroll, and contrast is checked at every point of that transition rather than only at the ends.

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 the surface behind it and clears 3:1 — 4.62:1 on the marketing pages, and between 4.09:1 and 8.9:1 inside the four demo platforms, each of which has its own palette.

Interactive elements are reachable by keyboard. That includes the clickable table rows, cards and chart columns inside the demo platforms, which are not buttons and so 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.

Motion is reduced or removed for anyone whose system asks for that, including the animated sequence on the homepage.

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 there.

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

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

Images are either described or, where decorative, hidden from assistive technology. 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 — focus order, computed contrast, element dimensions, keyboard activation — which is not the same as listening to what VoiceOver or NVDA actually announces, and we expect that to surface problems.

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 not run an automated audit tool or had an independent accessibility review.

The four demo platforms are dense, desktop-first interfaces. They are keyboard reachable now, but reachable is not the same as comfortable, and we have not verified 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.