Accessibility Statement
Our commitment to making SpicaNova AI usable for everyone, including people who rely on assistive technologies.
Our commitment
SpicaNova AI is committed to ensuring digital accessibility for people with disabilities. We are continually improving the user experience for everyone and applying relevant accessibility standards.
We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. WCAG 2.2 defines requirements for making web content more accessible to people with disabilities.
Conformance status
SpicaNova AI partially conforms to WCAG 2.2 Level AA. Partially conforms means that some parts of the content do not yet fully conform to the accessibility standard. We have not yet commissioned a full third-party audit; the assessment below is based on our own self-evaluation.
This statement reflects our own review of the product as deployed on August 9, 2026. It has not been reviewed or certified by anyone outside SpicaNova.
What we have done
The following accessibility features are currently implemented:
- Skip navigation link: a visible "Skip to main content" link appears on keyboard focus on our policy and product pages (Pricing, Security, Privacy, Terms and this page) and throughout the signed-in application, so keyboard users can jump past the navigation to the page body (WCAG 2.4.1).
- Semantic HTML: pages use proper landmark elements (
<header>,<main>,<nav>,<footer>) and heading hierarchy. - ARIA attributes: navigation elements include
aria-labelandaria-currentfor screen reader context. - Keyboard focus: a document-level
:focus-visiblestyle draws a visible focus ring, so keyboard focus is indicated on the marketing pages, the sign-in screens and the signed-in application. Some components (text fields and the message composer) replace that ring with their own border and glow instead of an outline. We have not verified every interactive element individually, and the third-party embeds listed below carry their own focus styles. - Reduced motion: for users who have set
prefers-reduced-motion: reducein their system settings, animations and transitions across the product are reduced to near-zero duration, so elements settle immediately instead of floating, spinning or scaling (WCAG 2.3.3). - Colour contrast (partial): in our spot checks, primary text on backgrounds meets AA contrast ratios. Some muted secondary text (ink-3 on the light theme) is at or near the 4.5:1 AA threshold. We have not measured every text and background combination.
- No auto-playing media: the product contains no audio or video elements at all, so nothing auto-plays.
Known limitations
The following known accessibility issues exist. We are working to resolve them:
| Area | Issue | Status |
|---|---|---|
| Page titles inside the app | Every page in the signed-in application shares one browser tab title. Individual page titles are not set, so a screen reader user cannot identify the current page from its title (WCAG 2.4.2). Identified in our June 2026 internal review and not yet resolved. | Open |
| Icon-only buttons | Buttons that show only an icon have not been swept for accessible names. Many carry an aria-label, but we have not checked all of them, so some may be announced only by their icon or not at all (WCAG 4.1.2). Identified in our June 2026 internal review and not yet resolved. | Not yet audited |
| Announcing live updates | Areas that change without a page load use aria-live in several places (the sync status pill, chat status, inline save confirmations) but not everywhere. A screen reader may not announce some draft and sync updates (WCAG 4.1.3). Identified in our June 2026 internal review; partially addressed. | Partial |
| Focus obscured by sticky elements | We have not tested whether the sticky application header, a dialog or a toast can cover an element while it holds keyboard focus (WCAG 2.4.11, new in WCAG 2.2). Identified in our June 2026 internal review and not yet tested. | Not yet tested |
| Touch and pointer target size | Target sizes, including the Approve and Reject controls and icon-sized buttons, have not been measured against the WCAG 2.2 AA minimum of 24 by 24 CSS pixels across breakpoints (WCAG 2.5.8). They appear large enough, but appearance is not a measurement. | Not yet measured |
| Urgent / OK colour indicators | The --urgent (red) and --ok (green) palette variables on draft cards have not been formally audited for contrast on the dark theme. Colour is also conveyed by a label, not colour alone. | Audit pending |
| Third-party canvas/diagram embeds | tldraw and Excalidraw are embedded tools with their own accessibility characteristics that we do not fully control. They may not fully meet AA. | Out of scope (third-party) |
| No automated a11y CI | We do not yet run automated accessibility tests (axe-core, Playwright a11y) in our CI pipeline. | Planned |
| PDF / PowerPoint exports | Agent-generated PDF and PPTX report downloads have not been audited for PDF/UA or accessible document structure. | Planned |
This list covers the issues we know about. It is not a claim that no other issues exist, because no full audit has been run. If you encounter an accessibility issue not listed here, please tell us (see contact below).
Assessment approach
SpicaNova AI assessed this product using the following approaches:
- Self-evaluation against WCAG 2.2 success criteria.
- Code review for semantic HTML, ARIA usage, and keyboard handling.
- Manual keyboard navigation testing (Tab, Shift-Tab, Enter, Space, arrow keys).
- Colour-contrast spot checks using the WebAIM Contrast Checker.
Just as importantly, here is what we have not done:
- We have not tested the product with a screen reader (NVDA, JAWS, VoiceOver or TalkBack).
- We have not tested with speech input, screen magnification, or a switch or other alternative input device.
- We have not tested on mobile browsers with assistive technology enabled.
- We do not run automated accessibility checks in our build or deployment pipeline.
- We have not commissioned a third-party audit, and we hold no VPAT or ACR.
A formal third-party audit against WCAG 2.2 AA is planned before the first enterprise customer onboarding.
Feedback and contact
We welcome feedback on the accessibility of SpicaNova AI. If you experience any accessibility barriers, please contact us:
- Email: accessibility@spicanova.ai
- General contact: hello@spicanova.ai
We aim to respond to accessibility feedback within 5 business days and to resolve confirmed issues in the next available release cycle.
Enforcement and complaints
If you are not satisfied with our response, you may contact a relevant regulatory authority. In the United Kingdom, this is the Equality and Human Rights Commission (EHRC). In the European Union, this is your national disability rights authority. In the United States, the applicable body is the Department of Justice.
EU Accessibility Act (EAA): SpicaNova AI is currently operated as a microenterprise (fewer than 10 staff and annual turnover below €2 million). Microenterprises are currently exempt from EAA product-accessibility requirements. We will reassess this status as the company grows and comply as required.