Accessibility Statement

1. The Standard We Aim For

We target the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. That is the level most public bodies and large organisations are held to, and it is the level we build client sites to as well.

Aiming for a standard is not the same as certification. No one has audited this site on our behalf, and we do not claim conformance. What we claim is that we test against WCAG 2.2 AA, that we fix what we find, and that we are honest about the parts we have not proven.

2. How We Test

Every change to this site runs through the following before it ships:

• An automated accessibility suite written for this project — currently 106 checks — covering landmarks and heading order, form labelling, focus styling, colour contrast ratios, reduced-motion support, link text, and the WCAG 2.2 additions such as target size and focus visibility
• axe-core 4.13.0 across the home, services, projects, contact, impact-websites, origins, privacy and booking pages, and against the navigation drawer while it is open — a state automated tools routinely miss because it does not exist until you open it
• Google Lighthouse on desktop and mobile
• Manual keyboard checks of the navigation drawer: that it opens, moves focus to the close button, keeps Tab inside itself, closes on Escape, and returns focus to the button that opened it
• Layout checks at 320 pixels wide, at 200% browser zoom, and with the WCAG 1.4.12 text-spacing overrides applied, confirming no content is lost and nothing scrolls sideways

At the last full run the project suite reported 106 passes and no failures, and axe-core reported no violations on any page tested, including the open drawer. Lighthouse returned 100 for accessibility on both desktop and mobile.

We record those numbers because they are checkable, not because they settle the question. A page can pass every automated test and still be unusable — which is what Section 3 is about.

3. What We Have Not Verified

This is the part most accessibility statements leave out. These are real limitations, and we would rather you knew them than found them:

• Screen reader output. We have not tested this site with NVDA, JAWS or VoiceOver. Automated tools confirm that elements carry accessible names and roles; they cannot confirm that what a screen reader actually announces makes sense in sequence. This is our largest untested area.
• Colour contrast over moving backgrounds. Several sections place text over an animated canvas. Our contrast checks confirm the colour tokens themselves meet or exceed the required ratios, but automated tools return an inconclusive result for text sitting over a canvas, because the background is not a fixed colour. We have not measured those combinations by hand.
• Testing with disabled people. We have not put this site in front of anyone who uses assistive technology daily. Automated checks and our own keyboard testing are not a substitute for that, and we do not present them as one.
• Third-party content. The booking calendar on our booking page is supplied by Cal.com and runs inside their own embedded frame. We chose to load it only when you ask for it, but we do not control its markup and cannot guarantee its accessibility. If it is a barrier for you, the same page offers to take your booking by message instead, and that route is ours and is tested.

4. Telling Us About a Problem

If any part of this website is difficult or impossible for you to use, please tell us. Email NuuLuxStudios@gmail.com with the page address and a short description of what went wrong, or call (910) 557-2032.

We will reply within 5 business days. If the fix is quick we will make it and tell you when it is live. If it is not quick we will tell you that honestly, explain what is involved, and give you a way to get what you needed in the meantime.

You do not need to know the name of the standard, or which guideline applies, or any technical language at all. “I could not get past the menu with my keyboard” is a complete and useful report.

5. Scope of This Statement

This statement covers nuulux.net only. It does not cover websites we have built for clients — those are owned and run by the businesses they belong to, and each has its own arrangements.

It also does not cover the content of third-party services reached from this site, such as the booking calendar described in Section 3 or any external site we link to.