Accessibility statement
We target WCAG 2.2 Level AA and we do not claim conformance. The list of what is wrong is the part of this page worth reading.
Version 1.0.0 Effective 2026-08-24 Last updated 2026-08-24
In short
Applies to: Public sector and enterprise buyers, and anyone who hits a barrier
- The target is WCAG 2.2 Level AA. We do not claim conformance.
- Known gaps are listed by name with the date each was found.
- There is a route to report a barrier and a stated response time.
The conformance target
Tingvar targets WCAG 2.2 Level AA on this website. We do not claim conformance, because a conformance claim asserts that every criterion is met on every page and we have not audited every page.
| Standard | Why |
|---|---|
| WCAG 2.2 Level AA | The current standard, and the level the European Accessibility Act expects |
| EN 301 549 | The harmonised European standard, which applies because we take payment from EU consumers |
| WCAG 2.2 criterion 2.4.13, focus appearance | Adopted as a house rule at Level AAA, without claiming AAA conformance |
Scope
This statement covers the public website. The application, the room and the mobile clients are not covered, because they are not built. This page is updated before any of them ships.
Known gaps
A statement with no known issues list is not credible. These are the ones we know about on the date beside each row. When one is fixed it moves to the version history rather than disappearing.
| Item | Criterion | Impact | Found | Fix by |
|---|---|---|---|---|
| No audit with assistive technology has been carried out | All | Nobody has confirmed the site with a screen reader in a recorded session | 2026-08-24 | Before launch |
| The room and the application are not covered by this statement | All | A user cannot tell from this page whether the product itself is usable | 2026-08-24 | When the application exists |
| The audio samples on the site carry a transcript and captions, and no audio description | 1.2.3 | A description of what is audible but not spoken is not provided | 2026-08-24 | Under review |
How we test
- Automated rule checks on every build, at four widths and in both palettes
- Keyboard only navigation of every built route
- Reflow at 320 pixels with no horizontal page scroll
Automated rules find roughly a third of what is wrong with a page. The rest needs a person with assistive technology, and the first row of the gaps table above is that nobody has done it yet.
The product, not the website
Tingvar is a spoken argument. The live transcript in the room is the media alternative for anyone who cannot use the audio, and we are not going to claim that a transcript makes a spoken debate equivalent for a deaf user. When the room exists, this page covers it and the gaps list grows.
Related questions
Can I use it with a screen reader, or without hearing the audio?
Tingvar targets WCAG 2.2 Level AA on the website, and the live transcript in the room is the media alternative for anyone who cannot use the audio. Known gaps are listed by name on the accessibility page with the date each one was found, rather than summarised as a commitment to inclusion. The product itself is a spoken argument, and we will not pretend that a transcript makes it equivalent for a deaf user. There is a route to report a barrier and a stated response time.
Report a barrier
Tell us what you were trying to do, what happened, and what you were using. We reply within 5 business days and we add the finding to the table above whether or not we can fix it quickly.
accessibility@tingvar.com
If we do not respond
In the UK, the Equality Advisory and Support Service handles complaints about an inaccessible service. In the EU, each member state names an enforcement body under the European Accessibility Act, and your national body is the route. Tell us first if you can, because we would rather fix it than read about it.