Accessibility

We want everyone to be able to draw, read and share a floor plan with FloorGen, whatever their sight, hearing or movement and whatever device they use. This statement covers floorgen.app: the public site, sign-in, your projects and the editor.

Our target

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA.

Current status

FloorGen is partially conformant with WCAG 2.2 AA: some parts do not yet fully meet the standard. They are listed under Known limitations, each with what to use instead.

What works today

• Keyboard: menus, dialogs, panels and forms work with the keyboard alone, with a visible focus ring. The editor lists its shortcuts under Help & shortcuts (the ? key).
• Skip links: the first Tab on a page offers to jump past the header to the content; in the editor, to the plan.
• Screen readers: buttons, icons and fields have names in the page's language, and notices and FloorGen AI's replies are announced as they arrive.
• Reduced motion: when your system asks for reduced motion, animations are cut down and demos do not play on their own.
• Contrast: text and control colours are tested against the WCAG contrast ratios, in the light and the dark theme.
• Windows High Contrast: forced colours are supported. Focus rings, selected states and icon buttons have their own forced-colour styles, checked in browser emulation; testing on Windows itself is still to do.
• Text alternatives to the drawing: the Outline panel lists the rooms and items on each floor as text, and choosing a row selects it on the plan. FloorGen AI takes plain requests such as "make the kitchen 3 m wide".

Known limitations

• The 2D plan and the 3D view are drawn pictures that a screen reader cannot read, and the 3D view cannot yet be focused or used to select things from the keyboard. Use the Outline panel to find and select what is on the plan, the properties panel to change it, and FloorGen AI to ask for changes in words.
• Selection on the plan is not announced yet: when you step through the plan with [ and ], a screen reader does not say what is selected. The Outline panel marks it.
• PDF exports are not tagged: they have no headings, reading order or text description of the plan. Plan summary in the editor gives the rooms and areas as text.
• Pinch zoom in the editor on touch screens: pinching zooms the plan and the 3D view, not the editor's menus and panels, so a pinch never leaves the editor stuck zoomed. To make the editor larger, use your browser's page zoom or text size (the aA menu in Safari, Zoom in Chrome's settings) or Ctrl or ⌘ and + on a keyboard. The public site and your projects list zoom as usual.

We are working on these, the plan and 3D view first.

How we test

Automated checks: axe-core runs in our browser tests of the main journeys (the public site, sign-in and the editor), and an accessibility lint and a contrast check of every colour pair we use run before every commit. By hand, we are testing with these screen readers and browsers; that audit is not finished yet:

Report a barrier

If something in FloorGen stops you, or this page is wrong, write to us with the Support topic. Tell us the page, what you tried, and the browser and assistive technology you use. We reply within 5 working days and tell you when it is fixed.

About this statement

We wrote this statement on 17 October 2026, from our own testing. We review it whenever we change how FloorGen works with assistive technology, and at least once a year.