Skip to content

Accessibility statement

Our target is WCAG 2.2 AA on every surface. Here’s where we stand.

This covers the help widget your customers use, the dashboard your team uses and this site. It says how we test, what we build in, and what doesn’t work well yet.

Request the ACRReport a barrier

At a glance

Standard
WCAG 2.2, Level AA
Covers
Widget, dashboard, this site, emails
ACR
Available on request

Scope and status

  • Help widget

    WCAG 2.2 AA

    Launcher, home, guides, Ask, FAQs, glossary, page viewer and contact sheet, in light and dark, under any brand theme

  • Dashboard

    WCAG 2.2 AA

    Every signed-in page at app.glassleaf.ai, including onboarding, review, insights, studio and settings

  • This site

    WCAG 2.2 AA

    Every public page at glassleaf.ai, including the live demo and the executive summary PDF

  • Emails

    WCAG 2.2 AA, where it applies

    Account, invite, processing and weekly digest emails

We won’t write “fully conformant” until an external audit says so.

What stays with you

We can’t make your PDF, your support pages or your brand colours accessible for you. Here’s what we do about each.

Your manual PDF
We flag pages with no text layer at upload, and show the manual’s content as text in the widget.
Your brand colours
A contrast guard adjusts any that fail. The Studio shows each ratio before you save.
Your support pages
The widget doesn’t change them. It keeps its own focus order and never traps keyboard focus.

Known limitations

What doesn’t work well yet, who it affects and what works in the meantime.

  • Diagrams wait for your review before they get a description

    Affects: Screen reader users, in the widget

    Works today: The page’s extracted text, the citation and Talk to a person

    Fix planned.

  • Manual page images can’t reflow

    Affects: People using 400% zoom

    Works today: Zoom buttons on the image, and the extracted text beside it, which reflows

    By design. The image is the source.

  • Untagged manual PDFs

    Affects: People who download the PDF with a screen reader

    Works today: The same content as guides, FAQs and Ask in the widget

    Your file. We flag it at upload.

  • Insights heatmap cells can’t be read one by one

    Affects: Keyboard and screen reader users, in the dashboard

    Works today: View as table shows every value, and it’s in the PDF export

    Fix planned.

  • Google sign-in screens

    Affects: Anyone signing in with Google

    Works today: Email and password sign-in

    Google’s pages, outside our control.

New in WCAG 2.2, and how we design for it

  • 2.4.11 Focus not obscured AA

    Widget: The focused control scrolls clear of the footer and the question box.

    Dashboard: Scroll padding matches the sticky top bar and the bulk action bar.

  • 2.5.7 Dragging movements AA

    Widget: Nothing needs dragging. The page viewer pans with buttons too.

    Dashboard: The PDF dropzone has Choose a file. Module order uses Move up and Move down.

  • 2.5.8 Target size AA

    Widget: Every target is at least 44 × 44 px.

    Dashboard: At least 24 × 24 px; most controls are 32 to 40 px tall.

  • 3.2.6 Consistent help A

    Widget: Talk to a person sits in the same place on every screen.

    Dashboard: Help and contact sit in the account menu on every page.

  • 3.3.7 Redundant entry A

    Widget: Talk to a person can include the conversation, so nobody retypes it.

    Dashboard: The widget key carries from onboarding into the Install tab.

  • 3.3.8 Accessible authentication AA

    Widget: Visitors never sign in.

    Dashboard: Paste and password managers work. No puzzles. Google sign-in is optional.

Contrast across both surfaces: body text 17.6:1, muted text 7.5:1, control edges 3.2:1 on the page ground. Safety notice panels 5.9:1 to 12.9:1. The full table is in the ACR.

How we test

Automated checks
On every change to the widget and dashboard. They find only part of the problems, so testing starts there and doesn’t end there.
Keyboard only
Each release, end to end: sign-up to verified install, review to release and recall, every widget screen.
Screen readers
NVDA with Firefox, JAWS with Chrome, VoiceOver on macOS and iOS, TalkBack on Android.
Zoom, reflow and settings
200% text, 400% zoom, 320 px width, forced colours, reduced motion.
Brand themes
The widget under three sample brands, light and dark, plus a pale-yellow brand that triggers the contrast guard.

Accessibility Conformance Report

Our ACR reports the widget and the dashboard criterion by criterion. It says who tested and when; without a named auditor, it’s our own assessment.

Procurement may also ask about Section 508 in the US or EN 301 549 in the EU. Your legal team decides which apply to you.

Request the ACR

Found a barrier? Tell us.

Email
accessibility@glassleaf.ai

Stuck in a manufacturer’s help widget? Choose Talk to a person there for help today, then tell us about the barrier so we can fix it.