Accessibility
Every party should be able to review and act with intent.
BL Sign targets WCAG 2.2 Level AA for its public and signing interfaces. This is an engineering target, not a third-party certification.
Updated August 31, 2026
What we build and test for
- Semantic headings, landmarks, labels, status announcements, and descriptive controls.
- Keyboard navigation, visible focus, logical focus order, and no pointer-only signing requirement.
- Browser zoom and responsive reflow, readable contrast, reduced-motion support, and information that does not rely on color alone.
- Typed signature and initials as an alternative to drawing, plus accessible names for signing fields.
- Current major browsers and common screen-reader combinations.
Document limitations
Uploaded PDFs come from senders and may not contain tags, reading order, text alternatives, accessible form structure, or usable scanned text. BL Sign’s web controls and completion evidence do not automatically remediate the source PDF. Senders remain responsible for providing an accessible document or equivalent format and an accessible way to review every binding term before signature.
Request an alternative or report a barrier
Email michael@blacklabelbots.com with the page or envelope task, the barrier, your browser or assistive technology if useful, and the format or accommodation you need. Do not include the document or signature in the first message. We will provide a reasonable alternative when available, prioritize the barrier, and verify the repair.
For senders
Before sending, use an accessible source document, write a clear title, place fields in a logical order, identify required fields in text, give recipients enough time, and offer a non-electronic or assisted path when needed. Accessibility requests do not require a signer to disclose a diagnosis.