Accessibility Statement

What this statement covers

This statement describes FileToWeb’s accessibility approach across its public website, authenticated product, conversion workflow, and published web output.

The current assessment status applies to FileToWeb’s public website, including its marketing pages, pricing pages, government pages, blog, documentation, FAQ, contact pages, and public tools.

The authenticated workspace, AI Editor, document viewer, publishing workflows, customer-uploaded source files, and customer-created content are not currently covered by a conformance claim. Their role in FileToWeb’s accessibility approach is explained below.

Product and conversion workflow

Accessibility is part of the FileToWeb product workflow, not only the public website. Our approach includes:

• A workflow for uploading source files, converting them to web content, reviewing the result, managing versions, and publishing the selected version.
• A conversion pipeline designed to produce structured, responsive HTML that can support headings, landmarks, lists, links, tables, images, and a logical reading order.
• An AI Editor that lets people review and revise converted content before it is published.
• Automated conversion and accessibility checks can reduce barriers, but they do not guarantee conformance. Human review remains important before publication.

We are evaluating the authenticated workspace, AI Editor, document viewer, and publishing workflows as distinct product surfaces. We do not yet make a conformance claim for those experiences.

Accessibility standard and current status

FileToWeb aims to conform to the Web Content Accessibility Guidelines, WCAG 2.2 Level AA.

A complete manual conformance evaluation of the website scope described above has not yet been completed. We therefore do not currently claim full conformance.

Target

WCAG 2.2 Level AA

Current conformance status

Not yet formally assessed

How we support accessibility

For the current review of the public website, FileToWeb used the following measures:

• Uses semantic HTML and native controls wherever practical.
• Runs automated accessibility checks during development for representative public pages.
• Tests representative public website journeys using keyboard navigation.
• Reviews focus order and visible focus for interactive elements in representative public website journeys.
• Checks responsive reflow and horizontal overflow at narrow viewport widths.

Report an accessibility barrier

We welcome feedback on the accessibility of FileToWeb. If you encounter a barrier or need information in another format, please use our accessibility feedback form.

Please include the page or document address, what you were trying to do, and any browser or assistive-technology details you are comfortable sharing.

You do not need to disclose a disability.

Known limitations

We are completing a representative manual assessment of the website and product surfaces described above. Until that assessment is complete, we are not claiming that no barriers exist.

When a limitation is confirmed, we will describe:

• The affected page or feature
• The barrier a user may encounter
• Who may be affected
• An available alternative or workaround
• The remediation status
• The date the item was last reviewed

Customer-provided content

FileToWeb allows customers to upload source files, edit converted content, and choose which version to publish. The accessibility of source files and customer-published pages can vary based on the original content, subsequent edits, and the review completed before publication.

FileToWeb provides structured conversion, automated checks, editing tools, versioning, and review workflows. These tools do not automatically certify every output as conformant or legally compliant.

If you encounter an accessibility barrier on a FileToWeb-hosted document, send us the document address through the accessibility feedback form. We will help identify the publisher, communicate the issue, and seek an accessible alternative where possible.

Browser and assistive-technology compatibility

We are building a documented compatibility matrix from combinations that have actually been tested. We do not currently claim compatibility with every browser or assistive technology.

Technical information

The accessibility of FileToWeb relies on the following technologies working with the user’s browser and assistive technologies:

• HTML
• CSS
• JavaScript
• SVG
• WAI-ARIA, where native HTML alone is not sufficient

We prefer native HTML semantics and controls over custom ARIA implementations wherever practical.

How we assess accessibility

Our current self-evaluation of the public pages in scope combines:

• Automated accessibility testing
• Code and semantic-markup review
• Manual keyboard testing
• Focus-order and focus-visibility testing
• Zoom and responsive reflow testing

Assessment type

Self-evaluation; formal conformance assessment not yet complete

Most recent review

August 6, 2026

Statement ownership

This accessibility statement is owned and approved by: