Threadsovereign

Accessibility Statement

Last assessed: 26 July 2026 · Next review: 26 October 2026

Threadsovereign Ltd is committed to making the Threadsovereign Platform accessible to as many people as possible, including those with disabilities. We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA standard.

1. Current Compliance Status

Partial compliance: The Threadsovereign Platform is partially compliant with WCAG 2.2 Level AA (and the overlapping WCAG 2.1 AA bar). We target full 2.2 AA. Automated checks and engineering remediations (Sprints A–D, July 2026) address many common barriers; live screen-reader sign-off and an independent audit are still outstanding. Some parts of the Platform may not yet fully meet the standard.

This statement was prepared through self-assessment by the development team, static analysis, and automated axe-core scans. It is not a claim of full WCAG 2.2 AA conformance.

Staging controls AX-01 (chart text alternatives) and AX-02 (form labels / error announcements) are recorded as PASS in BSA evidence trackers for scoped routes. Those spot checks do not equal platform-wide AA or a completed screen-reader matrix (AX-SR-01).

We have implemented the following accessibility features across the Platform:

  • Keyboard navigation support on most interactive controls
  • Screen reader-compatible form labels on primary flows
  • ARIA roles and attributes on Radix-based components
  • Visible focus indicators on core interactive elements
  • Semantic landmarks including labelled main regions and a skip-to-content link
  • Status badges include text labels (not colour-only indicators)
  • Animations respect prefers-reduced-motion
  • Unique, descriptive document titles derived from the route (updated as you navigate)
  • Task kanban and compliance checklist reorder support keyboard alternatives with polite live announcements
  • Analytics charts expose accessible names and (where practical) visually hidden data tables
  • Portal navigation landmarks are named; collapsed sidebars keep accessible names; risk-matrix cells announce likelihood, impact, and band

Residual gaps (tagged PDF/UA, independent WCAG 2.2 AA audit, and live assistive-technology sign-off) are listed below. We target WCAG 2.2 Level AA; automated and keyboard checks support that bar but do not replace an independent audit. Full conformance also requires residual UI polish and a PDF accessibility strategy (accessible HTML/CSV or a tagging-capable generator).

2. Known Accessibility Issues

We are aware of the following gaps that have not yet been fully resolved. They are listed in priority order.

PDF documents — accessibility tags (PDF/UA)

Ceiling

PDFs generated with jsPDF include document metadata and language where set, but are not tagged PDF/UA structure trees. Prefer the interactive HTML UI (or CSV/HTML exports where offered) as the accessible source of truth.
Target resolution: Programme beyond Q4 2026 (engine change or print-tagged HTML)

Independent WCAG 2.2 AA audit

Planned

Automated axe scans and keyboard journey smoke tests cover duty-holder routes, but a formal independent WCAG 2.2 Level AA audit (live NVDA/VoiceOver) is scheduled.
Target resolution: Q4 2026

File drop zones and remaining complex widgets

Lower priority

Some file upload drop zones remain mouse-oriented (click-to- browse is available). Residual RAG border patterns on some cards may still need text twins in edge cases.
Target resolution: Q4 2026

3. Technical Information

The Threadsovereign Platform relies on the following technologies for conformance:

  • HTML5 with semantic elements
  • CSS (Tailwind CSS v4)
  • JavaScript / TypeScript (React / Next.js)
  • WAI-ARIA 1.2

Testing to date (as of 26 July 2026):

  • Automated axe-core scans (WCAG 2.x A/AA tags) on expanded public and duty-holder routes
  • Keyboard-only smoke tests (Playwright) for skip link, landmarks, and selected occupied dialogs
  • Chrome accessibility DevTools and static code review

Live assistive-technology combinations below are planned for sign-off (matrix currently open — see internal AX-SR-01). We do not yet claim completed NVDA, JAWS, or VoiceOver validation across the Platform:

  • NVDA + Firefox / Chrome (Windows) — planned
  • JAWS + Chrome (Windows) — planned
  • VoiceOver + Safari (macOS) — planned
  • Keyboard-only navigation — smoke coverage in place

4. What We Are Doing to Improve

We are committed to ongoing accessibility improvement:

  • Accessibility testing (automated axe + keyboard smoke) is part of our development process for new features
  • We maintain an internal screen-reader sign-off matrix (AX-SR-01) and will update this statement when cells are signed Pass
  • Path to a scoped WCAG 2.2 AA claim: live AT Pass, residual polish, accessible PDF strategy (or HTML/CSV primary), then an independent audit and remediation loop
  • We review the known issues list quarterly and prioritise fixes by severity
  • We are working towards a full WCAG 2.2 Level AA audit by an independent accessibility specialist in Q4 2026
We welcome feedback on accessibility issues. If you encounter a barrier, please tell us — it helps us prioritise the right fixes.

5. Contact Us About Accessibility

If you experience any accessibility problems using the Platform, or you need information in a different format (e.g. large print, audio, accessible PDF), please contact us:

Accessibility contact

Email: accessibility@threadsovereign.io

We aim to acknowledge accessibility reports within 2 working days and respond in full within 5 working days.

6. Enforcement

If you contact us with a complaint about accessibility and are not satisfied with our response, you can contact the Equality and Human Rights Commission (EHRC):

In Northern Ireland, contact the Equality Commission for Northern Ireland.

This accessibility statement applies to the Threadsovereign platform at threadsovereign.io and all sub-paths. It was last reviewed on 26 July 2026.