Accessibility Statement

Conformance standard

We conform to the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA, as required by the United States Department of Justice ADA Title II Final Rule (April 2024). We test against this standard using automated tools, manual keyboard navigation, screen reader testing, and color-contrast verification.

Where practical, we also adopt improvements from WCAG 2.2 Level AA (such as 24×24 pixel touch targets) as forward-compatible best practices.

What this means for you

• Every interactive element is reachable and operable using a keyboard alone.
• Screen readers (VoiceOver, NVDA, JAWS, TalkBack) announce content, interactive controls, and dynamic updates.
• Color contrast on body text meets or exceeds a 4.5:1 ratio. Color is never the only way information is conveyed.
• Forms have clear visible labels, and error messages are announced to assistive technology.
• Pages remain functional and readable at 200% zoom.
• Motion-based animations honor the prefers-reduced-motion setting.
• Documents, forms, and public media published by ClockIn are designed to be accessible. If we ever host videos, they are captioned; if we ever host PDFs, they are tagged and structured for screen readers.

Where we're still improving

Accessibility is an ongoing commitment, not a one-time checkbox. We audit the platform regularly and maintain a public list of known issues with remediation timelines. If you encounter something that doesn't meet the standard, please let us know so we can fix it.

Report an accessibility issue

Email accessibility@clockin.jobs. When reporting, please include:

• The page or feature where you ran into the issue
• What you were trying to do
• What happened instead
• Your browser, operating system, and assistive technology (if applicable)

Our commitment: we acknowledge every report within one business day. We remediate most issues within 30 days. Complex issues may take up to 90 days, and in those cases we communicate an interim workaround. Accessibility reports are treated at the same priority as security reports.

Ongoing monitoring

• Automated accessibility linting runs in our continuous integration pipeline and blocks code merges on detected issues.
• Developers receive real-time accessibility warnings via in-browser tooling during development.
• Manual screen reader testing is required before every new feature ships.
• We conduct periodic (quarterly) full-platform accessibility audits and publish updates to this statement as our conformance posture evolves.

Third-party content

Content posted by employers (job descriptions, company information) is authored by those employers. We require employers to follow accessibility best practices when writing listings (clear language, structured information, descriptive titles), and we provide in-product guidance to that end. If you encounter employer-authored content that is inaccessible, please report it using the contact above and we will work with the employer to address it.