Accessibility statement for the Prompt to Page desktop app

We aim for the app to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. That includes WCAG 2.0 AA, which the revised US Section 508 standards (and EN 301 549) reference for software, and WCAG 2.1 AA.

The app is partially conformant. Some parts do not yet fully meet the standard, as listed under Known limitations.

In September 2026 the app was reviewed against WCAG 2.2 AA and Section 508. Version 0.7.0 fixes every critical and major problem that review found. The fixes have been checked with automated tests, by keyboard, and in the macOS release build through the macOS accessibility interface — the same information VoiceOver reads. They have not yet been checked with screen readers (JAWS, NVDA or VoiceOver) or by disabled people, and the Windows build of 0.7.0 has not yet been checked. Until then, this statement makes no claim of full conformance.

An Accessibility Conformance Report (ACR, on the ITI VPAT® template) will be published after the screen-reader testing.

• Use the app's features from the keyboard, including choosing and editing a section of the preview (Edit section opens a list of the page's sections, which the arrow keys move through) and reordering pages (Move up / Move down in the page's actions).
• Find any command, and its keyboard shortcut, in the command palette: ⌘K on macOS, Ctrl K on Windows.
• Zoom the whole interface from 90% to 200% (Settings → Appearance → Interface zoom, or ⌘/Ctrl + and −). The layout reflows at 200%, and your choice is remembered.
• Choose a light or dark theme, or follow your system. Both themes are designed to meet the standard's contrast requirements, and every control shows a solid focus outline.
• Keep notifications on screen until you close them (Settings → Appearance). Press F6 to move to the latest notification and F6 again to go back.
• Set up the app from the keyboard: the choice between the built-in model, Ollama and LM Studio is a set of radio buttons, and the controls inside each option work normally.
• Be told about progress, errors and generation results by a screen reader. The app announces them without moving your focus, and announces a summary of an accessibility check instead of reading out every result.

Settings → Help & feedback has a short summary of these.

• Screen readers: the app has not yet been tested with JAWS, NVDA or VoiceOver. Names, roles and announcements follow the WAI-ARIA patterns and have been checked through the macOS accessibility interface, but some may read awkwardly.
• Windows: the accessibility fixes in 0.7.0 have been checked on macOS. The Windows build still needs to be checked, including Windows High Contrast themes, which have only been checked in an emulated browser.
• Menus: on macOS the menu bar (File, Edit, View, Window, Help) holds only system commands. It does not yet include app commands such as zoom or keyboard shortcuts, and the Help menu is empty. On Windows there is no menu bar. Every command is available from the command palette and in the interface.
• Help from the first screen: help and feedback can't be reached from the Welcome screen of first-run setup.
• Setting up the local AI again: Settings → Local AI → Set up local AI again has no way to go back to the app without finishing setup; quitting and reopening the app returns you to where you were, with your settings unchanged. When setup opens, keyboard focus starts at the top of the page rather than on its first control.
• Single-key shortcut: pressing ? when you are not typing in a text field opens the command palette. This single-key shortcut can't yet be turned off or changed.
• System display settings: the app does not yet follow the macOS Increase contrast or Reduce transparency settings.
• Text spacing: when letter, word and line spacing are increased, some labels in the header and the model file name are shortened with an ellipsis. This was found in the September review and has not been re-checked.
• Smaller details found in the 0.7.0 checks:
  • in a narrow window (about 1,000 pixels) with the preview at Fit, the Edit section instructions can cover the top section of the preview;
  • while the HTML source view is open, the disabled Edit section, Add section and Link pages buttons say to choose "View rendered preview", but that control's spoken name is "View and edit HTML source";
  • closing the command palette after opening it from inside the preview returns focus to the preview page rather than the control you were on;
  • a page reference inserted with @ in the chat box shows the page's internal ID until you send the message;
  • the summary shown after a journey is generated stays over the preview and has no close button.
• The preview: the preview shows the generated page as its design system renders it. Its own accessibility depends on the generated markup; check it with the built-in accessibility checker and by hand.
• Pointer dragging: reordering pages and resizing the page list can be done by dragging, and also by Move up / Move down, a double-click on the resize handle (preset widths) or the keyboard.

• An automated axe-core scan of the app's own interface, in light and dark themes, runs with the end-to-end tests. New violations fail the build.
• Tests walk every Tab stop in the main screens and check that each one shows a visible focus outline, including in an emulated forced-colours mode.
• Unit tests check the colour contrast of the design tokens, form-field borders and selected states, keyboard focus after opening and closing panels, and the wording of announcements.
• Before each release, the installed macOS release build is driven through the macOS accessibility interface. For 0.7.0 (26 September 2026) that covered interface zoom and reflow, notifications and F6, keyboard reordering, the accessibility check before export, Edit section by keyboard, the / and @ suggestions, focus when panels and dialogs open and close, control names, contrast and focus outlines in both themes, shortcuts from inside the preview, and first-run setup.

If you find something in the app that is hard to use with your assistive technology, or you need this information in another format, email courtney.rj.allen@gmail.com. Tell us what you were trying to do, the assistive technology you use and your operating system. You can also use Email feedback in Settings → Help & feedback, which fills in the app version for you.

This statement was first prepared on 24 September 2026 and updated on 26 September 2026 for version 0.7.0. It will be reviewed after the screen-reader testing described above, and again whenever a release changes the app's accessibility.