Accessibility Statement
Where TheirStack stands against WCAG 2.2 Level A and AA — which success criteria we verify automatically on every build, which we have reviewed by hand, and which we have not assessed yet.
TheirStack is committed to making app.theirstack.com and theirstack.com usable by everyone, including people who navigate with a keyboard, a screen reader, or a browser zoomed well past 100%.
Our conformance target is WCAG 2.2 Level AA.
Current status
Partially conformant. Some parts of the product do not yet fully conform.
We would rather tell you that than hand you a checkbox. Automated tooling can decide roughly a third of the WCAG success criteria; the rest need a person, and our manual screen-reader assessment is still in progress. This page says which is which, and we keep it current as that changes.
What we verify automatically
Every pull request runs an axe-core scan, scoped to the WCAG 2.0/2.1/2.2 Level A and AA rule set, in a real browser against 42 rendered pages of the app plus the marketing site and documentation. A build check refuses to merge a new page that has no scan, so the coverage cannot quietly shrink. Alongside it we run eslint-plugin-jsx-a11y over the source, and our own per-page checks for the things axe evaluates element by element but never as a whole.
| Success criterion | Level | How it is verified |
|---|---|---|
| 1.1.1 Non-text Content | A | Every image, icon, <object> and image map has a text alternative |
| 1.3.1 Info and Relationships | A | Tables, lists and form labels are structural; the heading outline has no skipped levels |
| 1.3.4 Orientation | AA | No CSS locks the page to one orientation |
| 1.3.5 Identify Input Purpose | AA | autocomplete values are valid |
| 1.4.3 Contrast (Minimum) | AA | Every text/background pair is measured against 4.5:1 (3:1 for large text) |
| 1.4.4 Resize Text | AA | The viewport meta tag does not disable zoom |
| 1.4.10 Reflow | AA | Every page is rendered at 320px wide and must not scroll horizontally |
| 1.4.12 Text Spacing | AA | Every page is re-rendered with the WCAG line, letter, word and paragraph spacing, and must not clip text |
| 2.4.1 Bypass Blocks | A | Every page exposes a "Skip to main content" link and a <main> landmark |
| 2.4.2 Page Titled | A | Every page has a non-empty <title> |
| 2.4.3 Focus Order | A | No positive tabindex anywhere — the tab sequence follows the reading order |
| 2.4.4 Link Purpose (In Context) | A | Every link has an accessible name |
| 2.4.6 Headings and Labels | AA | One <h1> per page, no holes in the outline, repeated landmarks distinguishable |
| 2.5.3 Label in Name | A | A control's accessible name contains its visible label |
| 2.5.7 Dragging Movements | AA | Each drag surface is checked for a single-pointer alternative; a new one fails the build without it |
| 2.5.8 Target Size (Minimum) | AA | Targets are at least 24×24 CSS pixels, or spaced far enough apart to meet the criterion's exception |
| 3.1.1 Language of Page | A | <html lang> is present and valid |
| 3.1.2 Language of Parts | AA | Any lang override is valid |
| 3.3.2 Labels or Instructions | A | Every form control resolves to a label |
| 3.3.8 Accessible Authentication (Minimum) | AA | Sign-in is delegated to our identity provider; we implement no password field and block no paste |
| 4.1.2 Name, Role, Value | A | Every ARIA attribute is valid, and every element reachable by Tab announces as something |
A green check is evidence, not a certificate. These tests catch the machine-decidable part of each criterion on the pages they cover; a criterion can still fail in a way no rule can express — an alt that describes the wrong thing passes 1.1.1 automatically and fails it in practice.
What we have reviewed, but cannot verify automatically
These we have gone through and fixed by hand. No tool can decide them, so they are held by code review rather than by a test.
| Success criterion | Level | Where we stand |
|---|---|---|
| 2.1.1 Keyboard | A | Controls that were clickable <div>s are now real buttons; every interactive element is operable |
| 2.4.7 Focus Visible | AA | Every focusable control draws a focus ring |
| 2.4.11 Focus Not Obscured (Minimum) | AA | Sticky headers and dialogs no longer cover the control that just received focus |
| 4.1.3 Status Messages | AA | Notifications are announced by a live region; only errors interrupt, the rest wait for a pause |
| 1.4.1 Use of Color | A | Status is carried by text or an icon as well as colour; links in body text are checked automatically |
What we have not assessed yet
We are not claiming these, in either direction. They need a person with assistive technology, and that work is scheduled rather than done.
- 1.4.5 Images of Text, 1.4.11 Non-text Contrast, 1.4.13 Content on Hover or Focus (AA)
- 2.1.2 No Keyboard Trap (A) and 2.4.5 Multiple Ways (AA)
- 3.2.1 On Focus, 3.2.2 On Input (A), 3.2.3 Consistent Navigation, 3.2.4 Consistent Identification (AA)
- 3.3.1 Error Identification (A), 3.3.3 Error Suggestion, 3.3.4 Error Prevention (AA)
- Whether each
alttext describes the right thing, whether the reading order makes sense non-visually, and whether a screen reader announces changes in a way that is actually followable. A tool can tell us an alternative exists; only a person can tell us it is right.
Charts are the clearest known gap. They now carry a visually hidden data table so the numbers are reachable, but we have not validated the experience end to end with a screen reader.
Compatibility
The app is a modern web application and is tested in current versions of Chrome, Safari, Firefox and Edge. We have not certified it against a specific screen reader version; that is part of the manual assessment above.
Assessment approach
Self-evaluation, using the automated checks described above plus code review against the WCAG 2.2 Level A and AA success criteria. We have not commissioned a third-party audit.
Tell us where we fall short
If something in TheirStack is not usable for you, we want the specific case — the page, what you were trying to do, and the assistive technology you were using. Write to hi@theirstack.com and we will come back to you.
If you are evaluating us against a procurement questionnaire and need our position on a criterion this page does not cover, ask us directly rather than inferring it. We would rather answer a hard question honestly than have you discover the answer later.
How is this guide?
Last updated on
TheirStack Brand Kit
Download TheirStack's official logos, wordmark, icon, brand colors, and product screenshots. Use these assets when referring to TheirStack in articles, integrations, partner pages, or press coverage.
Account Deletion & Data Removal
How to delete your TheirStack account and all associated data, what gets removed, our retention practices, and how to request erasure of personal data even if you don't have an account.