Accessibility Statement

Perchpoint LLC (“Perch”) is committed to making its scheduling product usable by as many people as possible, including people who rely on assistive technologies. Accessibility is an ongoing effort, and we treat it as a first-class part of how we design and build — not an afterthought.

We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA, and to align with the requirements of the Americans with Disabilities Act (ADA), Section 508, and EN 301 549.

Perch’s current conformance is self-assessed against WCAG 2.1 AA. We have not yet completed an independent third-party accessibility audit, and we are transparent about that. If you have accessibility questions or need assistance, email accessibility@onperch.co.

What we do today across the product:

• Accessible component foundation. Interactive controls (menus, dialogs, popovers, tooltips, switches, tabs) are built on an accessibility-first component library that ships keyboard interaction, focus management, and ARIA roles/states by default.
• Semantic structure. Pages use semantic HTML and heading hierarchy, landmarks, and labeled form fields so screen readers can navigate and announce content meaningfully.
• Keyboard operability. Core flows are operable by keyboard, with visible focus indicators on interactive elements.
• Color and contrast. Colors come from a fixed design-token palette chosen for legibility; status and meaning are not conveyed by color alone (icons, labels, and text reinforce it).
• Responsive & zoom. Layouts reflow and remain usable when zoomed and across screen sizes; viewing the schedule and clocking in/out are supported on small and touch devices.
• Text alternatives. Meaningful images and avatars carry text alternatives; decorative elements are hidden from assistive technology.

We’re honest about where we’re still improving. Known areas as of the date above:

• Schedule authoring grid. Building schedules is a rich, spatial drag-and-drop experience designed for a wide screen and pointer. On small or touch devices we intentionally provide a streamlined, view-and-light-actions experience rather than full authoring. We are working to broaden keyboard- and screen-reader-only paths for complex grid editing.
• Not yet independently audited. Our conformance is self-assessed; we have not yet completed a formal third-party audit.
• Embedded third-party flows. Sign-in and payment screens are served by our sub-processors (authentication and payments providers). Their accessibility follows their own conformance, which we monitor and pass along on request.

Perch is designed to work with current versions of major browsers (Chrome, Edge, Safari, and Firefox) and with the assistive technologies commonly paired with them, including screen readers and OS-level zoom and contrast settings. We test against recent browser versions; older or unsupported browsers may degrade the experience.

If you encounter an accessibility barrier in Perch, or need information in an alternative format, please tell us — we want to fix it.

• Email accessibility@onperch.co with the page or feature, what happened, and the assistive technology and browser you were using.
• We aim to acknowledge accessibility reports within 5 business days and will work with you on a remediation or a workaround.

For vendor reviews and procurement, we can respond to the accessibility sections of vendor reviews and discuss a remediation plan and timelines. Start at accessibility@onperch.co or see our Security overview.

Perchpoint LLC · accessibility@onperch.co