Seacove Accessibility Statement
Last updated: 11 August 2026.
1. Our commitment
Seacove is built to be usable by everyone who wants to use it, including people using assistive technology, people navigating by keyboard alone, and people who need higher contrast, larger text, or reduced motion. This applies to seacoveapp.com, the marketing and support website. The mobile app is a separate product with its own accessibility work; this statement is scoped to the website.
2. Conformance status
Seacove’s website conforms to the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA.
This was tested, not assumed. A Lighthouse CLI audit in mobile form factor was run against every page type on the site (home, the legal pages, support, subscriptions, delete-account, download, FAQ, contact, and a non-English locale). Every page scored 100 on Accessibility and 98 or above on Performance, Best Practices and SEO. Two issues the first pass found (insufficient colour contrast on one link colour token in dark mode, and a missing <main> landmark) were fixed and re-tested clean before this statement was published.
A note on where the technical standard is heading. The EU’s European Accessibility Act (Regulation (EU) 2019/882), in force for covered services from 28 June 2025, sets its technical standard as EN 301 549, which is itself moving to incorporate WCAG 2.2 rather than 2.1. Seacove’s site meets WCAG 2.1 AA today, one version behind that direction of travel. Seacove currently qualifies for the EAA’s micro-enterprise exemption (services provided by an enterprise with fewer than 10 people and under €2 million annual turnover are exempt), which is true of Seacove’s small operating team today. That exemption is a status that can change as the operation grows, the same way the Article 37 Data Protection Officer threshold in the Privacy page can change. The honest position: Seacove is not currently legally required to meet the EAA’s own standard, meets a slightly earlier version of WCAG by choice, and will revisit the 2.1-versus-2.2 question if the exemption stops applying.
3. What is built to meet this standard
- Colour contrast. The site’s colour palette (violet
#8244EE, magenta#D946EF, and the surrounding neutral scale) has contrast ratios measured against WCAG AA thresholds indocs/design/design-system.mdbefore any page was built, not checked afterward. - Keyboard navigation. Every interactive element, the header navigation, the locale selector, the download badges, forms and links, can be reached and operated using a keyboard alone, with a visible focus state at every stop.
- Alt text. Every meaningful image carries descriptive alt text; purely decorative images (the SVG marine art) are marked so assistive technology skips them rather than reading out noise.
- Reduced motion. The site’s animated SVG art respects the operating system’s “reduce motion” setting and falls back to a static version when it is set.
- Semantic structure. Headings, landmarks and page structure follow a logical order, so a screen reader user can navigate the page by structure, not just top to bottom.
- Security and permissions headers. The site’s
_headersconfiguration denies camera, microphone and geolocation access at the platform level, which has no direct accessibility function but reflects the same build discipline: nothing is requested or exposed beyond what the page actually needs.
4. Known limitations
None found. The audit described in section 2 turned up two issues, both fixed and re-tested before this statement was published. If a future audit or a user report finds a specific page, component or interaction that does not meet the AA target, it will be listed here by name until it is fixed.
5. Reporting an accessibility problem
If you use Seacove’s website and hit a barrier, whether or not it is something covered above, tell us. This is one of the most useful things you can report, because an accessibility problem often is not visible to someone who is not experiencing it.
Report it to: support@seacoveapp.com
Tell us what page you were on, what you were trying to do, and what happened instead. If you were using assistive technology (a screen reader, a switch device, voice control, browser zoom), telling us which one helps us reproduce the problem.
This inbox is monitored and commits to acknowledging an accessibility report within 5 business days, and to giving you a clear answer on what will be done, and roughly when, in that same reply. This mirrors the response discipline already committed elsewhere in Seacove’s operations (the 24-hour moderation response inside the app, the 30-day GDPR rights response on the Privacy page), scaled to a reasonable window for a website fix rather than an in-app safety action.
6. Compatibility
The site is built and tested against current versions of the major browsers (Chrome, Safari, Firefox, Edge) on both desktop and mobile, and against common screen readers on those platforms. It does not rely on Flash, Java applets, or any other technology that assistive technology cannot reach.
7. Changes to this statement
This statement is a live document. It is updated whenever a material change is made to the site’s accessibility posture, or a new audit changes the result reported in section 2. A new dated version replaces this one when that happens, and the old version is kept in the project’s own records rather than deleted.