TailorBack

Accessibility

Last updated: June 8, 2026

This document describes how TailorBack works today. It is a plain-English summary intended for transparency, not formal legal advice. Items in [brackets] should be completed by the operator before public launch.

TailorBack is built to be usable by as many people as possible, including those who rely on keyboards, screen readers, or other assistive technology. We aim to meet the WCAG 2.1 AA guidelines and we keep improving as the product grows.

1. What we do

Keyboard friendly. You can reach and operate the main flows with a keyboard alone, including a "skip to content" link, visible focus outlines, and dialogs that trap focus, close with Escape, and return focus to where you were.
Readable by design. Pages use semantic headings and landmarks, labelled form fields and buttons, and clear status messages.
Comfortable visuals. We work toward sufficient colour contrast in both the light and terminal themes, and we honour your "reduce motion" system setting by toning down animations.
Responsive. The layout adapts to phones, tablets, and desktops, and to larger text sizes.

2. Known limitations

Some areas are still being improved, for example the live document editor and generated PDF previews. If you hit a barrier, please tell us and we will prioritise a fix.

3. Tell us about a problem

If something is hard to use or read, contact us through the contact form or at contact@tailorback.com. Please include the page and what you were trying to do, so we can reproduce and fix it quickly.

4. Standards

This statement reflects our current efforts toward WCAG 2.1 AA. It is reviewed as the product changes; the "Last updated" date above shows the latest revision.