Accessibility

Version 1.0, approved 2026-09-21. This page may only state conformance that a dated test has shown. No such test has yet been run, so it states the target and the gap, not a conformance level; the table below is filled in when a test is.

Our target

eScryber aims to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA for the pages a signer uses — the signing page, its consent step, and the completion page — and for the sender application. We are not yet able to say that we meet it, because it has not yet been tested in the way that would justify saying so.

What has been tested, and when

Scope	Method	Date	Result
Signing page, sender application	No dated accessibility test yet	—	—

When a test runs, this table will record: the pages covered, the assistive technologies and browsers used (screen reader, keyboard-only, zoom to 200%, high contrast), the automated checker and version, the findings, and what was fixed. Until then the table stays empty rather than implying a result.

What is built with accessibility in mind today

These are design intentions in the code, not tested conformance:

• The interface is built from components that carry keyboard focus, roles and labels by default.
• Field placement and signing are operable by keyboard as well as pointer, and the signing page offers a typed signature as well as a drawn one.
• The mobile signing view reflows document text rather than presenting a shrunken page image, where the document allows it.
• Colour is not the only carrier of meaning for recipient roles and field states; text labels accompany it.
• Emails are sent as HTML with a plain-text alternative.

Known limitations

• PDF documents are rendered as images on the desktop signing page; their text is available to assistive technology only through the reflowed mobile view, and only when that view could be generated for the document.
• Documents supplied by senders may themselves be inaccessible; eScryber does not alter their content.
• Drawing a signature with a pointer is inherently visual; the typed alternative exists for this reason.

Tell us

If something on eScryber does not work with the technology you use, write to accessibility@escryber.com and tell us what you were trying to do, on which page, with what browser and assistive technology. We will reply within 5 business days and, where we cannot fix the barrier quickly, offer another way to complete the task — for a signer, that may mean the sender providing the document another way.

Changes

This page is updated with a new version and date each time a test is run or a limitation changes.