Accessibility
Accessibility statement
Seaggle treats accessibility as a product requirement rather than a launch clean-up task. This page explains what we target, what we have verified, and how to tell us when we fall short.
Our target
We aim to meet WCAG 2.2 Level AA across templates, components, forms, motion, content, and responsive states. Automated checks support that work; they do not replace manual keyboard, screen-reader, zoom, and contrast review.
What we build to
- Semantic landmarks and a logical heading hierarchy on every page
- A skip link, descriptive link text, and visible current-page states
- Full keyboard operation for menus, selectors, accordions, and forms
- Visible focus indicators that are never removed
- Labels, hints, and errors associated programmatically with their fields
- No meaning conveyed by colour alone
- Text equivalents for diagrams and meaningful images
- Support for 200% zoom and reflow without loss of content or function
- Touch targets of approximately 44px or larger
- A reduced-motion alternative that preserves all information
Known limitations
Third-party embeds
The site currently contains no third-party embedded content. If any is added, it will be assessed against the same standard before it ships.
Formal audit
Accessibility has been built in and tested during development. An independent audit has not yet been commissioned; when one is, this statement will record the date and findings.
Tell us when something does not work
If any part of this site prevents you from doing what you came to do, we want to know — including which page, what you were trying to do, and the assistive technology or settings you use. We will acknowledge your message and tell you what we intend to do about it.
Send accessibility feedback