Legal

Accessibility Statement

Last updated August 20, 2026 · Effective August 20, 2026

Formspace ("Formspace," "we," "us," or "our") is committed to making our website and our product visualization platform usable by as many people as possible, including people with disabilities. This Accessibility Statement describes the standard we work to, the steps we take, the limitations we currently know about, and how to reach a person who can help if something on our site or in our product does not work for you.

We treat accessibility as ongoing work rather than a finished state. This statement is written to be accurate about where we actually are, because an honest account is more useful to you than a claim of perfection would be. If you encounter a barrier that is not described here, we want to hear about it — see Reporting a Barrier below.

1. Scope of This Statement

This statement applies to the Formspace marketing website at www.formspace.us and to the authenticated Formspace application, including the studio, the editorial canvas, the gallery, and account and billing screens (together, the "Service").

It does not apply to third-party websites, platforms, or services that we link to or that operate alongside the Service, and it does not apply to imagery, product data, or other content supplied by our customers. Those are addressed separately in sections 9 and 10.

2. Conformance Status

Our conformance target is the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA, published by the World Wide Web Consortium (W3C). We also track WCAG 2.2 Level AA and treat its additional criteria as our forward-looking target.

Formspace is currently partially conformant with WCAG 2.1 Level AA. "Partially conformant" is the W3C’s term for a site that meets much of the standard but where some content does not yet fully conform. We are stating this deliberately rather than claiming full conformance: the specific areas we know fall short are listed in section 8, and the work to close them is described in section 14.

Conformance is assessed on an ongoing basis. Because the Service changes frequently, a page that conformed at one point may regress, and we rely partly on reports from users to catch that.

3. Legal Framework

We aim to meet our obligations under applicable accessibility and non-discrimination laws, which may include:

  • The Americans with Disabilities Act (ADA) — including Title I as it applies to employment and Title III as it applies to places of public accommodation.
  • Sections 504 and 508 of the Rehabilitation Act of 1973 — relevant where Formspace is procured or used by federal agencies or federally funded entities.
  • State law — including California’s Unruh Civil Rights Act, New York’s Human Rights Law, and comparable statutes in other states where our users are located.
  • Non-U.S. requirements — including EN 301 549 and the European Accessibility Act in the European Union, the Accessibility for Ontarians with Disabilities Act (AODA) in Ontario, and comparable frameworks elsewhere, where they apply to us.

Neither the ADA nor most state statutes currently designate a single binding technical standard for private commercial websites. We use WCAG 2.1 Level AA because it is the standard most consistently referenced by regulators, courts, and settlement agreements, and because it is the standard most assistive technology is built around.

4. Measures We Take

Accessibility is addressed as part of how the Service is built, not as a later cleanup. Current measures include:

  • Semantic structure and landmarks. Pages are built with semantic HTML — headings in order, lists as lists, and named navigation, main, and footer landmarks — so screen reader users can navigate by structure rather than reading linearly.
  • Keyboard operation. Interactive controls are reachable and operable by keyboard, and a visible focus indicator is drawn on every focusable element rather than being suppressed.
  • Text alternatives. Meaningful images carry descriptive alternative text, and images that are purely decorative are hidden from assistive technology so they do not add noise.
  • Reduced motion. Animation on our site respects the operating system "reduce motion" setting. Where that setting is on, transitions and moving imagery are stilled rather than merely shortened.
  • Colour and contrast. Body text, headings, and interactive text are chosen to meet or exceed the WCAG AA contrast minimum against their backgrounds, and colour is not used as the only means of conveying information.
  • Resizable, reflowable text. Layouts use relative units so text can be enlarged or the page zoomed without content being clipped or lost.
  • Language of page. The document language is declared so screen readers use the correct pronunciation.
  • Accessibility in review. Accessibility considerations are part of how we review changes, and reported barriers are triaged alongside other defects rather than in a separate backlog that never moves.

5. Technical Specifications

Accessibility of the Service relies on the following technologies working with your browser and any assistive technology you use:

  • HTML
  • CSS
  • JavaScript
  • WAI-ARIA
  • SVG and raster image formats
  • HTML canvas, used for decorative visual effects only

JavaScript is required for the authenticated application to function. The marketing and legal pages, including this one, render their content without it.

6. Browser and Assistive Technology Compatibility

The Service is designed to work with current versions of major browsers — Chrome, Safari, Firefox, and Edge — on desktop and mobile, together with the assistive technology commonly paired with them, including screen readers such as NVDA, JAWS, VoiceOver, and TalkBack, screen magnification, speech input, and browser zoom.

We do not claim to have verified every combination of browser, operating system, and assistive technology, and we do not represent that the Service performs identically across all of them. Older browsers and older assistive technology versions may not support the features the Service relies on. If a specific combination you depend on does not work, please tell us which one it is — that detail materially speeds up a fix.

7. How We Assess Accessibility

Our current assessment is a self-evaluation, carried out by the team that builds the Service. It combines review against the WCAG 2.1 Level AA success criteria, keyboard and screen reader testing of primary flows, and contrast checking of our colour palette.

We have not yet commissioned an independent third-party accessibility audit or obtained external certification. We are stating that plainly rather than implying external validation we do not have. Engaging an independent evaluator is part of the plan described in section 14.

We do not use, and do not intend to use, an automated accessibility overlay, toolbar, or widget as a substitute for accessible code. Overlays do not reliably remediate underlying barriers and can interfere with a user’s own assistive technology.

8. Known Limitations

Despite our efforts, some parts of the Service are not yet fully accessible. We know about the following, and each is tracked for remediation:

  • No skip-to-content link. Pages do not yet offer a mechanism to bypass the repeated header navigation, so keyboard and screen reader users must move through it on each page. Landmark navigation is available as a partial substitute in the meantime.
  • Contrast of some secondary text. A small number of supporting elements, such as minor captions and footer meta text, use a muted tone that does not meet the 4.5:1 minimum for normal-size text. The information in these elements is always available elsewhere on the page in conforming contrast.
  • The editorial canvas. Composing a scene involves direct manipulation — dragging, placing, and rotating objects on a canvas. Keyboard and screen reader equivalents for some of these operations are incomplete. If you need to produce a scene and cannot use the canvas, we will do it with you or for you; see section 11.
  • Automated regression coverage. Our automated test suite does not yet include accessibility checks, so regressions in interface code are currently caught by review and by user reports rather than automatically.
  • Third-party components. Some embedded third-party functionality, such as payment and analytics components, is not fully under our control. See section 9.

This list reflects what we currently know. It is not a representation that no other barrier exists, and identifying one that is not listed here is a reason to contact us, not a reason to assume it is intended.

9. Third-Party Content and Services

The Service incorporates components and content provided by third parties, including payment processing, analytics, web fonts, and hosting infrastructure. We do not control how those third parties build their components, and we cannot guarantee their accessibility.

Where a third-party component creates a barrier, we will make reasonable efforts to work with the provider toward a fix, to offer an accessible alternative path to the same outcome, or to replace the component. We consider accessibility when selecting vendors and request conformance information, such as a VPAT or accessibility conformance report, where a vendor publishes one. If a third-party component is blocking you, tell us and we will find another way to get you the same result.

10. Customer and AI-Generated Imagery

Formspace produces product and room-scene imagery from inputs our customers supply. Two things follow from that, and both matter for accessibility:

  • Alternative text for generated imagery. Where imagery produced with Formspace is published on a customer’s own website, catalog, or storefront, the customer is responsible for providing appropriate alternative text in that destination, since only the customer knows the context the image appears in. We encourage every customer to do so, and we are glad to advise on writing useful alternatives.
  • Customer-supplied content within the Service. Product names, descriptions, and uploaded assets are provided by customers. We do not author that content and cannot warrant its accessibility, though we aim to present it in an accessible container.

11. Alternative Access and Accommodations

If any part of the Service is not usable for you, we will provide the same information, service, or outcome through another means, at no additional cost to you and without requiring you to disclose a diagnosis or provide medical documentation. Depending on what you need, that can include:

  • Providing information from this site or the application in an alternative format, such as plain text, large print, or an accessible document.
  • Completing a task in the application on your behalf, or working through it together by phone, email, or video call.
  • Supplying pricing, terms, or account information directly rather than through an interface that is not working for you.
  • Arranging additional time or an alternative route through any workflow that is presenting a barrier.

To request an accommodation, email hello@formspace.us with "Accessibility" in the subject line. Requests are handled on the timeline in section 12.

12. Reporting a Barrier

We welcome reports of accessibility barriers, and we would rather hear about a problem than have you work around it. To report one, email hello@formspace.us.

Anything you can tell us helps, and none of it is required. If it is easy to include:

  • The page address or the part of the product involved.
  • What you were trying to do, and what happened instead.
  • The browser, operating system, and any assistive technology you were using, including versions if you know them.
  • How you would prefer us to reply.

Our commitment: we aim to acknowledge accessibility reports within 2 business days and to provide a substantive response within 10 business days, describing what we found, what we intend to do, and an expected timeframe. Where a fix will take longer, we will offer an interim alternative under section 11 so you are not left waiting on the repair to get what you came for.

We will not retaliate against anyone for raising an accessibility concern.

13. Escalation

If you are not satisfied with our response, you may ask that your report be escalated for review by a member of our leadership. Send your original report and our reply to hello@formspace.us with "Accessibility escalation" in the subject line, and we will respond within 10 business days.

Using this process is optional. Nothing in this statement requires you to exhaust it, and nothing in it limits or waives any right you have to pursue a complaint or remedy with a regulator, an enforcement agency, or a court.

14. Ongoing Work

Accessibility work currently planned includes adding a skip-to-content mechanism, raising the contrast of the remaining secondary text, extending keyboard and screen reader support in the editorial canvas, adding automated accessibility checks to our test suite so regressions are caught before release, and commissioning an independent evaluation.

We review this statement and the limitations in section 8 at least annually, and after any significant change to the Service. Items listed here are commitments to effort and attention, not guarantees of a delivery date.

15. Employment Accommodations

Formspace does not discriminate on the basis of disability in hiring or employment. Applicants and employees who need a reasonable accommodation to participate in our application process, to interview, or to perform a role may request one by emailing hello@formspace.us. Requests are treated confidentially and handled through an interactive discussion about what would work for you.

16. Purpose and Effect of This Statement

This statement is provided for transparency about our accessibility practices. It is a good-faith description of our current position and intentions, and it is not a warranty, guarantee, or contractual commitment that the Service is free of accessibility defects or that it conforms fully to any particular standard.

Nothing in this statement waives, limits, or is intended to waive or limit any right or remedy available to you under applicable law, and nothing in it is an admission of liability. Where this statement conflicts with our Terms and Conditions, those Terms govern the contractual relationship between us, except that nothing in them limits your rights under applicable accessibility or non-discrimination law. Personal information you send us in an accessibility report or accommodation request is handled under our Privacy Policy.

17. Changes to This Statement

We may update this Accessibility Statement to reflect changes in the Service, in our practices, or in applicable standards and law. When we do, we will revise the "Last updated" date at the top of this page. Material changes to the reporting process or to the accommodations we offer will be described here.

18. Contact Us

For anything related to accessibility — a barrier, an accommodation, a question about this statement, or a request for conformance information for a procurement review — please contact us:

  • Email: hello@formspace.us
  • Subject line: "Accessibility", so your message is routed to someone who can act on it
  • Company: Formspace
  • Jurisdiction: State of Georgia, United States

If email is not an accessible channel for you, say so by any means you can reach us and we will arrange another way to communicate.

← Back to home