Accessibility

1. The standard we aim for

We use WCAG 2.1 Level AA as our target. It is the standard most widely referenced for websites, including under the Americans with Disabilities Act, and it is what we measure ourselves against.

This is a statement of partial conformance: most of RouteWrk meets that standard, and the parts that do not are listed in section 3. Section 2 describes what has been measured.

2. What we have done

As of August 1, 2026, across our public pages:

• Text contrast. Every text colour on these pages was measured against the background it is actually painted on and adjusted to meet the 4.5:1 minimum (3:1 for large text).
• Form labels. Every field on our sign-in, sign-up, password-reset and contact forms has a label a screen reader can announce, rather than placeholder text alone.
• Keyboard operation. Menus and controls in the site header can be reached and operated with a keyboard, and Escape closes any open menu.
• Visible focus. The element you are on is always outlined, so you can see where you are while tabbing.
• Skip to content. A skip link is the first thing you reach on every page, so you do not have to tab through the whole navigation to get to what you came for.
• Zoom and reflow. Pages work down to a 360px-wide screen and do not block pinch-zoom.
• Reduced motion. Scrolling animation is turned off if your system asks for reduced motion.

3. Where RouteWrk does not yet conform

Two areas fall outside the conformance described above. If either affects you, section 4 is how we work around it with you in the meantime.

• The workflow canvas requires a pointing device. Building a workflow means dragging nodes onto a canvas and drawing connections between them, and that interaction is not currently operable by keyboard alone. Everything a workflow produces (tickets, approvals, the board, email) is reachable without it. If you need a workflow built or changed, contact us and we will do it with you.
• The signed-in application is measured to a lower standard than these public pages. The colour, focus and labelling systems are shared, so improvements to the public pages apply there too, but the application has not been assessed screen by screen. Report anything you hit and we will treat it the same way.

4. Tell us about a barrier

If any part of RouteWrk is difficult or impossible for you to use, we want to hear about it. This is the fastest way for us to find problems our tooling cannot. Reach us through our contact form.

Tell us the page or screen, what you were trying to do, and what you use to browse (for example, "NVDA on Firefox" or "keyboard only") if you are comfortable sharing it. We aim to reply within five business days, and we will tell you plainly whether we can fix it, and roughly when.

If something you need is blocked by one of the two areas in section 3, tell us what you are trying to do and we will find another way to get it done.

5. How this was assessed

Our public pages are measured with an automated pass that loads each page in a real browser and checks the computed colour of every piece of text against the background actually painted behind it, the label relationship of every form control, and whether interactive elements can be reached by keyboard. That pass runs against every public route.

Those measurements are paired with manual keyboard testing. What they do not include is testing with people who use assistive technology daily; roughly a third of WCAG criteria call for human judgement that no automated check replaces. Section 3 lists the areas we know fall short; section 4 is how you tell us about anything we have missed.