Accessibility statement

Checks carried out

Before launch, the site was checked as follows:

• Keyboard. Every page, including the menu, the four tools and the contact form, was used with a keyboard alone. Focus is visible on every link, button and field, with a focus outline that contrasts with each background.
• Screen widths. Every page was rendered at phone, tablet and desktop widths to check that nothing scrolls sideways and nothing is cut off.
• Contrast. Text colours were checked against their backgrounds for a contrast ratio of at least 4.5 to 1 for body text.
• Targets. Buttons and form controls were checked to be at least 24 by 24 CSS pixels, the minimum in WCAG 2.2 criterion 2.5.8, and main buttons are larger.
• Structure. One main heading per page, a heading order with no gaps, a skip link, and the page split into header, navigation, main and footer regions.
• Images. Informative drawings have text alternatives; decorative ones are hidden from screen readers.
• Forms. Every field has a visible label, required fields are marked in words, and errors name the field and explain the fix.
• Tables. Every data table has a caption and header cells.
• Without JavaScript. Pages remain readable, and the menu stays open, when scripts are switched off.

These checks were made with automated browser tests and by hand.

Not tested yet

Nobody has yet tested the site with a screen reader, or with disabled people on their own devices and settings. When that testing happens, this statement will be updated with what it found.

Known limits

• The planning tools need JavaScript to produce a result. Their questions remain readable without it.
• Line drawings of houses and plans are illustrations. Where they carry meaning, the text around them says the same thing.

Reporting a barrier

Please email hello@contractovix.site about any part of the site you cannot use, with the page address and a description of the problem. Please say how you would like a reply. If a barrier stops you using the contact form, email is always available as an alternative.

How changes are checked

Every page is produced by the same build, which refuses to publish a page with a missing title, an over-long description, a table without a caption or a broken internal link. When a page changes, the browser tests above are run again on the changed pages before they go live. New tools or forms get the full keyboard check before publication.

Design choices that help

• Body text is set at a comfortable size with generous line spacing, and line length is kept short enough to read easily.
• Colour is never the only way information is shown; required fields say so in words, and links in text are underlined.
• The handwritten style is used only for short decorative notes, never for information you need.
• Motion is avoided, and the site respects the reduced motion setting.

Standards

The target is the W3C's Web Content Accessibility Guidelines 2.2, level AA.