1. Scope

This Statement applies to:

Fintant’s public website; public inquiry and scheduling entry points controlled by Fintant; the authenticated accounting-firm portal; client-facing status, questions, files, deliverables, and approval workflows; Fintant operations interfaces used to prepare and review work; and legal, privacy, security, support, and help content published by Fintant.

Third-party services, client-uploaded documents, and exported files may have separate accessibility characteristics, as explained below.

2. Accessibility target

Fintant uses WCAG 2.2 Level AA as its technical reference. WCAG addresses accessibility through four principles: content and functionality should be perceivable, operable, understandable, and robust.

Fintant’s intended approach includes:

semantic page regions, headings, labels, lists, tables, and status messages; keyboard access without traps; a visible keyboard-focus indicator; a skip link and predictable navigation; accessible names and instructions for controls; error identification and recovery guidance; status, warning, approval, and exception meaning that does not rely on color alone; sufficient text and non-text contrast; text resize, responsive reflow, and use from approximately 320 CSS pixels upward; accessible invitation, authentication-code, session, and recovery instructions; meaningful link and button labels; text alternatives for informative images; captions or alternatives for time-based media when used; reduced-motion and user-preference support where applicable; and compatibility testing with current browsers and commonly used assistive technology.

3. Implemented foundations

The current application includes or is designed around:

semantic landmarks and heading hierarchy; keyboard-visible focus states; a skip-to-content link; form labels and field-level error messages; non-color indicators for status and workflow state; responsive public and portal layouts; accessible legal and support routes; structured tables and lists for accounting information; and separation of internal notes from client-facing content.

Implementation in source code does not by itself prove full conformance. Fintant must validate complete user workflows in the deployed environment with automated checks, keyboard testing, zoom and reflow testing, and assistive technology.

4. Current validation status and known limitations

Fintant has not yet completed an independent accessibility audit of the production service. The current system is not approved for live Client Financial Data, and full accessibility release evidence remains a launch gate.

Areas that require continued testing or remediation include:

complete invitation, authentication, recovery, recent-authentication, and logout flows using the approved production identity provider and configured authentication method; file upload, quarantine, error, retry, replacement, download, and deletion states using approved production storage and scanning; complex accounting tables, comparison views, workpaper previews, filters, exports, and status changes; client review, rejection, acceptance, and approval workflows; charts, document previews, PDFs, spreadsheets, and client-uploaded source documents; timeouts, reauthentication, focus restoration, live status announcements, and validation errors; embedded scheduling or meeting-provider interfaces; mobile and high-zoom behavior across full workflows; and compatibility with representative screen-reader, browser, keyboard, voice, and magnification combinations.

Fintant will not claim full WCAG 2.2 AA conformance until the applicable pages and complete processes satisfy the requirements and the evidence is approved.

5. Client-uploaded and generated documents

Accounting firms may upload statements, invoices, receipts, workpapers, spreadsheets, PDFs, images, and other documents that Fintant did not create. Their accessibility depends on the source format and author.

Fintant will use reasonable efforts within the contracted scope to:

preserve text and structure where available; provide accessible portal labels, status, and surrounding instructions; avoid presenting an image as the only way to understand a material workflow state; provide a reasonable alternative format for Fintant-created content when practical; and identify material limitations that affect a user’s ability to review or approve work.

Fintant does not automatically remediate every client-provided source document unless that service is separately agreed.

6. Third-party services

Fintant may use approved third-party services for identity, scheduling, meetings, email, file storage, support, or other functions. Third-party interfaces and content may be governed by the provider’s accessibility practices.

Before a provider is activated, Fintant will consider:

whether the user can complete the essential process with a keyboard and assistive technology; whether the provider supports labels, focus, errors, reflow, contrast, and accessible authentication; whether an accessible alternative path is available; whether the provider accepts and remediates accessibility reports; and whether material limitations must be disclosed.

Contact Fintant if a third-party step prevents access. Fintant will attempt to provide an alternative within its control.

7. Supported technology approach

Fintant intends to support current major desktop and mobile browsers and commonly used assistive technologies. The final supported-technology list must be established through production testing.

Accessibility may be reduced when:

a browser, operating system, or assistive technology is no longer supported by its vendor; scripting, cookies, or essential browser storage is disabled; a corporate network, extension, or security tool modifies the interface; a third-party service has a limitation outside Fintant’s control; or a source document lacks accessible text or structure.

Fintant will not require a specific assistive technology when a standards-based solution is reasonably available.

8. Assistance and accommodations

If you cannot access information or complete a task, email support@fintant.ai with “Accessibility” in the subject line. Fintant can work with you and the accounting-firm administrator to identify a reasonable alternative, which may include:

accessible instructions; an alternate document format; an alternate communication method; assistance completing a non-financial portal task; a corrected label, focus, contrast, or error issue; an alternate scheduling path; or another practical accommodation within Fintant’s authority.

Fintant cannot bypass identity, authorization, organization, approval, confidentiality, or security controls as an accommodation. A safe alternative may require identity verification or coordination with the accounting firm.

9. How to report an accessibility problem

Email support@fintant.ai with “Accessibility” in the subject line and include, if possible:

the page, feature, document, or workflow; the web address; the task you were trying to complete; the problem encountered; your browser, operating system, and assistive technology; whether an alternative format or method would help; and a safe way to contact you.

Do not include credentials, account numbers, tax information, financial statements, source files, or other Client Financial Data in ordinary email. Fintant may provide a secure follow-up channel.

Fintant’s proposed non-contractual target is to acknowledge an accessibility report within 5 business days and provide a status or alternative path as soon as reasonably practical. This target must be approved and operationalized before publication.

10. Feedback, testing, and improvement

Fintant’s accessibility program is intended to include:

accessibility acceptance criteria in product requirements; automated checks in development and release workflows; manual keyboard, focus, zoom, reflow, contrast, and screen-reader testing; testing of complete user processes rather than isolated components; issue severity, ownership, remediation, and retest evidence; accessibility review of material third-party providers; accessible document and communication practices; training for design, engineering, operations, support, and content owners; and periodic review after material product or provider changes.

Feedback from users with disabilities is important and will be considered in prioritization.

11. Enforcement and legal rights

This Statement describes Fintant’s accessibility commitment and current status. It does not limit rights or remedies under applicable law, waive security or privacy requirements, or amend a Client Agreement.

If a specific accessibility law applies to a client, geography, service, or document, Fintant and the client organization will allocate responsibilities in the applicable agreement and implementation plan.

12. Contact

Accessibility reports and accommodations: support@fintant.ai, with “Accessibility” in the subject line General support: support@fintant.ai Privacy questions: privacy@fintant.ai Mail: Fintant Inc., 73-12 35th Avenue, Suite A45, Jackson Heights, NY 11372