Accessibility Statement

Our commitment

FieldsDesk is designed to be usable by everyone. We target WCAG 2.1 Level AA as our baseline for both the marketing site (fieldsdesk.com) and the FieldsDesk application that customers install on their own servers.

We also aim for compatibility with the Americans with Disabilities Act (Title III) standards as interpreted by U.S. Federal court precedent.

What this means in practice

• Every interactive element is reachable and operable with a keyboard alone.
• Visible focus indicators on every focusable element.
• Text contrast ratio of at least 4.5:1 for body text and 3:1 for large text and UI components.
• Form fields have visible, programmatic labels.
• Icon-only buttons carry an aria-label or screen-reader text.
• Color is never the sole means of communicating information — we pair it with text or icons.
• The interface respects prefers-reduced-motion; animations are reduced or removed when the OS-level setting is on.
• Touch targets are at least 44×44 pixels on mobile.
• Heading hierarchy is preserved (no skipped levels).
• Skip-to-content link as the first focusable element on every page.

How we test

• Automated: axe-core runs against the marketing site and the application's primary user flows in CI on every commit. Any new accessibility violation fails the build.
• Keyboard: we navigate every primary user flow with the keyboard alone.
• Screen reader: we test critical flows with VoiceOver (macOS / iOS) and NVDA (Windows).
• Browser zoom: the layout remains usable at 200% browser zoom without horizontal scrolling.

Known limitations

We're working on these — they're identified, prioritized, and tracked publicly:

• PDF markup canvas: drawing on a PDF (clouds, callouts, measurements) is currently a mouse-and-touch-only interaction. We're investigating keyboard-driven equivalents. ETA Q3 2026.
• Gantt schedule view: the schedule's visual Gantt chart is a complex grid; we expose the same data as an accessible table fallback, but the visual chart itself is not yet fully keyboard-navigable. ETA Q4 2026.

Reporting an issue

If you encounter an accessibility barrier — on the marketing site, in the application, or in any PDF / email FieldsDesk generates — please tell us:

• Email: accessibility@fieldsdesk.com
• GitHub Issues: github.com/fieldsdesk/fieldsdesk/issues (tag: a11y)

We respond to accessibility reports within 3 business days and aim to resolve confirmed issues in the next release.

Self-hosted considerations

FieldsDesk runs on your own server. A few things that affect accessibility are in your hands:

• Your reverse-proxy or domain must serve over HTTPS — assistive technology often refuses to interact with mixed-content pages.
• If you upload your own brand logo, alt text is taken from your company name; make sure it's readable.
• Custom brand colors set in Admin → Branding should be tested for contrast — we surface a warning when the primary color falls below the 4.5:1 ratio against white.