Este sitio está disponible en español.Ver en español
Skip to content

What works, what does not yet, and how we know.

BeforeJD reads a contract for the person about to sign it, so we want what it returns to be usable by the people who sign. This page says what we measured, the main gaps we know of, and how to reach us.

What we measured

On October 2, 2026 we tested the public site and the signed-in web application. We tested in English and Spanish and in light and dark, with automated rules, scripted keyboard checks and zoom checks.

  • Keyboard

    Every page and state we measured can be used with a keyboard, with the one exception named below. The public site, the sample report and the application each begin with a skip link. The signing pages and the sign-in pages do not have one.

  • Zoom and reflow

    No page needed horizontal scrolling at 320 pixels wide, across 143 public pages and 31 application screens. Text at twice its size clipped nothing new, and pinch zoom is never disabled.

  • Contrast and color

    No reproducible contrast failure appeared in light or dark. Verdicts and statuses are always words, with color as a second cue.

  • Motion

    On the public site, animations finish within five seconds, and none run when a reader has asked the device for reduced motion. We measured this on 47 public pages on September 30, 2026.

  • Language

    Every page declares English or Spanish. The Spanish signing page is served as English and corrected in the browser before it can be used.

  • Signing and signing in

    A signature can be typed or uploaded instead of drawn. Signing in never asks for a puzzle or a test: an emailed link, a passkey, Apple or Google, or a password that a password manager can fill.

  • Voice is optional

    The Contract Assistant can be typed to. The voice conversation starts only when you ask for it, shows a live transcript, and has a control to end it.

On the iPhone, iPad and Mac

The iPhone and iPad app follows the text size a reader sets, up to the largest accessibility size. Five elements stop at the largest standard size, and the report pages shown inside the app scale to about 1.8 times their size. The Mac app scales page text with the Zoom item in the View menu and with a Text size setting. Its sidebar, toolbar and Settings do not scale. Several screens in both apps are the same web pages shown in a web view, so what we measured on the web applies to them.

Screen readers and other assistive technology

No person who uses a screen reader has tested BeforeJD yet, and we have not recorded a VoiceOver, NVDA or JAWS session. Automated rules find a missing name, role or label. They cannot tell us how a page sounds. Until that testing is done, we do not say how BeforeJD works with any particular screen reader.

The main gaps

As of October 2, 2026, the main gaps we know of:

  • Films

    The product tour and the guide films have English captions but no audio description. The product tour has no transcript and no Spanish captions, and we have not checked the captions on the 11 videos from YouTube in Learn.

  • Single-key shortcuts

    The keyboard shortcuts that use one key (N, G then a letter, ?, /, J, K and X) work whenever focus is outside a text field. They cannot yet be turned off or remapped. This applies to the web and to the web pages inside the Mac app.

  • Signature fields

    Placing a signature field in Send for signature needs a pointer, and moving one is a drag. Automatic placement is the keyboard route.

  • Time limits

    The voice assistant ends when its time budget runs out, with the time shown but no warning. Some error messages in organization settings disappear after four seconds.

  • Names and announcements

    The six boxes of the two-factor code share one group label instead of a name each. The status of a file upload and some drafting errors are not announced to a screen reader.

  • Focus under sticky bars

    On a few screens a focused control can sit partly under a sticky bar.

The conformance report below lists every gap we found, with the criterion each one affects.

Tell us about a barrier

If something here does not work for you, write to us. Tell us the page, your device and the assistive technology you use, and what you were trying to do. We answer in English or Spanish, within one business day, Monday through Friday.

[email protected]

Or use the support page.

The conformance report

Our Accessibility Conformance Report follows the VPAT 2.5Rev Revised Section 508 edition, row by row against WCAG 2.0, 2.1 and 2.2 at Level A and AA. It is a self-evaluation: no independent party has audited BeforeJD. We update it as we fix things.

Read the conformance report