Accessibility statement

Last updated: Nov 6, 2026

1. What this statement covers

Exotool, LLC generates web apps from a visual design. This statement is about the apps Exotool generates: the page, the screens, the forms, the dialogs and the theme that every generated app is made of. The builder of an app adds its content, its texts, its images and sometimes its own HTML templates and styles; the builder remains responsible for those, as the Terms of Service say (section 2.d). The Exotool editor, the tool builders use, and this web site are not covered by this statement.

2. Our target

Generated apps target the Web Content Accessibility Guidelines (WCAG) 2.1 at level AA, the level named by EN 301 549 in the European Union and by the US Department of Justice rule under Title II of the ADA. The generator makes this the default: a builder does nothing to get it, and has to go out of their way to lose it.

3. What the generator does by default

  • The page declares its language (the app's language setting, English when none is set) and never blocks pinch-to-zoom.
  • Every form control has a label bound to it; a control without a visible label is named from its placeholder or title.
  • An action is a button and a link is a link: form buttons are real buttons, a link that only runs an action is announced as a button, and a link that shows only an icon (such as the back arrow) carries its name.
  • Images are named from their title, or hidden from assistive technology when they are decorative.
  • Keyboard focus is always visible, and the keyboard reaches every control, including the buttons of alert, confirm and prompt dialogs and action sheets; focus moves into a dialog when it opens and back where it was when it closes.
  • Dialogs are announced as dialogs with their title; notifications are announced as status messages.
  • The theme presets (Clean, Glass, Expressive and High contrast, in their light and dark variants) keep every text colour at a contrast of at least 4.5:1 against its background, and the High contrast preset underlines text links and widens its targets.
  • The layout respects the safe areas of current phones and does not lose the bottom toolbar under the home indicator.

4. How we test

We run axe-core (version 4.10.2, the WCAG 2.1 A and AA rule set) in a headless browser over the sample apps of the App Library and over test apps built for the purpose, on every screen, signed out and signed in, and we review the dialogs and the keyboard path by hand. As of this statement the generator's own markup produces no axe-core violation on those apps. Findings that remain come from the samples' own styles and are fixed in the samples themselves.

5. Known limitations

  • The Classic theme, the look generated apps had before November 2026 and kept for existing apps, uses the colours of the underlying UI library, some of which fall short of the 4.5:1 contrast on links (a link inside a form's label block, for example). Switching the app to a theme preset removes this.
  • Third-party content an app embeds (a map, a video player, a payment form) is accessible to the extent its provider makes it so.
  • HTML templates and styles a builder writes are the builder's, and a builder can lower the contrast or remove a label the generator gave.
  • Automated tests find most but not all problems; we have not had a third-party audit.

6. Conformance report (VPAT)

An Accessibility Conformance Report in the VPAT 2.5 format, WCAG edition, is available on request from info@exotool.com, for the generated apps as they stand at the date above.

7. Tell us

If you find something in a generated app that does not work with your assistive technology, write to info@exotool.com or use the contact page, and say which app and which screen. If the cause is in the generator we fix it there, so every app gets the fix at its next build.