Accessibility Statement

1. What this statement covers

Sianipar Consults LLC wants Ayebridge to work for everyone who uses it: our customers, their teams and the clients they invite, whatever device or assistive technology they use. This statement covers the website at ayebridge.com, the Ayebridge app and the client portals our customers share with their clients, including portals on portal subdomains and custom domains.

2. The standard we aim for

Our target is the Web Content Accessibility Guidelines (WCAG) 2.2 (opens in a new tab) at Level AA. This is the standard we design and test against. It is a target, not a certification: Ayebridge has not yet been audited by an independent accessibility specialist, so we do not claim full conformance.

3. How we build for accessibility

• Semantic HTML: one main heading per page, landmarks, and a “Skip to content” link.
• Everything can be done with a keyboard, with a visible focus indicator.
• Form fields have visible labels, and errors are given in text, not only by color.
• Menus and dialogs use native browser elements where possible, so they behave as assistive technology expects.
• Images have text alternatives; decorative images are hidden from screen readers.
• Statuses such as “Approved” or “Changes requested” are written out, not shown by color alone.
• Layouts adapt to small screens and to browser zoom, and animation is reduced when your system asks for reduced motion.
• Files can be added with a standard file picker as well as by drag and drop.
• Client contacts sign in with an emailed link, so they do not need to remember a password or solve a visual puzzle.

4. Known limitations

These are the limitations we know about. We list them so you can plan around them, and we are working on them.

• Generated PDFs. Quotes, invoices and approval records exported as PDF may not be fully tagged for screen readers. The same information is available as a web page inside the app or portal.
• Customer content. Files, images and documents uploaded by our customers and their clients may not have text alternatives or accessible formatting. We cannot control that content, but we are happy to help a customer make theirs more accessible.
• Previews. Image and PDF previews show the file as it is. Where a file is not accessible, download it to open it in an application that suits you.
• Color contrast. We have recently changed our color palette. It was chosen to meet WCAG AA contrast, and we are re-checking every screen against it.
• Stripe pages. Checkout and the billing portal are provided by Stripe on Stripe’s own pages, and their accessibility is managed by Stripe. If you have trouble with them, email us and we can help with billing by email instead.

5. Feedback and help

If something in Ayebridge is hard to use, or you need information in another format, email support@ayebridge.com with “Accessibility” in the subject. Tell us the page or feature, what you were trying to do, and the browser and assistive technology you use, if any.

We reply within 1–2 business days. While we fix a problem, we will help you get the information or complete the task another way.

6. About this statement

This statement was prepared on the date shown at the top, based on our own review of the website, the app and client portals. We will update it when we complete further testing or fix the limitations above.