Company
Accessibility at Aventide
We aim for aventide.ai to meet WCAG 2.2 at level AA. Most of the basics pass, and the gaps we found are listed below. The pages your clients open are built with accessibility in mind, and we haven’t audited the full app yet.
Last tested November 6, 2026. Last updated November 8, 2026.
EB
Eric Baxter
Target
WCAG 2.2 level AA
Where we are
Tested, with known gaps
Last tested
November 6, 2026
Our commitment
We want everyone to be able to use aventide.ai and the pages your clients open: booking pages, client portals, proposals, contracts and invoices. That includes people who use a screen reader, a keyboard, zoom, voice control or reduced motion.
The standard we aim for
We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA on this website. We are not there on every page yet. The known gaps are listed below, and we’re fixing these now.
Where we stand
Accessibility looks different in three places. Here is where each one stands today.
This website
Tested, with known gaps
aventide.ai. We ran an automated check on all 102 pages in our sitemap, and tested keyboard use, reflow and reduced motion by hand. The gaps we found are listed below.
Pages your clients open
Built with care, not yet tested
Booking pages, client portals, proposals, contracts and invoices. They use labeled sections, announced form errors and visible focus, and they keep text readable whatever brand colors you choose. We haven’t yet tested them with a screen reader.
The Aventide app
Not yet audited in full
The full app is built for computer screens and doesn’t rearrange itself for narrow windows or high zoom. On a phone, use the Aventide app, or Sidekick in Telegram, WhatsApp or Slack. An audit of the full app in August 2026, not including the phone app, found issues that we’re still working through, and we haven’t yet tested it with a screen reader.
What works today
On the pages we tested, these basics pass.
Every page has a “Skip to content” link, a main content area and a language setting.
Headings follow a logical order, and every page has one main heading.
Every image has a text description, and every link and button has a name.
The menus open and close with a keyboard and tell screen readers whether they’re open. On a phone, the menu button does the same.
Pages reflow to 320 pixels wide without sideways scrolling of the page.
Moving parts stop when your device asks for reduced motion.
The cookie notice never covers a link that has keyboard focus.
The automated check found no other problems on any of the 102 pages.
Known gaps
These are the problems we found. We take each one off this list once its fix is live.
What’s wrong
Where
On a phone, wide tables scroll sideways, and some browsers don’t let you scroll them with a keyboard.
Three legal documents: Privacy, Cookie policy and Open source
The app is built for computer screens. It doesn’t rearrange itself for narrow windows or high zoom, so you may need to scroll sideways.
The Aventide app (app.aventide.ai)
Some small text is hard to read: green labels and numbers, one price note and the initials in some avatar circles.
Home page
What we’ve built into the product
These are the accessibility features we’ve built, checked against our code. They’re not a claim that every screen is accessible.
Pages your clients open
Sections have headings and labels that screen readers can jump between.
Sign-in and form errors are announced, and tied to the field they belong to.
Status messages, such as “You’re signed out,” are announced without moving your place on the page.
Links that open a new tab say so to screen readers.
Decorative symbols are hidden from screen readers, and dates are marked up as dates.
Buttons and form fields show a visible focus outline.
Text stays readable whatever brand colors a business chooses. If a color combination would be hard to read, Aventide adjusts it or falls back to a readable palette.
In the app
Icon buttons need a text label, and show a clear focus ring.
Most dialogs and side panels use components that move focus into the panel and return it when it closes.
The app’s shared styles turn off animations when your device asks for reduced motion.
Our code checks run accessibility rules on every change. They warn rather than block, because the August 2026 audit left a backlog that we’re working through. The keyboard rules already block in the redesigned Business Hub.
How we tested
An automated check with axe-core 4.10.2 against the WCAG 2.2 A and AA rules, on all 102 pages in our sitemap, at desktop width (1440 pixels) and phone width (390 pixels), in Chromium.
Checks by hand: keyboard focus through the menus and past the cookie notice, reduced motion, reflow at 320 pixels wide, heading order on every page, and color contrast on a sample of pages.
Not tested yet: screen readers (VoiceOver, NVDA), voice control, zoom to 200% on desktop, Safari and Firefox, and the app at app.aventide.ai.
Common questions
Is Aventide accessible?
We’re working toward WCAG 2.2 level AA. Our website passed an automated check on all 102 pages apart from one issue listed in the known gaps, and the pages your clients open are built with labeled sections, announced errors and visible focus. We haven’t yet audited the whole app or tested with screen readers, so we don’t claim full conformance.
Does Aventide meet WCAG 2.2 AA?
Not in full yet. That is our target. We’ve tested the website against it and listed the gaps we found. We haven’t completed an audit of the app, so we don’t claim conformance.
Can I use Aventide with a screen reader?
Our website and the pages your clients open use standard headings, labels and landmarks that screen readers rely on. We haven’t yet tested them with VoiceOver or NVDA, and we haven’t tested the app, so we can’t promise a smooth experience. If you run into a problem, write to support@aventide.ai.
Can I use Aventide with only a keyboard?
On our website, yes. There is a “Skip to content” link, the menus open and close with a keyboard, and focus stays visible. Wide tables on a few pages are the exception, as listed in the known gaps. We haven’t finished auditing keyboard use across the app.
Does Aventide respect reduced motion settings?
Yes on our website. Moving parts stop when your device asks for reduced motion. The app’s shared styles do the same.
Do you have an accessibility conformance report (VPAT)?
Not yet. If you need one, write to support@aventide.ai and tell us what you need it for.
How do I report an accessibility problem?
Write to support@aventide.ai. Say which page, what you were trying to do, and what you use, for example a screen reader or a keyboard.
Tell us about a problem
If something on our site, or on a page your client opened, doesn’t work for you, write to support@aventide.ai. Say which page, what you were trying to do, and what you use (for example a screen reader or a keyboard).
How we protect your data is on our Security page, and what we collect is in our Privacy Policy.