Skip to content
Inkstand

legal

Accessibility

How this measures against WCAG 2.2 AA, surface by surface, and what to do when something stops you working. Self-assessed.

Version 0.1Effective 28 July 20265 min readTouch Grass AB

Written from the system, not from a template. Every statement here describes what the software actually does — the region, the sub-processors, what is collected, what is retained, what leaves the EEA. It is a description of a system rather than legal advice, and it is published rather than sent after a call. If your counsel needs redlines, or your own paper, that is a conversation and not a problem.

Contents — 5 clauses

1What this covers, and what it is worth#

1.1This statement covers the Inkstand website and the signed-in application operated by Touch Grass AB.
1.2It is a self-assessment. No accessibility audit has been commissioned, no assistive technology user has been paid to test it, and no conformance claim is made or implied anywhere on this site. It is the honest current position, prepared on the effective date above from the state of the code, and it will be wrong in places we have not found yet.

2The standard we measure against#

2.1The target is the Web Content Accessibility Guidelines version 2.2 at level AA, which is the standard incorporated by EN 301 549 and by the European accessibility rules.
2.2Status: partially conformant. Parts of the product have been built and repaired against specific success criteria, and other parts have not been assessed at all. Clause 4 names the ones we know fall short.

3What has been done#

Each of these is a specific repair to a specific failure rather than a general assertion, which is the only form in which this section is worth reading.

  • Bypass blocks. Every marketing page put eleven navigation and footer links ahead of the content with no way past them on a keyboard. A skip link is now the first thing the Tab key reaches, and its target takes focus rather than merely scrolling.
  • Visible focus. A focus ring is applied globally and marked so that a utility class removing outlines cannot cancel it, which it previously did on every input on the site.
  • Target size. Navigation links were nineteen pixels tall on a site whose traffic is mostly phones. Interactive controls are now held to a forty-four pixel floor on touch devices.
  • Reachability on a phone. The whole navigation used to be hidden below 768 pixels with no replacement, which made several pages unreachable on a phone. There is a mobile navigation now.
  • Reduced motion. Every animation and transition is disabled when the operating system asks for reduced motion, and the loading placeholders stop pulsing rather than merely slowing down.
  • Page changes announced. Client-side routing changes the page without a screen reader noticing. A polite live region announces the new page title on every route change, reading the title rather than a second list of names that could disagree with it.
  • Text contrast. The interface is near-black by design. The three text colours used on it have been checked by calculation against the 4.5:1 threshold and clear it, the lowest being the muted grey used for labels at about 6:1.
  • Structure. Headings are real headings, tables are real tables with header cells, and this legal set is numbered and anchored so a clause can be reached directly rather than by scrolling.

4What falls short#

  • The editor canvas. Composing a slide means positioning and resizing elements by pointer. Keyboard equivalents exist for some of it and are not complete, and the canvas has not been assessed against a screen reader. If composing artwork by keyboard alone is a requirement for you, treat this as not working today and tell us — it changes what gets built next.
  • Exported PDFs contain no text. Each page is a rendered image of the slide, so the text in an exported PDF cannot be selected, searched, resized or read aloud. This is a property of how the artwork is produced and it is a real limitation for anyone who receives an exported deck. The governance record exports as JSON, which is fully accessible, and slide copy can be copied out of the editor before export.
  • Images inside a slide carry no alternative text. They are treated as part of a picture the user is composing rather than as content, and the product does not yet ask for a description or carry one into an export.
  • Not assessed. The account, admin and review surfaces have not been reviewed against the guidelines. Neither has the product at 400% zoom, nor with Windows high contrast mode, nor with voice control.
  • No audit, no user testing, no VPAT. None of the three has been commissioned. If your procurement requires a VPAT or an EN 301 549 conformance report, we do not have one and will not produce a self-certified one to satisfy a form.

No part of the product is exempt from this statement on the grounds of disproportionate burden. The items above are unfinished work, not exclusions.

5Telling us something is wrong#

5.1If something on this site or in the product stops you doing what you came to do, tell us at privacy@touchgrass.consulting, or through the contact form. Say what you were trying to do, what happened, and what you are using, if you are willing to.
5.2You will get a reply from a person within ten working days, with a workaround if one exists and an honest answer about timing if one does not. If you need information from this site in another format, ask and we will provide it.
5.3If you are not satisfied with the response, you can raise it with the market surveillance authority designated for accessibility in the EU country where you live. The name of that body differs by country, so we have not guessed at yours.

Accessibility statement, version 0.1, effective 28 July 2026. Every agreement, and who you are contracting with, on the legal index.