Accessibility statement
schedule.construction is committed to making construction scheduling usable by people with disabilities. We target Web Content Accessibility Guidelines (WCAG) 2.1 Level AA for our marketing site and application.
This statement describes a self-assessed conformance posture. It is not a third-party certification. Procurement teams may request a fresh Accessibility Conformance Report (ACR) from an independent auditor using our published ACR as a starting point.
Conformance status
As of , we evaluate the product against
WCAG 2.1 AA using automated axe-core scans in Playwright, contrast checks, and a
documented keyboard sample. Detailed criterion ratings are published in our product
repository under docs/accessibility/ACR-WCAG21-AA.md. Email
[email protected]
if you need the current Accessibility Conformance Report (ACR) sent as Markdown or PDF.
Marketing pages, authentication screens, and the schedule ribbon meet our automated AA gates. The interactive Gantt and untagged PDF exports are known partial or non-supporting areas; accessible alternatives are described below.
What this covers
- Marketing site (this domain), including Features and this statement
- Authenticated web app (projects, schedule ribbon, panels, settings, billing shell, admin)
- Owner share links and the offline / PWA shell
- Export paths (SVG, PDF print pack) and documented alternatives
- Third-party dependencies called out in the ACR (Stripe Checkout redirect; Sentry telemetry SDK; self-hosted fonts on this site)
Known limitations
- Interactive Gantt. Bars, many table cells, and resize handles expose labels and keyboard focus, but the virtualized chart is not a full ARIA grid with complete screen-reader row/column navigation.
- PDF exports. Generated PDFs are visual (not tagged). Prefer the HTML share view, SVG export, or browser print of the live page for accessible reading.
- Stripe Checkout. Subscription checkout opens Stripe’s hosted pages; accessibility of that flow is covered by Stripe’s own ACR.
Accessible alternatives
If a barrier blocks your work, email [email protected] with the page or feature, assistive technology you use, and what you need. We will provide a reasonable alternative format (for example a tabular export, share link, or assisted walkthrough) as quickly as we can.
Feedback and contact
Report accessibility barriers to [email protected]. Please include the URL, steps to reproduce, and your browser / assistive technology if known. We aim to acknowledge within two business days.
Compatibility
We design for current evergreen browsers (Chrome, Firefox, Safari, Edge) and commonly used assistive technologies (NVDA with Firefox or Chrome; VoiceOver with Safari). Older browsers and uncommon AT combinations may work but are not part of the formal evaluation sample.
Assessment approach
- Automated WCAG 2.1 A/AA checks with axe-core in CI
- Color contrast verification against WCAG AA ratios
- Manual keyboard checklist on core flows (skip link, ribbon menus, share print)
- Self-attested ACR updated when ratings change
Last reviewed: .