Overview
Complaint Analyst is used by analysts and compliance reviewers in regulated organisations, so the product needs to be usable by everyone on the team, including people who rely on assistive technology. This statement documents the accessibility posture of the analyst product and the public Trust Center today.
We publish what is currently true rather than a marketing promise. Where the product does not yet meet a particular criterion, it is listed openly under Known Limitations, together with the route for reporting new issues.
Standard & Target
The target standard for the product is the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. This is the same target used by the UK public sector bodies accessibility regulations and by most regulated enterprise buyers.
Complaint Analyst has not yet completed an independent third-party WCAG audit. We therefore do not claim certified conformance. What we do claim is a good-faith, in-progress effort to meet WCAG 2.1 AA, with remediation work prioritised when new gaps are identified.
Screen Reader Support
Pages are structured with a single top-level heading per page, descriptive section headings, and landmark elements such as nav, main, article, and aside so that assistive technologies can build a reliable outline of the page. Navigation landmarks carry an explicit aria-label to distinguish primary navigation, breadcrumb navigation, and in-page tables of contents.
Decorative separators in breadcrumbs and metadata rows are marked aria-hidden so that screen readers do not announce them as content. Form controls are paired with visible labels, and the public inquiry form used throughout the Trust Center is built around standard label and input associations.
Colour, Contrast & Visual Design
The product uses a light-only visual system defined in DESIGN.md. Brand colours and typography are configured in a single Tailwind configuration file, which gives the design system a single source of truth for colour tokens and spacing rather than ad hoc per-component styling.
We do not ship a dark mode toggle today. Users who prefer a higher-contrast or inverted appearance can rely on operating-system level tooling (high-contrast modes, reader view, custom stylesheets) while we continue to evaluate a first-party dark theme.
Known Limitations
The product has not yet been tested against every WCAG 2.1 AA success criterion by an external auditor, so there may be undiscovered issues. In particular, we are aware that complex analyst workflows involving keyboard shortcuts, drag interactions, and data tables benefit from dedicated accessibility review, and this review is part of the outstanding remediation backlog.
The public marketing site and the Trust Center are prioritised for accessibility because they are the main surfaces that reach reviewers outside the customer organisation. Internal analyst surfaces are iterated against the same standard but may lag the public surfaces while a new feature is being built.
Feedback & Remediation
If you encounter an accessibility barrier in Complaint Analyst, please report it using the diligence request form at the bottom of this page. Include the page or workflow where the issue appears, the assistive technology you were using, and a short description of what you expected to happen.
Reported accessibility issues are triaged alongside security and compliance reports rather than being routed into a generic feedback queue. When a fix requires a product change, the change is tracked in the normal engineering workflow so that there is an auditable trail from the report to the remediation.
Third-Party Content
Some parts of the experience include content or components provided by third parties, such as edge TLS and content delivery from Cloudflare, and managed database infrastructure from Supabase and Hetzner. We rely on those providers' own accessibility posture for their infrastructure surfaces, and we do not republish their dashboards inside the product.
Customer-supplied content loaded into the product (for example a knowledge base article written by an analyst team) inherits the accessibility of the authored text. We encourage customer administrators to use descriptive headings, plain language, and meaningful link text when authoring knowledge base content.