Deadline Pilot

Our Commitment

NeuralSoft Systems is committed to making Deadline Pilot accessible to everyone, including users who rely on assistive technology. Accessibility is part of our definition of “done” for new features, not an afterthought. We aim to meet or exceed the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA, and we treat the Americans with Disabilities Act (ADA), Section 508, and equivalent international standards (EU Web Accessibility Directive, UK Equality Act) as binding obligations on the public-facing portions of the Service.

Standards We Measure Against

WCAG 2.1, Level AA (Web Content Accessibility Guidelines, W3C Recommendation, 5 June 2018)
WAI-ARIA 1.2 (Accessible Rich Internet Applications, W3C Recommendation, 6 June 2023) for any custom interactive components
U.S. Section 508 Refresh (36 CFR Part 1194), which incorporates WCAG 2.0 AA by reference
EN 301 549 V3.2.1 (European harmonized standard), the reference standard for the EU Web Accessibility Directive

What We Have Done

A skip-to-main-content link is the first focusable element on every page so keyboard and screen-reader users can bypass the navigation.
Every form input has a programmatically-associated label or aria-label; every icon-only button has an aria-label; the cookie banner has role="alert" semantics.
Heading hierarchy is consistent across every page (no skipped levels), and every page has exactly one <h1>.
Every page declares <html lang="en"> so screen readers announce content in the correct voice.
The site uses semantic landmarks (<header>, <nav>, <main>, <footer>) so navigation by landmark works.
Color contrast is checked against the WCAG AA thresholds (4.5:1 for normal text, 3:1 for large text). Brand-gold text on dark navy meets AA; gold-on-white in body copy is avoided.
Lighthouse accessibility audits run automatically on every code change in CI. Any change that drops the public site's accessibility score below 90 is blocked from merging.

Known Limitations

We are honest about what we do not yet meet:

Some PDF documents that you upload may themselves be inaccessible (scanned images, untagged PDFs). We extract their text via OCR, but the source PDF is not modified by us.
Authentication, multi-factor enrollment, and OAuth flows are rendered by Clerk (our identity provider). Clerk's components are independently tested for WCAG 2.1 AA but issues there are reported to Clerk and tracked at clerk.com/docs/accessibility.
Stripe Checkout is hosted by Stripe; their accessibility statement is at stripe.com.

Our Response Timeline

When you report an accessibility barrier:

Within 5 business days: we acknowledge your report by email.
Within 30 days: we respond with either a fix, an accessible workaround, or a written explanation of why we cannot fix it (and what we are doing instead).
Blocking-severity reports (you cannot use the Service at all with your assistive technology) are escalated within 24 hours and we work to provide a workaround within 5 business days.

Report an Accessibility Barrier

If you encountered a problem using Deadline Pilot with your assistive technology, please tell us. The more specific you can be (which page, which element, what you expected vs. what happened), the faster we can fix it.

Alternative Ways to Reach Us

If the form above is not accessible to you, you can email us directly at accessibility@deadlinepilot.com. The form and the email both reach the same inbox; the same response timeline applies.