Accessibility statement

Last updated August 16, 2026

We build websites for trade companies. We want the people who use them, and the people who use this site, to be able to do that whatever their circumstances and whatever they are using to browse.

That includes people using a screen reader, people navigating with a keyboard instead of a mouse, people who have made the text larger, people who prefer reduced motion, and people on a slow connection or an old phone. Plenty of the tradesmen we build for are reading on a cracked phone in bright sun with one hand. Accessibility and that are the same problem.

What we are aiming for

We aim to meet WCAG 2.2 Level AA, the most widely referenced web accessibility standard. We are not claiming we meet it everywhere today. We are claiming it is the target we build to, that we test against it, and that when we fall short we fix it rather than argue about it.

What we do on every page we build

• Text and background colours are checked for contrast, not eyeballed.
• Every button and link works with a keyboard alone and shows a clear outline when it has focus.
• Tap targets are at least 44 pixels, so they can be hit with a thumb.
• Every image carries a text alternative, and decorative images are marked so a screen reader skips them.
• Headings run in order, so navigating by heading gives a real outline of the page.
• Pages work without JavaScript. If a script fails, the content and the phone number are still there.
• Movement is small, happens once, and is switched off entirely for anyone whose device asks for reduced motion.
• Text can be enlarged in the browser without the layout breaking.
• Forms have real labels, and errors are described in words, not by colour alone.

Where we know we fall short

Being straight about this is part of the point. We have not completed an independent third-party audit; our testing is our own, using automated checks and manual keyboard and screen reader passes. We have not tested every combination of browser, operating system and assistive technology; we test the common ones. Some older pages may lag behind our current standard until we work back to them.

Content we do not control

Some pages link out to sites we did not build, including our customers' own sites once they take them over, and services such as maps or payment pages. We cannot promise anything about those. If a link from our site sends you somewhere unusable, tell us and we will look for another route.

Tell us about a problem

If any part of this site is hard to use, email [email protected] and say what happened, what page you were on, and what you were using. You do not need technical terms. "The button would not work with my keyboard" is a perfect bug report.

We aim to reply within five working days. If what you need is on a page you cannot use, tell us and we will give you the same information another way.

If you raise an accessibility problem with us and are not happy with how we handled it, you can take it to the accessibility authority where you live.

This statement

This statement applies to nitni.site and to the websites NITNI builds and hosts for its customers. It was prepared on August 16, 2026, and is reviewed at least once a year and whenever we make a significant change to how our pages are built.