Accessibility statement
We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA on every page. If something gets in your way, email support@trilly.io or see how to tell us.
How the site is built
Navy on white, almost 14 to 1The guidelines ask for 4.5 to 1. Colour never says anything alone: statuses have words.
A clear focus ringOn every link and button you reach with the keyboard.
Works without JavaScriptWhere scripts add comforts, like copy buttons, the page still works without them.
Less motion when you askAnimations and smooth scrolling stop when your device asks for less motion.
Lexend for body textA typeface designed to be easy to read.
What each one means
- Navy on white, almost 14 to 1. The guidelines ask for 4.5 to 1. Colour never says anything alone: statuses have words.
- A clear focus ring. On every link and button you reach with the keyboard.
- Works without JavaScript. Where scripts add comforts, like copy buttons, the page still works without them.
- Less motion when you ask. Animations and smooth scrolling stop when your device asks for less motion.
- Lexend for body text. A typeface designed to be easy to read.
What we test
About 120 kinds of page, automatically, on every change
The same pages at phone width
By hand, before releases that change pages
What each test checks
On every change, automatically. Before any update reaches the site, a test renders about 120 kinds of page through the real app, the public ones and the ones you see once logged in, and checks each one for:
- the page's language and title, one main heading, and headings in order;
- a working "Skip to content" link, and no unusual tab order;
- a text alternative for every image, and a name for every button and link;
- a label for every field, with error messages read out with the field they belong to.
On phones, automatically. The same pages must let you zoom, never scroll sideways at 320 pixels wide, turn tables into cards or let them scroll, and open the menu without JavaScript. Buttons and links are big enough to tap: at least 44 pixels on touch screens.
By hand, before releases that change pages. We go through each changed page with the keyboard only, at 200% zoom and at phone width, with a screen reader (NVDA on Windows and VoiceOver on iPhone), with "reduce motion" switched on, and we check colour contrast.
How we test is written up in full for our team, and the tests run on every change.
What isn't right yet
- A few form hints aren't yet read out with their field (for example, the hint under your name when you join). We fix them as we work on each page.
- We haven't yet checked every page type with the axe accessibility checker, or tried the phone menu on every iPhone and Android phone.
- On public pages that most people see without logging in, the buttons that copy text appear only once you're logged in. Without them, one tap selects the whole text, ready to copy.
- Paying (Stripe's page) and logging in with Google or Microsoft happen on those companies' own pages, which follow their own accessibility commitments.
- Skills ask your AI for clear headings, tables with header rows and no meaning shown by colour alone, but how answers look is up to your AI app.
Tell us about a problem
If any part of Trilly is hard to use, email support@trilly.io or use our contact form. Tell us the page, what you were trying to do, and your device, browser and any assistive technology. We'll reply within two working days, and if you need it, we'll get you the information another way while we fix it.
If you're not happy with our reply and you're in Australia, you can contact the Australian Human Rights Commission. Elsewhere, your country's equality or disability body can help.