What we've been building.
The tickets page is now a board workspace. Tickets are grouped by surface in uniform columns with statement status surfaced in the drawer, platform-aware filters, and publish-aware abandon. The redesign is the primary /tickets route.
Bundle related tickets into groups for shared planning. Resolving now requires a Pass or N/A outcome, and abandoning a ticket asks for a reason so the audit history stays explainable. New filter scopes for In progress, All, and Resolved-only.
Filter questions by status with the new check filter bar, navigate back through screens with a dedicated button, and see which WCAG and EN 301 549 standards each question maps to with inline standards chips.
Audit questions are now split into screen-level and app-level. Screen-level questions apply per screen, while app-level questions cover your product as a whole. Both must be answered before publishing your accessibility statement.
Select your target jurisdictions — EU, UK, or US — and the right accessibility standards are mapped automatically. WCAG 2.2 AA and EN 301 549 criteria are now included alongside WCAG 2.1 AA, with per-screen classification driving question applicability.
A mobile-first messenger for communicating with your team and AUDITSU support. Real-time notifications via WebSocket, conversation threads, a new member picker, and a green presence indicator when support is online.
Audit across devices in real time. Connect your phone for testing and your desktop for review — verdicts, skips, and fail dialogs sync instantly via WebSocket. A presence indicator shows which devices are connected, and a mobile handoff prompt guides you through the setup.
The app shell now streams skeletons while billing data loads, server-side caching eliminates redundant API calls, and breadcrumbs provide consistent navigation across audit, screen, and walkthrough pages.
New users now walk through a five-step welcome flow: set your name, create a workspace, choose a theme, learn the core concepts (Measure, Manage, Evidence), and try The Lens. Progress is synced to the backend so you can pick up where you left off.
The public accessibility statement page now follows the spec structure with phase-aware rendering, enforcement procedures, and organisation legal details. Added a warmer statement of intent flow with question-led field hints.
