CrewSlate accessibility baseline

Accessibility Statement

CrewSlate is being prepared for supervisor scheduling workflows with an accessibility-first baseline. This statement is implementation evidence, not a lawyer-approved or live-domain compliance claim.

Public and app-shell pages expose a skip link, page landmarks, labeled forms, keyboard-reachable controls, visible focus states, and footer links to Privacy, Terms, Accessibility, and Contact.
CrewSlate targets WCAG 2.2 AA-oriented behavior for headings, labels, contrast, focus indication, keyboard navigation, responsive layout, and reduced personal-data exposure.
Known live-domain blocker: crewslate.com currently resolves to a parked third-party page, so live accessibility compliance cannot be claimed until owner-controlled domain/deploy evidence exists.
Accessibility requests need a monitored owner-approved contact path before production launch; until then, use the project review workflow and include page, browser, assistive tech, and reproduction details.

Reviewer checklist

Before public launch, rerun keyboard, screen-reader, contrast, responsive, and automated axe/Lighthouse-style checks against the owner-controlled production domain, then replace this baseline with the confirmed support contact and effective date.