Accessibility

A skip link to the main content, which is the first thing a keyboard reaches. Headings in a real order rather than chosen for their size. Labels on every form field. Tables with captions. Images carrying descriptions of what they show rather than their filenames. A declared page language, so a screen reader pronounces it as British English.

Text contrast is checked against the AA threshold rather than judged by eye. A contrast failure at 4.35 to 1 shipped on this site in September and was caught by measurement, not by anyone looking at it, which is the reason it is measured.

The homepage, the cost comparison, the contact page and the portfolio were audited on 3 October 2026 against WCAG 2.1 AA, on a mobile profile, through PageSpeed Insights so the result comes from Google's hardware rather than one laptop. One failure was found and fixed in the same change: links inside body text were distinguished by colour alone, and in-prose links are now underlined.

That is not a conformance claim, and it would be dishonest to present it as one. Automated tooling finds a minority of the ways a page can fail someone. It cannot tell whether a link makes sense read out of context, whether a heading order describes the page or merely sizes it, or whether a form that passes every check is still unusable with a screen reader. Those need a person, and ideally a person who uses one.

So what is claimed here is narrow and true: a standard is being aimed at, automated checks pass, and the things found have been fixed rather than noted.

No part of this site has been tested by someone who relies on a screen reader day to day. Until it has, there will be failures nobody here has thought of, and the honest position is to say so rather than wait to be caught.

The cost comparison carries a wide table. It reads correctly on a phone, and the figures are reachable in order, but a table is a harder thing to navigate aurally than prose and the same information is not currently offered any other way.

Email hello@wizardworks.io and say what you were trying to do, what happened, and what you were using. You do not need to know the standard or name the failure. A sentence is enough.

You will get a reply within two working days, and anything that stops you using the site is treated as a defect rather than a feature request, which means it is fixed at no charge and not scheduled.

This statement covers Wizard Works's own site. Sites built for clients are the client's, and their accessibility is covered by whatever was agreed in that engagement. If you have hit a problem on a site built here, tell us anyway and it will reach the right people.

The terms cover the commercial side, and the privacy policy covers what is collected.