DBX SIGNAccessibility

Accessibility

What we aim for

We work towards WCAG 2.1 Level AA. We have not engaged an independent accessibility auditor, so what follows is our own assessment of our own product. We would rather publish a truthful one than none at all.

What is in place

• The signing flow is operable by keyboard alone, and focus is visible on every control.
• Controls have accessible names; the brand mark and action buttons carry labels for screen readers.
• Body text and interface colours are chosen for contrast against their own background, and no instruction relies on colour alone.
• Text resizes with the browser, and the layout reflows to a single column on a narrow screen without horizontal scrolling.
• Form fields have real labels, and errors are described in words rather than by a red outline alone.
• No automatically playing media, no content that flashes, and no time limit on reading a document before signing.
• A signer who cannot use the typed or drawn signature tools can be sent the document for wet-ink signature by the sender instead — the sender is told that this is always an option.

Known gaps, stated plainly

• An uploaded PDF is rendered as an image of the page. If the original document is not itself accessible, our rendering of it will not be either. This is the single biggest limitation and it is inherent to every signing platform. Senders should provide an accessible source document where a signer needs one.
• The drag-and-drop field placement in the sender's editor is not fully keyboard-operable yet. It is on the list.
• We have not tested with every assistive technology, and we have no VPAT yet. One is being prepared.

If something does not work

Write to [email protected] with "ACCESSIBILITY" in the subject and tell us what you were trying to do. We will reply within two business days, and if we cannot fix it quickly we will find you another way to get the document signed.