Accessibility

We want everyone who directs agents to be able to use Gaitro: on a phone or a laptop, with a keyboard, a screen reader, zoom, or reduced motion.

What we aim for

The Web Content Accessibility Guidelines (WCAG) 2.2 at level AA, across gaitro.com and app.gaitro.com.

What we've done

• Every page can be used with a keyboard alone, starts with a link that skips to its content, and shows where focus is.
• Errors and confirmations are announced to screen readers, and a form that fails keeps what you typed.
• Text and controls meet AA contrast in light and dark mode, and every page works at a phone's width.
• Animations stop when your system asks for reduced motion.
• Checks are written as sentences and changes are summarised in plain words, so nobody has to read code to decide.

What we know isn't there yet

• Side-by-side diffs are wide tables; on small screens they switch to one column, but they're still dense with a screen reader. The plain-words summary above each change says the same thing more simply.
• Syntax colours in code are there to help, not to carry meaning; added and removed lines are also marked with + and −.
• Payment happens on Stripe's checkout page, which Stripe makes accessible, not us.

Automated tests check the skip link, the menus and the announcements on every change. We haven't had an independent audit yet.

Tell us

If anything in Gaitro gets in your way, email info@gaitro.com with the page and what happened. We reply within five working days and tell you when it's fixed.