Accessibility statement.
What we're targeting, what's actually been checked so far, and where we're honestly still short.
Our target
We're building this site to conform to WCAG 2.2 Level AA. That's a target we're actively working toward, not a claim that every page fully meets it today — the section below says plainly which parts have and haven't been verified.
What's been done
The site is built with semantic HTML landmarks, a skip-to-content link, labelled form fields, and descriptive link text rather than "click here." Icons and decorative graphics are marked so screen readers skip them; meaningful ones carry a text alternative. Colour combinations used for body text are checked against the 4.5:1 contrast minimum at build time, not eyeballed.
A manual pass has since verified: keyboard-only navigation across the site, including the mobile menu — which now moves focus into the menu when it opens, returns focus to the menu button when it closes, and prevents Tab from reaching content hidden behind it while it's open, none of which was true before this check; visible focus indicators on every interactive element, including form fields, which previously relied on a border-colour change alone; reflow at 320px CSS width (equivalent to 400% zoom) across every page template with no horizontal scrolling; and hover-state colour contrast on primary links and buttons.
What hasn't been manually verified yet
We don't have screen-reader software (NVDA / VoiceOver) available in the environment this check was run from, so a real assistive-technology pass — particularly of the enquiry form's error and success states — is still outstanding. 200% text-only scaling (as opposed to full-page zoom) also hasn't been separately checked.
We're not going to claim these are fine until we've actually checked them. This statement will be updated once that's done, with fixes for whatever it finds.
Known limitations
Scroll-triggered reveal animations respect prefers-reduced-motion and turn off entirely for anyone with that preference set. Beyond the screen-reader and text-scaling gaps above, we don't currently know of specific barriers.
Reporting a problem
If you hit an accessibility barrier anywhere on this site, tell us and we'll fix it: info@greensuniversal.com. Include the page and, if you can, what assistive technology you were using — it makes the fix faster.