Target
The public site is built with WCAG 2.2 AA as the working standard.
The public site is built with WCAG 2.2 AA as the working standard.
Use the feedback form if something is hard to use or you need another format.
Support built in
The public journeys are designed to be readable, keyboard reachable, and usable without relying on one accessibility widget.
Skip links, clear headings, breadcrumbs, visible focus states, and keyboard-friendly menus.
Labels, helper text, visible errors, focus recovery, and a no-JavaScript fallback.
Reduced-motion preferences are respected and heavy third-party embeds are avoided on arrival.
Checks
This statement is based on the live build and repo checks, not a claim of perfection.
Keyboard, focus, forms, motion, and responsive layout were reviewed across the main public routes.
The repo uses Astro validation and browser checks to catch regressions.
Reviewed against the live launch build on 23 April 2026.
Working target: WCAG 2.2 AA. Assessment approach: self-evaluation.
No independent audit published yet
Cookie choices
This site does not show a cookie banner at launch. The Cookie Notice explains the live first-party aggregate analytics model, the objection control on that route, and the storage that stays absent.
Known limits
Known limits are listed plainly with the practical next step.
Instagram, email apps, calendar apps, and external map services are outside the main website.
The launch build has been reviewed, but no independent accessibility audit is published yet.
External services
External destinations have their own accessibility and privacy behavior.
Social links leave the site and open the third-party platform.
Mailto links and calendar files depend on the app that opens them.
The contact route does not auto-load a map. Future map links will need review.
Review
The statement should change when the website changes or a new barrier is found.