What we aim for, and where we fall short.

We build XOsign against WCAG 2.2 Level AA. That is the target we design and review to. It is not a certification: no outside body has audited XOsign, and we do not publish a VPAT or claim conformance.

In practice that means keyboard access to every control, visible focus, text alternatives for meaningful images, colour that meets the AA contrast ratios, and a page that still works when text is enlarged.

We last ran our automated check on 15 September 2026 using axe-core 4.13.0, at 1440px and 390px wide, over 16 public pages. Someone also walked the header and mobile menus, the list of questions and the demo door using the keyboard alone.

Problems found

0

Closed since the run before

6

Pages checked

16

Gaps we know of

4

By how serious they are: 0 critical, 0 serious, 0 moderate, 0 minor.

Pages checked: Home, About, Accessibility statement, Compare, Contact, Demo start, Help centre, Industries, Sign in, Platform, Pricing, Security, Create an account, Templates, Trust, Use cases.

The last automated run found nothing on the pages it covers. That is not the same as the product being fully accessible — the gaps below are the ones no automatic checker can see.

Automatic checks catch perhaps a third of what matters. These are the things we know are weak and have not fixed yet.

• Document editor and field placement — Placing a signature or date field on a document is a drag-and-drop action, and the keyboard-only way to do the same thing is incomplete. What we plan to do: Add keyboard placement and movement for every field type, then re-test the whole placement flow without a mouse.
• Signing flow — We have not run a full screen-reader pass over signing with JAWS, NVDA and VoiceOver. Parts of it are announced correctly because they use ordinary controls, not because anyone tested them. What we plan to do: Book a scripted screen-reader run through send, sign and download, and publish what it finds here.
• Customer PDFs — PDFs that customers upload are their own files. We do not add a tag structure or reading order to them, so a scanned or untagged PDF is still untagged after signing. What we plan to do: No fix planned for other people's files; we will document how to supply a tagged PDF instead.
• Whole site — We have not tested the site at 400% zoom or with the Windows high-contrast theme. What we plan to do: Add both to the audit run so they are checked every time rather than once.

If something on XOsign is hard or impossible for you to use, email support@xosign.ai or use the contact form. Tell us what page you were on, what you were trying to do, and what assistive technology you use if any. We reply to every message, and an accessibility report goes to the top of the queue.

If a document is blocking you right now, say so in the subject line. We will get you a usable copy while we fix the cause.

The numbers and the list above are generated from our own audit run and updated by the XOsign team from those results — they are not written by hand. If the last run gets more than 90 days old, our build fails until someone runs it again, so this page cannot quietly go stale.

It sits alongside what we publish about trust, security and compliance.