Clear guidance
Guided steps should be easy to read, hear, follow, and review while a technician is moving through the job.
Last updated: July 7, 2026
Field work happens in real-world conditions: bright sun, dark mechanical rooms, noisy job sites, gloves, ladders, tablets, phones, and teams with different abilities. CoSkip designs its website and product experiences so more people can understand, navigate, and use them with confidence.
CoSkip is committed to providing an accessible digital experience for technicians, managers, customers, partners, and visitors, including people with disabilities. Our goal is to design and maintain digital experiences that align with Web Content Accessibility Guidelines WCAG 2.2 Level AA where applicable.
Accessibility is an ongoing effort. Some parts of CoSkip may be pre-release, pilot-stage, or dependent on third-party systems, customer configuration, device settings, browser behavior, or assistive technology combinations. When we find barriers, we work to address them in a practical and timely way.
For field teams, accessibility is not only about compliance. It is about whether the work can actually be completed when conditions are imperfect.
Guided steps should be easy to read, hear, follow, and review while a technician is moving through the job.
Buttons, inputs, and workflow actions should be practical on phones and tablets, including field conditions where precision is harder.
Core website experiences should support keyboard navigation, semantic structure, labels, and screen reader-friendly patterns.
Motion should not get in the way of understanding. Focus states should make it clear where a user is on the page.
Photos, notes, exceptions, timestamps, and signoff details should be organized so managers and customers can review work clearly.
CoSkip experiences should be usable on the devices field teams actually carry.
We combine automated checks with manual review because automated testing alone cannot confirm whether an experience is actually usable.
Semantic headings, landmarks, and page structure
Descriptive links and buttons
Text alternatives for meaningful images
Sufficient color contrast
Visible keyboard focus states
Full keyboard navigation for core website flows
Form labels, instructions, and error messages
Screen reader-friendly HTML patterns
Responsive layouts for mobile, tablet, and desktop
Browser zoom and text scaling support
Reduced motion support using prefers-reduced-motion
Avoidance of flashing or distracting animations
Clear target sizes and spacing for interactive controls
Accessible modal and dialog behavior where modals are used
Testing for cookie banner, navigation menus, pilot forms, waitlist forms, calculators, and CTA flows
Clear status and review order
Alternative text and context
Readable exception details
Visible completion state
We aim to support modern browsers and common assistive technology combinations used across desktop and mobile environments. Support may vary by browser, operating system, device, assistive technology version, and customer configuration.
CoSkip is actively evolving. Some pilot-stage, prototype, embedded, or third-party experiences may not yet meet the same accessibility quality bar as our core website pages. We review new components, forms, navigation patterns, and product surfaces as they are introduced.
If you need an alternative format or a practical workaround while we investigate an issue, contact us and we will try to help.
If you experience difficulty accessing CoSkip, notice an accessibility barrier, or need content in another format, please contact us.
We aim to acknowledge accessibility feedback within 5 business days.
For customers evaluating CoSkip, accessibility is part of our broader trust, security, privacy, and product quality process. If your organization needs accessibility information for procurement or vendor review, contact us and include the relevant questionnaire or review requirements. Accessibility review materials may be provided where available.
CoSkip is building AI-guided field work for real job conditions. Start with one workflow, one team, and one clear path to better guidance, better proof, and better closeout.