Frontbell Accessibility Statement

Effective Date: August 4, 2026 Last Reviewed: August 4, 2026 Review Cadence: This statement is reviewed at minimum every 6 months and after any audit that materially changes our conformance status.

Our Commitment

Frontbell (a product of Vaxio, Inc.) is committed to making our software usable by everyone, including people who rely on assistive technology — screen readers, keyboard-only navigation, voice control, and screen magnification. Accessibility is an ongoing effort, not a one-time project, and this statement is updated as our conformance status changes.

We build for tradespeople running their businesses from a job site or a truck — many of our users are on a phone, in bright sunlight, wearing gloves, or otherwise not using a mouse and a keyboard under ideal conditions. Accessible design is directly in line with that use case, not in tension with it.

Conformance Standard

Our target is WCAG 2.1, Level AA (Web Content Accessibility Guidelines, published by the W3C), which is the standard most commonly referenced by U.S. regulators, courts, and accessibility auditors as the practical benchmark for web accessibility — including the standard the U.S. Department of Justice adopted for state and local government websites under Title II of the ADA.

Current Conformance Status: Substantially Conformant (Audited Surfaces)

We have completed a remediation pass addressing every issue identified in our August 4, 2026 WCAG 2.1 AA audit. As of August 4, 2026, we consider Frontbell substantially conformant with WCAG 2.1 Level AA on the specific surfaces that audit covered: the org-portal application (login, dashboard, customers, invoices, settings), the client-portal login page used by our customers' own clients, and our public legal pages.

"Substantially conformant" means: on these audited surfaces, an automated re-scan (axe-core, WCAG 2.1 A + AA rule tags) found zero rule violations, and the specific defects our manual keyboard-only pass identified have been fixed and re-verified. It is not a claim of full, permanent, or Service-wide conformance — automated and manual testing cannot catch every possible barrier, and parts of the Service outside this audit's scope have not yet been assessed (see Scope below). We treat this as a snapshot that we will keep re-testing and updating, not a one-time certification.

Remediation history (as of August 4, 2026)

Our August 4, 2026 audit found a small number of concentrated, mostly shared-root-cause issues: keyboard focus was not visually indicated anywhere in the signed-in application or on the login form's input fields; several icon-only controls (including the password-visibility toggle) had no label a screen reader could announce; a chat panel component could, in some states, be reachable by keyboard focus while marked hidden from assistive technology; body and secondary text in a number of places fell slightly short of our target contrast ratio; every page shared the same non-descriptive title; and a couple of footer links on our legal pages had low-contrast styling.

All of the above were fixed the same day (commit c186cd476): a visible focus indicator was applied across the application, the affected controls were given accessible names, the chat panel's hidden/focusable state was corrected, the shared text-color token was darkened to clear the 4.5:1 AA contrast threshold, every route was given a unique page title, and the low-contrast links were darkened and underlined. Re-running the same automated audit against the same surfaces afterward found zero remaining violations.

We are continuing to expand our audit coverage to the rest of the Service (see Scope) and will update this section — including reopening it if a future audit finds new issues — as that work continues.

Feedback

If you encounter an accessibility barrier while using Frontbell, please tell us. We want to know, and we will make a good-faith effort to respond and to fix or work around genuine barriers in a reasonable time.

Email: legal@vaxio.ai (or support@frontbell.ai for in-product issues)

Please include: the page or feature you were using, the assistive technology or browser you were using (if applicable), and a description of what happened. We will acknowledge feedback within 5 business days.

Scope

This statement covers frontbell.ai, the org-portal web application, the client portal used by our customers' own clients (accessed via a link your service provider sends you), and our public legal pages.

Our August 4, 2026 audit — the basis for the "substantially conformant" status above — directly tested a defined set of surfaces: the org-portal login, dashboard, customers, invoices, and settings pages; the client-portal login page; and our public legal pages. It did not yet reach every org-portal route and workflow beyond those five, the client portal's authenticated pages past login, the Frontbell mobile application, or frontbell.ai itself. We have not identified known issues on those not-yet-audited surfaces, but we also have not yet verified them the way we verified the surfaces above, so we are not claiming conformance there. Expanding coverage to these areas is ongoing work, and this statement will be updated as it happens.

This statement does not cover third-party integrations you connect to your account (for example, your own email or calendar provider), which are governed by that provider's own accessibility practices.

Technical Specifications

Accessibility of Frontbell relies on the following technologies to work with the particular combination of web browser and any assistive technologies or plugins installed on your computer:

• HTML
• CSS
• JavaScript

These technologies are relied upon for conformance with the accessibility standards used.

Assessment Approach

Frontbell assessed the accessibility of the Service by the following approaches:

• Automated testing (axe-core, an open-source accessibility testing engine) against the application's authenticated and public-facing pages, run once to establish the initial findings and again after remediation to confirm the fix.
• Manual testing, including a keyboard-only navigation pass through the sign-in flow, primary navigation, and core workflows.

This is a self-assessment, not a third-party certification or a formal Accessibility Conformance Report (ACR/VPAT). See docs/legal/VPAT_TEMPLATE_NOTES.md for our readiness to produce a formal VPAT if a customer's procurement process requires one.

---

This statement follows the format commonly used for W3C-style accessibility statements. It is not a legal document and does not constitute a warranty of accessibility or ADA/WCAG compliance.