Accessibility Statement

1. Our commitment

Unify is committed to making our platform accessible to all users, including those who rely on assistive technology. We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA, the international standard for digital accessibility. Accessibility is a continuous process for us, not a one-time checklist — we treat it as part of how we build, not an afterthought.

2. Conformance status

Unify is currently partially conformantwith WCAG 2.1 Level AA. "Partially conformant" means some parts of the content do not yet fully meet the standard.

We want to be honest about where we are: Unify is a young product, and we have not yet completed a full third-party accessibility audit. We are actively working toward full conformance and prioritizing fixes as we identify them.

3. What we've done so far

The following accessibility practices are in place today:

Semantic HTML throughout — meaningful headings, landmarks, lists, and form elements rather than generic divs.
Keyboard navigation is supported across our primary flows, including signup, login, dashboard navigation, and the job application process.
Color contrast on primary text and interactive elements meets WCAG AA minimum ratios.
Form fields have associated labels so screen readers can announce what each input is for.
Buttons and icons have aria-labelswhere visible text isn't present. A recent audit pass added explicit labels to back buttons and toggle switches; the rest of the app has matching coverage from our build conventions.
Focus indicators are visible on interactive elements when navigating by keyboard.
Alt text on meaningful images. Placeholder and decorative graphics are explicitly marked as decorative so screen readers skip them.
Modals and dialogs support focus management — focus moves into the dialog on open and returns to the trigger on close.

4. Known limitations

We want to be straightforward about areas where we know we fall short today:

The contractor's geo-fenced check-in screen relies on map visuals; alternative text descriptions for screen readers are limited.
Some PDF document previews shown to admins during review aren't fully accessible — the PDFs themselves may not be tagged for assistive technology.
Mobile app accessibility (Android live; iOS coming) has had less testing than the web experience. We're actively improving it.
Some complex interactive components (e.g., drag-to-reorder) may have keyboard alternatives that are functional but not optimal. We're iterating on these.

5. Compatible assistive technology

We regularly test Unify with the following assistive technology and browser combinations:

The latest two versions of NVDA on Windows
VoiceOver on macOS Safari and iOS Safari
TalkBack on Android Chrome
Keyboard-only navigation in Chrome, Firefox, Safari, and Edge

6. Standards we follow

Our primary reference is WCAG 2.1 Level AA. We also evaluate applicable WCAG 2.2 enhancements and adopt them where appropriate as the specification matures and tooling support stabilizes.

7. Reporting accessibility issues

If you encounter an accessibility barrier on Unify, please tell us. Email accessibility@weunify.io (or support@weunify.io if that address doesn't reach us yet). To help us investigate quickly, include:

The page URL or app screen where you ran into the issue
What you were trying to do
What actually happened, and what you expected to happen
Your assistive technology, browser, and device (e.g., "NVDA 2025.1 on Chrome 130, Windows 11")

We commit to acknowledging accessibility reports within 5 business days and working in good faith to remediate the issue.

8. Last reviewed

This statement was last reviewed on June 28, 2026.

9. Continuous improvement

We review accessibility on every major release. Material changes to this statement are dated at the top of the page. If you have feedback on how we can improve the experience for users of assistive technology, we'd genuinely like to hear it — we read every report.