Letterpier · Accessibility statement
Version 0.1 (draft) · Last updated 30 September 2026
https://app.letterpier.com/legal/accessibility
Accessibility statement
Erklärung zur Barrierefreiheit
We want everyone who builds with Letterpier to be able to use it, whatever their setup. This page says how far we have got, where we fall short, and how to tell us.
Contents (5)
We aim to meet WCAG 2.2 level AA on this website and in the dashboard. We have not had an independent audit, so we do not claim full conformance.
This statement covers app.letterpier.com: the website, the docs, sign-in and the dashboard. It does not cover the content of email that customers send or receive through Letterpier.
We publish this statement voluntarily. Letterpier is offered only to businesses, so the German accessibility act for products and services (Barrierefreiheitsstärkungsgesetz, BFSG), which covers services for consumers, does not require it.
- Everything works with a keyboard, and every focused element shows a visible outline. The first link on every page with navigation is “Skip to content”.
- We respect your system’s reduced-motion setting. The website’s footer also has a “Reduce motion” switch. With reduced motion, animations are replaced by their final state.
- Our automated tests check the contrast of every colour pair in our design system’s contrast table, for text, controls and focus outlines, in light and dark mode.
- If your system asks for more contrast, borders and secondary text become stronger. In forced-colours modes, such as Windows contrast themes, background textures are removed and status labels get a solid border.
- Pages are structured with headings, landmarks and lists, and each page has one main heading.
- Nothing appears only on hover. Tooltips repeat information that is also available elsewhere.
- Simulations and charts have text alternatives. The animated message trace on the home page, for example, has a written description and a button for each station. [To verify: confirm once the trace ships on the home page]
- Pages reflow at a width of 320 pixels without scrolling sideways; code blocks and wide tables scroll inside their own box.
- Apart from the 10-minute validity of a sign-in code, which the sign-in page states, and the 7-day sign-in session described in our privacy policy, nothing ends on a timer. After asking for a code, you can ask for a new one after 60 seconds.
- German words and passages are marked as German, so screen readers pronounce them correctly.
We know of these limitations:
- Email previews in the dashboard show the message’s own HTML in a sandbox. How accessible a preview is depends on whoever wrote the email.
- Code samples in the docs are long lines of code. Screen readers read them symbol by symbol, and on small screens they scroll sideways inside their box.
- The dashboard’s log tables are dense and harder to use on small screens.
- Short notifications in the dashboard close by themselves after a few seconds. They stay open while the pointer rests on them, and each has a close button, but they don’t stay open while they have keyboard focus.
- The licence texts on the open-source licences page are reproduced exactly as their authors wrote them, as plain monospaced text.
[To verify: complete this list after the manual test pass before publishing]
Self-assessment with axe and manual keyboard testing, . Screen-reader testing: [To be supplied: date of the screen-reader pass].
We check pages with axe, using the WCAG 2.0, 2.1 and 2.2 rules for levels A and AA, in light and dark mode and with reduced motion, and by hand with a keyboard. Automated checks find only some problems, which is why we test by hand as well.
[To verify: after the screen-reader pass (VoiceOver on macOS and iOS), replace the placeholder with its date; name the automated suite and its pages once it runs in CI]
If something on Letterpier is hard to use with your setup, or you need information in another form, write to mail@michael-ketzer.com.
It helps if you tell us the address of the page, what you were trying to do, and the browser and any assistive technology you use.
We aim to reply within 10 working days.
Version history
| Date | Version | Changes |
|---|---|---|
| Version 0.1 (draft) (this version) | First draft for legal review. |