Accessibility

We want everyone working toward a licence to be able to use Gusset. Our target is the Web Content Accessibility Guidelines (WCAG) 2.2, level AA, which also covers WCAG 2.1 AA, the standard Ontario's AODA and the federal Accessible Canada Act point to.

What we do

• Every page is checked by automated accessibility tests (axe, WCAG 2.2 AA) at phone and desktop sizes, in light and dark, each time the site changes, and the accessibility tree of every page is saved and read by a person.
• Everything works from the keyboard, with a visible focus outline. Sheets keep the Tab key inside them and hand focus back when they close.
• Every button, link, image and drawing has a name for screen readers; every form field has a label, and errors are announced.
• Every control takes a tap across at least 44 pixels, even where it looks smaller.
• Text and controls meet AA contrast in both themes, and pages reflow down to 320 pixels wide without sideways scrolling.
• With “reduce motion” on, the 3D story and all animation are replaced with still pictures. The animated story is also given in words for screen readers.
• Talking with Gus shows every word as captions, both Gus's and yours, and you can type instead at any point. The moving sound level next to the mic is decorative; a timer and the words appearing in the box say the same thing in text.
• Topics in Entries are plain buttons that wrap onto new lines, and a competency marked Done says “Done” in words, not only with a line through it.
• No accessibility overlay or widget: the pages themselves are built to be accessible.

Known gaps

• The day grid in Entries is summarised in a sentence for screen readers rather than read square by square.
• Voice notes and talking with Gus need a microphone and a connection; where Gusset's speech service isn't available, voice notes fall back to your browser's own speech recognition, which not every browser has. Typing always works.
• The payment form is provided by Stripe, and the person check on the contact form by Cloudflare; we don't control their accessibility.
• Automated tests don't catch everything. We haven't yet tested with people who use assistive technology every day, and there has been no independent audit.

Tell us

If something doesn't work for you, write to support@gussetlog.com or use Help & contact. Say what you were doing and what you use (browser, screen reader), and we'll answer within five working days.