Accessibility statement

Our aim

formaster.app should be usable by everyone, including people who use a keyboard, a screen reader, voice control, zoom or large text, or reduced motion, and people who write in a right-to-left language. We aim for WCAG 2.2 level AA. No independent accessibility audit has been done yet, and it has not been tested with a panel of disabled users, so treat this page as what we have built and checked ourselves, not as a certification.

What works today

• Keyboard: every control can be reached with Tab and has a visible focus ring, and a “Skip to main content” link comes first on every page. On the page itself, each field can be focused; Enter selects it, the arrow keys move it (hold Shift to move it ten times as far) and Delete removes it. Ctrl or Cmd with Z undoes and with Shift redoes, and + − 0 zoom the page. Menus, tabs, the date picker’s calendar and the language list follow the usual arrow-key patterns.
• Placing fields without pointing: after choosing a field type, “Place at the middle of the view” puts it there, and the arrow keys or the Position tab’s numeric X and Y values fine-tune it. The “All fields” list shows every value in the document as an ordinary form that can be filled in with the keyboard and a screen reader.
• Screen readers: pages have landmarks and headings; icon buttons and fields on the page have names; each field on the page announces its name, type, value and state; status messages are announced politely and errors assertively; the AI run’s activity is a live log.
• Hiding data from the AI does not depend on drawing: “Choose text…” lists the page’s printed text with checkboxes, “Find sensitive text” and “Hide this page” are buttons, and every hidden area is listed with a button to remove it.
• Language and direction: formaster.app’s interface is in English only. Text you enter in Arabic, Hebrew or another right-to-left script is shaped and aligned right to left, on the page and when you export it, and “Form language” can show a form’s questions in another language (translated with AI), with the “All fields” list laying out right to left when that language is written that way. The PDF page itself always stays as printed.
• Display: animations stop when your device asks for reduced motion; Windows high-contrast (forced colours) keeps the edges of controls visible; layouts adapt to narrow screens; colour contrast on the main screens passes automated checks (axe-core), which cover only part of what contrast requires.
• Your own settings: “Accessibility settings” (in the footer of the main pages, on the sign-in page and in the editor’s menu) lets you choose a larger text size, a high-contrast mode with darker text, stronger edges and a thicker focus ring, “Reduce motion” even if your device did not ask for it, and underlined links. They apply straight away, are remembered in this browser, and work without agreeing to any optional cookies. Text sized in the page’s type scale also follows the text size set in your browser.
• Choosing pages for the AI: “This page”, “All pages” or “Choose pages” are buttons in a group; chosen pages are typed as ranges (1-3, 5) or picked with a button for each page, which state whether they are pressed, and a live summary says which pages will be used. The cookie choices notice can be reached and used with the keyboard and a screen reader, and “Reject all” is as easy to use as “Accept all”.

Known limitations

• The PDF is drawn as a picture. Inside the editor, a screen reader reads the fields you add but not the printed text of the PDF itself; read the original in a PDF reader, or use the “All fields” list.
• Drawing a signature or initials, and drawing or highlighting a hidden area on the page, need a pointer or touch screen. If you can’t draw, add your signature as an Image field (choose “Image” when adding a field), and use the keyboard-friendly ways to hide data described above. Typing a signature is not supported yet.
• formaster.app’s interface and the legal pages are in English only. The “Form language” feature translates a form’s questions with AI, so its accuracy depends on the model.
• AI suggestions need a person’s review. The review dialog shows the proposed placements as a picture of the page, next to a list that can be read and ticked with a screen reader.
• Some third-party components (the PDF engine’s rendering, the browser’s own file picker) are outside our control and follow your browser’s accessibility.

Reporting a problem

formaster.app does not yet have a built-in way to report accessibility problems. If you meet a barrier, please tell whoever provides this copy of formaster.app to you, and describe the page, what you were trying to do, and the browser and assistive technology you use.