Skip to content

Accessibility Statement

Last reviewed: June 8, 2026

Covey is a payment-confirmation and ordering platform for restaurants — including Zelle/payment confirmation, hosted menus, and live order tracking. We want everyone to be able to use it, regardless of ability or the technology they rely on.

Our commitment to accessibility

Accessibility is part of how we design, build, and review Covey — not an afterthought. We are committed to making the product usable by as many people as possible, including people who use assistive technologies such as screen readers, screen magnifiers, voice control, and keyboard-only navigation. We treat accessibility as an ongoing responsibility and work to improve it continuously as the product evolves.

Conformance status

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA — the standard most commonly referenced in connection with the Americans with Disabilities Act (ADA) and the technical basis for Section 508 of the Rehabilitation Act.

Covey is currently partially conformant with WCAG 2.1 Level AA. “Partially conformant” means most of the product meets the standard, but some parts may not yet fully conform. We describe the known limitations below and are actively working to close them. We do not claim full or certified compliance; we describe this as a substantial, good-faith, and improving effort.

Measures we take & accessible features

  • Use semantic HTML with landmarks, headings, lists, and buttons, so structure is conveyed to assistive technology.
  • Provide text alternatives for meaningful images and icons, and mark purely decorative imagery so it is skipped by screen readers.
  • Add accessible names and ARIA attributes (labels on icon-only buttons, dialog roles on modals, live regions for status updates) where native semantics are not enough.
  • Support keyboard operability with a clearly visible focus indicator for keyboard users and the ability to dismiss overlays with the Escape key.
  • Associate form labels with their fields so forms are understandable with assistive technology.
  • Maintain readable color contrast for body text and interface elements, targeting WCAG AA ratios.
  • Provide a skip-to-content link so keyboard users can jump past repeated navigation.
  • Respect reduced-motion preferences, gating non-essential animation for visitors who request reduced motion at the operating-system level.
  • Never rely on sound alone — for Deaf and hard-of-hearing users, audio alerts (such as new-order and order-ready chimes) are always paired with a visual indicator and an optional beacon light, and we do not use audio or video that would require captions.
  • Provide responsive reflow, so content adapts to small screens and zoom without loss of information.

Compatibility

Covey’s accessibility relies on HTML, WAI-ARIA, CSS, and JavaScript. It is designed to be compatible with recent versions of major browsers (Chrome, Edge, Firefox, and Safari) on desktop and mobile, used with current screen readers and assistive technologies. Some features depend on JavaScript being enabled. If a combination of browser and assistive technology is not working for you, please contact us below.

Known limitations

  • Live order and status updates. Order status can change in real time; these updates may not always be announced clearly or promptly by every screen reader.
  • Embedded and third-party content. Some components — such as embedded payment/confirmation widgets and payment processing — are provided in part by third parties, whose labeling and focus behavior may not be fully under our control in every combination.
  • Confirmation screenshots and bank-email content. Where a payment confirmation is shown from an image or a forwarded bank message, the underlying text alternative may be incomplete.

In all of these cases, the same information is available in plain text within the page, and we will provide it another way on request — including a plain-text summary of an order, its status, or a payment confirmation.

Ongoing efforts

Covey assesses accessibility primarily through self-evaluation and ongoing internal review during design and development — including keyboard testing, checking with assistive technology where practical, and reviewing color contrast and page structure. We revisit accessibility as the product changes and incorporate feedback we receive.

Feedback & requesting accommodations

We welcome your feedback. If you encounter a barrier, or you need information provided in a different, accessible format, please tell us using any of our support channels:

Please describe the problem, the page or feature involved, and the assistive technology or browser you were using, if you can. We make a reasonable effort to respond within 3–5 business days and to provide the information you need in an accessible format on request.

A note on this statement

This statement is provided in good faith and for transparency about our accessibility efforts. It is not a warranty, guarantee, or legal advice, and it does not create any legal obligation beyond applicable law.