Keyboard operation
Core navigation and controls are designed for logical tab order, visible focus, and operation without a pointer.
Accessibility
A high-trust product has to work for more people.
ContractPulsar is being designed toward WCAG 2.2 Level AA across public, account, document, pricing, review, and approval workflows.
Accessibility is a release requirement
ContractPulsar does not currently claim third-party conformance certification. Testing and known limitations will be published as the product reaches production readiness.
Interface practices
Accessibility is part of the component system.
These practices guide current implementation and QA. They are tested at desktop, 390-pixel, and 320-pixel widths and will expand to document viewers, spreadsheet editing, signature, and native experiences as those surfaces are built.
Structure and labels
Pages use descriptive titles, landmarks, headings, field labels, status text, and code-native controls.
Contrast and reflow
The design targets readable contrast, responsive reflow, zoom support, and touch controls at least 44 pixels tall.
Motion choice
Motion is intended to support orientation and respect the user’s reduced-motion preference.
Assistive technology and document workflows
Proposal work includes difficult formats: scanned PDFs, government forms, dense spreadsheets, visual schedules, and signed records. The product roadmap includes accessible text alternatives, focus-safe viewers, keyboard editing paths, status announcements, and export checks. A generated PDF is not treated as accessible merely because it opens successfully.
Known pre-release limitations
Advanced document viewers, spreadsheet editors, signing, and native applications are not part of the current foundation. Their accessibility behavior has not yet been validated. This page will identify confirmed limitations and workarounds as those features enter QA.
Tell us where the experience breaks down.
Include the page, the task you were completing, your browser or assistive technology, and the barrier you encountered. Do not attach sensitive proposal content to the first message.