Accessibility
Accessibility conformance
TCS is meant to be usable with a keyboard alone, with a screen reader, and at whatever text size someone needs. This page summarises our conformance report. The full report is available on request.
What we assess against
- WCAG 2.2, Levels A and AA
- Revised Section 508 (36 CFR 1194, Appendix A to C)
- EN 301 549 v3.2.1
The report follows the VPAT 2.5 Rev format, so it can go straight into a procurement or accessibility review.
What the assessment covers
The signed-in web application, the public intake portal, the sign-in and password-reset flows, the native iPhone and iPad app, and the signature and validation report PDFs the server generates, which are tagged with headings, reading order and a document language.
Not covered: spreadsheet exports, which carry no structure beyond a header row; email notifications, which are informational and never the only way to act on something; and the companion macOS apps, which are built on standard platform controls but have not been evaluated, so we do not claim them.
How it was evaluated
- Keyboard-only traversal of every interactive surface, by hand
- VoiceOver on macOS and iOS
- A contrast audit of all 28 shipped themes against 15 foreground and background pairings
- Automated accessibility linting across the web source, plus source review of every interactive component
This is a self-assessment, not a certification. We performed it ourselves. It has not been audited by an independent third party, and we have not yet run testing with disabled participants. We consider that the most significant limitation of the report, and we would rather say so than imply otherwise.
Known exceptions
We would rather name these than round them up.
- Printed-from-the-browser PDFs. The reports the server generates are tagged. Pages you print from the browser produce whatever PDF the browser makes; the pages themselves are fully accessible, and the same data exports as CSV or XLSX.
- Spreadsheet exports carry no structural metadata beyond a header row. The same data is accessible inside the product.
- Email notifications are plain HTML and have not had an accessibility review. Nothing in TCS requires acting inside an email.
- Image cropping moves in steps by keyboard rather than continuously. This only affects optional refinement of a profile photo or organization icon; both upload and display correctly without cropping.
- Translation is partial. The interface is available in English, Brazilian Portuguese and Spanish, covering the screens people use daily. The administrative consoles are still English, and the translations are a first pass that a native speaker has not yet reviewed. Untranslated text falls back to English rather than failing.
- The release-history chart is announced as one described figure rather than as individually navigable points, which is the intended treatment for a data visualisation. Every issue behind it is reachable through My Work and Query, and the per-release figures are a real list directly beneath the chart.
- No independent audit, and no testing with disabled users. See above.
Reporting a barrier
If something in TCS keeps you from doing your work, write to hello@usablesoftware.com. We treat a reported barrier as a defect, not a feature request. Ask at the same address for the full conformance report.