Accessibility Conformance Report.

A self-evaluation of the BeforeJD web application, iPhone and iPad app and Mac app, in the Revised Section 508 edition of VPAT 2.5Rev. It states what was measured and how, and where a row was not fully measured it says so.

Back to accessibility

Revised Section 508 Edition, based on VPAT® Version 2.5Rev

Name of Product/Version

BeforeJD: the web application and public website at https://beforejd.ai (production as of 2026-10-02); BeforeJD for iPhone and iPad (version 1.0.24); BeforeJD Desktop for macOS (version 1.1.6).

Report Date

2026-10-02

Product Description

BeforeJD reads a contract for the person about to sign it. It returns a plain-language report (Summary, Analysis, Redline and Contract tabs), drafts common contracts from answers, and sends contracts for electronic signature. It is delivered as a web application in English and Spanish, an iPhone and iPad app, and a macOS app. The iPhone, iPad and macOS apps show several screens (the report, drafting and the signing ceremony) as the same web pages inside a web view.

Contact Information

BeforeJD LLC, Houston, Texas. [email protected], https://beforejd.ai/support

Notes

This report is a self-evaluation. BeforeJD evaluated its own products with automated testing tools, scripted keyboard and zoom checks, and a review of the source code. No independent third party audited the products, and no person who uses assistive technology took part. Each remark states what was measured and how. Where a criterion was not fully measured, the conformance level says so rather than assuming support.
"Web" covers the public website and the signed-in web application, in English and Spanish, in light and dark appearance. "iOS" covers the iPhone and iPad app. "macOS" covers the desktop app. Where an app screen is the web page in a web view, the Web remarks apply to it.
The native apps were evaluated from their source code at the commit below and from their automated accessibility tests. The live store versions are 1.0.24 (iOS) and 1.1.6 (macOS); a native change made after those versions may not yet be in users' hands.
WCAG 2.1 and 2.2 success criteria are reported beyond the WCAG 2.0 criteria that Section 508 incorporates, as the 2.5Rev template allows. 4.1.1 Parsing is reported as WCAG 2.2 treats it.

Evaluation Methods Used

All measurements were taken on 2026-10-02 against production (https://beforejd.ai) and against a preview build of the same code (commit 5933bf03c, which differs from production main only in a test file). The scripts are in the repository at scripts/compliance/wcag-measure.mjs and scripts/scorecard/public-floor.mjs.

Automated rules (axe-core 4.12). WCAG 2.0, 2.1 and 2.2 A and AA rules, target size included, every impact level recorded:
- every public page in the sitemap plus the sample report, sign-in and password reset, 143 pages, in light and dark;
- 31 signed-in screens rendered by the application's test harnesses, in English and Spanish, light and dark (62 page loads each way);
- the continuous-integration gates, which fail any serious or critical violation: 24 public routes, 18 signed-in screens in light and dark, and 18 states of the signing ceremony on Chrome and WebKit.
Keyboard. On every page above, a scripted keyboard pass of up to 60 Tab stops records the first stop, any stop without a visible focus indicator, any stop hidden under a fixed or sticky layer, and any trap. Dialog focus handling is covered by the continuous-integration suite.
Zoom, reflow and text spacing. Each page at 320 CSS pixels wide (horizontal overflow), with text at 200 percent, and with the WCAG 1.4.12 spacing overrides, recording any text box that clips.
Contrast. axe color-contrast in light and dark; form-field boundaries measured from computed styles (3.04:1 light, 3.01:1 dark).
Media. Every video, audio and embedded player found on the pages, and whether it carries captions; transcript and audio description by source review.
Native apps. Source review of accessibility labels, traits, Dynamic Type, Reduce Motion and other display settings, keyboard commands and the apps' automated accessibility audits (performAccessibilityAudit on iOS; accessibility unit tests on macOS).
Not performed. No session with a person using assistive technology. No VoiceOver session was recorded on iOS or macOS, and no NVDA or JAWS session on Windows (no Windows device was available). Criteria that depend on screen-reader output are therefore not reported as "Supports" for the native apps.

Applicable Standards/Guidelines

Web Content Accessibility Guidelines 2.0, 2.1 and 2.2

Included In Report: Level A (Yes), Level AA (Yes), Level AAA (No)

Revised Section 508 standards published January 18, 2017 and corrected January 22, 2018

Included In Report: Yes

Terms

Supports: the functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation.
Partially Supports: some functionality of the product does not meet the criterion.
Does Not Support: the majority of product functionality does not meet the criterion.
Not Applicable: the criterion is not relevant to the product.

WCAG 2.x Report

Table 1: Success Criteria, Level A

1.1.1 Non-text Content

Conformance Level: Partially Supports
Remarks and Explanations: Web: Supports. No image-alt, input-image, svg or button-name violation on any page or state measured. iOS: Partially Supports. Images are labeled or hidden from VoiceOver, but one image in scanned-page review opens on tap without a label or button trait, and no VoiceOver session was recorded. macOS: Partially Supports. The sidebar and toolbar are labeled; the menu bar extra has no accessibility labels; no VoiceOver session was recorded.

1.2.1 Audio-only and Video-only (Prerecorded)

Conformance Level: Supports
Remarks and Explanations: Web: no prerecorded audio-only or video-only content. Animations are decorative. iOS and macOS: Not Applicable (no media).

1.2.2 Captions (Prerecorded)

Conformance Level: Partially Supports
Remarks and Explanations: Web: the product tour film and the guide films carry English captions (<track kind="captions">). The 11 videos embedded from YouTube on the Learn pages were not verified for captions. The tour has no Spanish captions on Spanish pages. iOS and macOS: Not Applicable.

1.2.3 Audio Description or Media Alternative (Prerecorded)

Conformance Level: Partially Supports
Remarks and Explanations: Web: guide films have a full transcript. The product tour film has neither a transcript nor audio description. iOS and macOS: Not Applicable.

1.3.1 Info and Relationships

Conformance Level: Partially Supports
Remarks and Explanations: Web: Partially Supports. Landmarks, headings, lists, tables and form labels pass automated rules on every page measured. Drafting-wizard field errors are plain text with no programmatic tie to their field, and the six digit boxes of the two-factor code share one group label with no name each. iOS: Partially Supports. Headings carry the header trait; no VoiceOver session was recorded. macOS: Partially Supports, for the same reason.

1.3.2 Meaningful Sequence

Conformance Level: Supports
Remarks and Explanations: Web: reading and Tab order follow the visual order on every page measured. iOS and macOS: layout order follows source order; not verified with VoiceOver.

1.3.3 Sensory Characteristics

Conformance Level: Supports
Remarks and Explanations: Instructions name the control they refer to. Where copy says "above" or "below", it names the labeled control as well; the two references to an icon also give a text path.

1.4.1 Use of Color

Conformance Level: Supports
Remarks and Explanations: Verdicts, severities and statuses are always words, with color as a second cue. Links in text are underlined.

1.4.2 Audio Control

Conformance Level: Supports
Remarks and Explanations: Web: no audio plays without the person starting it; videos use native controls. The voice assistant starts only on request and has an end control. iOS and macOS: the same assistant.

2.1.1 Keyboard

Conformance Level: Partially Supports
Remarks and Explanations: Web: Partially Supports. Every page and state measured can be operated by keyboard, except the signature-field editor in Send for signature: placing a field is a click on the page and moving it is a drag, with no keyboard method (automatic field placement is the keyboard route). iOS: Partially Supports. The iPad has keyboard commands for its main destinations; full keyboard operation was not verified. macOS: Partially Supports. Menus and keyboard commands cover the main actions; Full Keyboard Access was not verified, and the web-page gap above applies.

2.1.2 No Keyboard Trap

Conformance Level: Supports
Remarks and Explanations: Web: no trap on any page measured; dialogs return focus on Escape (tested in continuous integration). iOS and macOS: none known; not verified with a hardware keyboard pass.

2.1.4 Character Key Shortcuts

Conformance Level: Does Not Support
Remarks and Explanations: Web and macOS (web pages): single-key shortcuts (N, G then a letter, ?, /, J, K, X) act whenever focus is outside a text field. They cannot be turned off or remapped. iOS: Supports (iPad commands use the Command key).

2.2.1 Timing Adjustable

Conformance Level: Partially Supports
Remarks and Explanations: Web: Partially Supports. Sign-in links, signing codes and signing links can be requested again. Some error messages in organization settings appear as notices that vanish after 4 seconds with no pause. The voice assistant ends when its time budget runs out, with the time shown but no warning or extension. iOS: Partially Supports (the same assistant). macOS: Supports for the native app; its Touch ID lock after 15 minutes idle is a security timeout, with a password fallback. The web-page items above apply inside the window.

2.2.2 Pause, Stop, Hide

Conformance Level: Supports
Remarks and Explanations: Animations finish within 5 seconds, and none run under Reduce Motion (measured on 47 public pages on 2026-09-30). Videos have native pause. Loading placeholders animate only while loading.

2.3.1 Three Flashes or Below Threshold

Conformance Level: Supports
Remarks and Explanations: No flashing content. Theme changes are resolved before first paint (measured frame by frame on 2026-10-01).

2.4.1 Bypass Blocks

Conformance Level: Supports
Remarks and Explanations: Web: every page has landmarks; the public site, sample report and application have a skip link as the first Tab stop (measured). The signing ceremony, sign-in pages and phone pages have landmarks but no skip link. iOS and macOS: Not Applicable to the native screens (WCAG2ICT).

2.4.2 Page Titled

Conformance Level: Supports
Remarks and Explanations: Web: every page measured has a descriptive title in its language. macOS: the window shows the page title. iOS: screens carry navigation titles.

2.4.3 Focus Order

Conformance Level: Supports
Remarks and Explanations: Web: the first Tab stop is the skip link, and the order follows the page on every page measured; dialogs move focus in and return it. iOS and macOS: not verified with VoiceOver or a hardware keyboard.

2.4.4 Link Purpose (In Context)

Conformance Level: Partially Supports
Remarks and Explanations: Web: link names pass automated rules on every public page. The header's reads-balance link has no accessible name while the balance is still loading (found on the report screens). iOS and macOS: links are labeled buttons; not verified with VoiceOver.

2.5.1 Pointer Gestures

Conformance Level: Supports
Remarks and Explanations: No action needs a multipoint or path gesture. A signature can be typed or uploaded instead of drawn. Pinch zoom in the iOS signing ceremony is optional.

2.5.2 Pointer Cancellation

Conformance Level: Supports
Remarks and Explanations: Controls are native buttons and links that act on release. The field editor places a field on click.

2.5.3 Label in Name

Conformance Level: Supports
Remarks and Explanations: Web: axe label-content-name-mismatch is enabled and finds nothing on any page measured. iOS and macOS: visible labels are the accessible names in the evidence reviewed; not verified with VoiceOver.

2.5.4 Motion Actuation

Conformance Level: Not Applicable
Remarks and Explanations: No function is triggered by device motion.

3.1.1 Language of Page

Conformance Level: Supports
Remarks and Explanations: Web: every page declares English or Spanish (measured). The Spanish signing ceremony is served as English and corrected in the browser before it can be used. iOS and macOS: follow the system language.

3.2.1 On Focus

Conformance Level: Supports
Remarks and Explanations: No change of context on focus: the keyboard pass never left a page.

3.2.2 On Input

Conformance Level: Supports
Remarks and Explanations: No select, radio button or switch changes the context when its value changes. Settings save in place; the language is changed with links; sort and filter controls re-render the same page.

3.2.6 Consistent Help

Conformance Level: Supports
Remarks and Explanations: Web: Contact and Support sit in the same place in the footer on every public page. In the application, help appears on the Settings page only. The signing ceremony points the signer to the sender.

3.3.1 Error Identification

Conformance Level: Supports
Remarks and Explanations: Errors are described in text next to the field or in a margin note. See 1.3.1 and 4.1.3 for how some are exposed to assistive technology.

3.3.2 Labels or Instructions

Conformance Level: Partially Supports
Remarks and Explanations: Web: fields have visible labels (axe label passes everywhere measured). The six two-factor digit boxes have one group label and no label each, and that page is not in the automated gates. iOS and macOS: fields are labeled.

3.3.7 Redundant Entry

Conformance Level: Supports
Remarks and Explanations: An adopted signature or initials is reused across every field in a signing ceremony. No process asks for the same information twice.

4.1.1 Parsing

Conformance Level: Supports
Remarks and Explanations: WCAG 2.2 treats this criterion as always satisfied for HTML. No duplicate-ID or ARIA-attribute violation in production pages; one harness-only page tied a tab to a panel it did not render.

4.1.2 Name, Role, Value

Conformance Level: Partially Supports
Remarks and Explanations: Web: Partially Supports. Name, role and value pass automated rules on every production page and gate. The exception is the reads-balance link with no name while loading (2.4.4). iOS and macOS: Partially Supports. Standard controls expose name, role and state through the platform; custom controls are labeled where reviewed; no VoiceOver session was recorded.

Table 2: Success Criteria, Level AA

1.2.4 Captions (Live)

Conformance Level: Not Applicable
Remarks and Explanations: No live synchronized media. The voice assistant is a two-way conversation with a live transcript on screen.

1.2.5 Audio Description (Prerecorded)

Conformance Level: Does Not Support
Remarks and Explanations: Web: the product tour and guide films have no audio description track and no described version. iOS and macOS: Not Applicable.

1.3.4 Orientation

Conformance Level: Supports
Remarks and Explanations: iOS: iPhone and iPad run in every orientation. Web: no page locks orientation; the optional landscape view in the slide viewer opens only when the person asks for it. macOS: Not Applicable.

1.3.5 Identify Input Purpose

Conformance Level: Partially Supports
Remarks and Explanations: Web: sign-in, password, two-factor, contact and profile fields carry the correct autocomplete tokens. Gaps: the waitlist email field has none, and the profile street address uses a token that does not match a single-line field. iOS: sign-in, password and code fields carry content types; the profile's name, phone, ZIP, company and title fields do not. macOS: uses the web forms.

1.4.3 Contrast (Minimum)

Conformance Level: Supports
Remarks and Explanations: Web: no color-contrast violation in light or dark on any production page or harness screen measured. One mid-deploy scan of the Spanish home page saw three contrast nodes that three re-scans did not reproduce. iOS and macOS: color pairs are checked by unit tests (primary actions and brand pairs); web views follow the web result.

1.4.4 Resize Text

Conformance Level: Partially Supports
Remarks and Explanations: Web: Supports. Text at 200 percent clips nothing new on any page measured, and pinch zoom is never disabled. iOS: Partially Supports. Native text follows Dynamic Type to the largest accessibility size, but five elements stop at the largest standard size (the brand lockup, page standfirsts, a Signatures row, the assistant buttons, which offer the Large Content Viewer). Web views scale to about 179 percent at the largest size, against 312 percent for native text, with pinch zoom available. macOS: Partially Supports. Page text scales with View > Zoom and a Text size setting; the native sidebar, toolbar and Settings do not scale.

1.4.5 Images of Text

Conformance Level: Supports
Remarks and Explanations: Text is text. The brand lockup is a logotype.

1.4.10 Reflow

Conformance Level: Supports
Remarks and Explanations: Web: no horizontal scrolling at 320 CSS pixels on any of the 143 public pages or the 31 application screens measured, in English and Spanish. iOS: layouts restack at accessibility text sizes. macOS: Not Applicable to native windows (minimum window size); web pages follow the web result.

1.4.11 Non-text Contrast

Conformance Level: Supports
Remarks and Explanations: Form-field borders measure 3.04:1 (light) and 3.01:1 (dark) against the field. Focus indicators are the accent outline. Verdict meter segments are paired with the verdict in words.

1.4.12 Text Spacing

Conformance Level: Partially Supports
Remarks and Explanations: Web: with the WCAG spacing overrides, no text box clips on any page measured (143 public pages and 31 application screens). Single-line names in lists (for example contract titles) end in an ellipsis by design. More spacing shortens what is visible; the full name is on the record page. iOS and macOS: Not Applicable to native text (no author-level spacing control); web views follow the web result.

1.4.13 Content on Hover or Focus

Conformance Level: Supports
Remarks and Explanations: No content appears on hover alone. Explanations open on click and close with Escape; row actions that show on hover also show on keyboard focus; notices pause while hovered or focused.

2.4.5 Multiple Ways

Conformance Level: Supports
Remarks and Explanations: Web: navigation, search (with Command K in the application), the footer and the sitemap. iOS and macOS: tabs or sidebar, and search.

2.4.6 Headings and Labels

Conformance Level: Supports
Remarks and Explanations: Web: exactly one first-level heading and no skipped levels on public pages; descriptive form labels. iOS and macOS: headings carry the header trait where present; not verified with VoiceOver.

2.4.7 Focus Visible

Conformance Level: Partially Supports
Remarks and Explanations: Web: Supports. Every Tab stop on the 143 public pages and the 62 application screen loads draws a visible focus indicator. iOS: Partially Supports. Hardware-keyboard focus on native screens was not verified. macOS: Partially Supports. Native views rely on the system focus ring, which was not verified with Full Keyboard Access.

2.4.11 Focus Not Obscured (Minimum) (WCAG 2.2)

Conformance Level: Partially Supports
Remarks and Explanations: Web: the scripted keyboard pass found one control partly hidden by a sticky bar ("Copiar la solicitud" on the Spanish sample report) across 143 public pages and 62 application screen loads. Sticky headers, the report tab bar and the signing ceremony's bottom bar have no scroll padding, so a focused control can sit partly under them. iOS and macOS: not verified.

2.5.7 Dragging Movements (WCAG 2.2)

Conformance Level: Supports
Remarks and Explanations: Moving a signature field by drag has a single-pointer alternative: remove it and click where it belongs. File upload has a Browse button beside drag and drop.

2.5.8 Target Size (Minimum) (WCAG 2.2)

Conformance Level: Partially Supports
Remarks and Explanations: Web: Supports. axe target-size finds no target under 24 by 24 CSS pixels (or without the spacing that substitutes for it) on the 143 public pages or the 31 application screens, in light and dark. iOS: Partially Supports. The app's own accessibility audit flagged four hit areas as too small by Apple's measure (one tab bar item and three filter chips); their size against the 24-pixel WCAG minimum was not measured. macOS: standard controls; not measured.

3.1.2 Language of Parts

Conformance Level: Partially Supports
Remarks and Explanations: Web: untranslated blog posts on Spanish pages are marked English. On the Spanish sample report, clauses quoted from the English contract are not marked English, nor are redline text and drafted replacement clauses. iOS and macOS: the same web pages.

3.2.3 Consistent Navigation

Conformance Level: Supports
Remarks and Explanations: The navigation is in the same order on every page of the public site and of the application.

3.2.4 Consistent Identification

Conformance Level: Partially Supports
Remarks and Explanations: The same function has two names in places within the web application: starting a read is "New analysis" in the navigation and "Analyze a contract" in the Contracts empty state.

3.3.3 Error Suggestion

Conformance Level: Supports
Remarks and Explanations: Error text says what to do (for example, request a new code, or the format expected).

3.3.4 Error Prevention (Legal, Financial, Data)

Conformance Level: Supports
Remarks and Explanations: Signing needs an explicit "I agree and sign" after review, and declining is confirmed. Purchases go through a review step. Deleting the account needs the account's email typed in.

3.3.8 Accessible Authentication (Minimum) (WCAG 2.2)

Conformance Level: Supports
Remarks and Explanations: Sign-in by an emailed link, a passkey, Apple or Google, or a password that can be pasted or filled by a password manager. Two-factor codes accept paste and autofill. The sign-in check (Cloudflare Turnstile, interaction-only) is not a puzzle or a cognitive test.

4.1.3 Status Messages

Conformance Level: Partially Supports
Remarks and Explanations: Web: results, saves, progress and errors use live regions in most places. File-selected and upload status, and drafting-wizard field errors, are not announced. iOS: announcements on sign-in, two-factor, offline and envelope screens. macOS: not verified.

Revised Section 508 Report

Chapter 3: Functional Performance Criteria (FPC)

302.1 Without Vision

Conformance Level: Partially Supports
Remarks and Explanations: Web structure and names pass automated rules throughout; no screen-reader session was recorded on any platform. Gaps in Tables 1 and 2 (1.3.1, 4.1.2, 4.1.3) apply.

302.2 With Limited Vision

Conformance Level: Partially Supports
Remarks and Explanations: Zoom and reflow hold on the web; some native elements do not scale (1.4.4).

302.3 Without Perception of Color

Conformance Level: Supports
Remarks and Explanations: Color is never the only cue (1.4.1).

302.4 Without Hearing

Conformance Level: Partially Supports
Remarks and Explanations: Captions on the tour and guide films; embedded YouTube videos not verified (1.2.2). The voice assistant shows its transcript, and the typed assistant is the primary path.

302.5 With Limited Hearing

Conformance Level: Partially Supports
Remarks and Explanations: As 302.4.

302.6 Without Speech

Conformance Level: Supports
Remarks and Explanations: Speech is never required; the assistant can be typed to.

302.7 With Limited Manipulation

Conformance Level: Partially Supports
Remarks and Explanations: Signature-field placement needs a pointer (2.1.1), and single-key shortcuts cannot be turned off (2.1.4).

302.8 With Limited Reach and Strength

Conformance Level: Supports
Remarks and Explanations: No action needs reach, strength or a timed grip.

302.9 With Limited Language, Cognitive, and Learning Abilities

Conformance Level: Supports
Remarks and Explanations: Plain-language reports in English and Spanish, consistent navigation, and sign-in without a cognitive test.

Chapter 4: Hardware

Not Applicable. BeforeJD is software.

Chapter 5: Software

501.1 Scope

Conformance Level: See WCAG 2.x section
Remarks and Explanations: The web application is evaluated under WCAG. The rows below cover the iOS and macOS apps.

502.2.1 User Control of Accessibility Features

Conformance Level: Supports
Remarks and Explanations: The apps do not change platform accessibility settings.

502.2.2 No Disruption of Accessibility Features

Conformance Level: Supports
Remarks and Explanations: The apps do not disable or override platform accessibility features.

502.3.1 to 502.3.14 Interoperability with Assistive Technology

Conformance Level: Partially Supports
Remarks and Explanations: Standard SwiftUI and AppKit controls expose name, role, state, value, text, focus and actions through the platform accessibility APIs, and custom controls are labeled where reviewed. Gaps: one unlabeled image control (1.1.1), few custom accessibility actions, no recorded VoiceOver session.

502.4 Platform Accessibility Features

Conformance Level: Partially Supports
Remarks and Explanations: iOS honors text size, appearance and (in eight places) Reduce Motion. It does not read Increase Contrast, Reduce Transparency, Bold Text or Differentiate Without Color, and some animations ignore Reduce Motion. macOS honors Reduce Motion and appearance, not Increase Contrast or Reduce Transparency.

503.2 User Preferences

Conformance Level: Partially Supports
Remarks and Explanations: As 502.4. macOS native text does not follow a system text size (macOS has none for apps), and the in-app Text size setting scales page content only.

503.3 Alternative User Interfaces

Conformance Level: Not Applicable
Remarks and Explanations: The apps do not provide an alternative interface that functions as assistive technology.

503.4 User Controls for Captions and Audio Description

Conformance Level: Supports
Remarks and Explanations: Web videos use native player controls with a captions toggle. The apps have no video.

504 Authoring Tools

Conformance Level: Partially Supports
Remarks and Explanations: Drafting produces Word and PDF contracts. The tagging and structure of those files for assistive technology were not evaluated in this report.

Chapter 6: Support Documentation and Services

601.1 Scope

Conformance Level: Heading cell, no response required

602.2 Accessibility and Compatibility Features

Conformance Level: Partially Supports
Remarks and Explanations: https://beforejd.ai/accessibility (English and Spanish) describes what was measured for keyboard, zoom, contrast, motion and language, the known gaps, the apps' text-size behavior, and how to report a barrier, and links this report. It does not yet explain how to use the product's own accessibility features, such as the keyboard shortcuts, the text size setting on macOS or the appearance setting.

602.3 Electronic Support Documentation

Conformance Level: Supports
Remarks and Explanations: The Support page, Learn guides and help content are web pages measured under the WCAG section.

602.4 Alternate Formats for Non-Electronic Support Documentation

Conformance Level: Not Applicable
Remarks and Explanations: No non-electronic documentation.

603.2 Information on Accessibility and Compatibility Features

Conformance Level: Supports
Remarks and Explanations: Support points people to https://beforejd.ai/accessibility and this report, and takes barrier reports at [email protected] in English or Spanish.

603.3 Accommodation of Communication Needs

Conformance Level: Supports
Remarks and Explanations: Support is by email and web form, in English and Spanish.

Legal Disclaimer (BeforeJD LLC)

This report describes the conformance of the products named above as measured on the report date. It is provided for information. BeforeJD LLC works to close every gap listed here and will update this report as products change.