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, and version 0.7.0 fixed every critical and major problem that review found. Version 0.7.0 was tested on 26 September 2026, on macOS through the macOS accessibility interface and on Windows with the NVDA screen reader and two Windows Contrast themes. Version 0.7.1 fixed the blocking and major problems those tests found.

Between 27 September and 5 October 2026, version 0.7.1 and the release candidates of 0.7.2 were tested in the installed app:

• on Windows, with the NVDA 2026.2 and JAWS 2026 screen readers, the Night sky and Desert Contrast themes, Windows text size at 200% with the interface zoomed up to 200%, and the Windows UI Automation tree. JAWS was used with version 0.7.1 only;
• on macOS, from the keyboard through the macOS accessibility interface, with the VoiceOver screen reader, with Increase contrast turned on, and with the interface zoomed to 200%.

An AI agent ran all of these tests. It drove the app with key presses and recorded what each screen reader said: from NVDA's log, from JAWS's speech history, and from VoiceOver's caption panel. The owner switched the system settings, such as the Contrast theme and the text size.

Version 0.7.2 fixes the problems those tests found, apart from those listed under Known limitations. On macOS, most of the fixes were checked in the installed release candidates, and the published 0.7.2 build was checked on 5 October 2026; the rest, such as following Reduce transparency on its own, were checked by automated tests. On Windows, the last release candidate to be tested still had problems that 0.7.2's code now fixes: NVDA read some questions and tour steps more than once and cut off two confirmations, some parts of the workspace did not fit a very small window, and unavailable buttons were faint in a light Contrast theme. 0.7.2 was released for Windows on 6 October 2026 before those fixes were checked with NVDA, in a Contrast theme or at Windows text size 200%, so they are still to be checked. The released Windows build was checked from the keyboard and with the interface zoomed to 200%, without a screen reader.

The app has not yet been tested by a person who uses a screen reader, by disabled people, or with Voice Control, Voice Access or Dragon. Until then, this statement makes no claim of full conformance.

An Accessibility Conformance Report (ACR, on the ITI VPAT® template) will be published after people who use screen readers have tested the app.

• 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.
• On macOS, use the app's commands from the menu bar: File, View and Help hold them, with their keyboard shortcuts. Help → Accessibility Help opens a summary of these features, and Help → Accessibility Statement opens this statement.
• 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.
• On macOS, turn on Increase contrast for solid borders and field edges, darker secondary text and opaque panels, or Reduce transparency for opaque panels and dialogs.
• Use a Windows Contrast theme: selected tabs and pressed buttons are marked with a thick edge in your theme's highlight colour.
• Answer every "Are you sure?" question in the app's own dialog, which starts on Cancel, closes with Escape, is read in full, and follows the interface zoom and text size.
• Keep notifications on screen until you close them (Settings → Appearance). Press F6 to move to the latest notification and F6 again to go back. A notification with an action, such as Undo, stays for at least 20 seconds.
• 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. Every step of setup has Help & feedback, and Set up local AI again can be cancelled without changing your settings.
• 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. Each issue the check finds lists the elements that fail, with their markup.

On Windows, the app's own question dialogs and the 20-second notifications are new in 0.7.2. Settings → Help & feedback has a short summary of these.

• Screen readers:
  • No person who uses a screen reader has tested the app yet, and JAWS has been used with version 0.7.1 only.
  • When a dialog opens, NVDA may read its name twice.
  • NVDA says "clickable" at the top of the window and before the main area.
  • The handle for dragging a page to a new position needs the screen reader's focus mode switched on by hand, in NVDA and in JAWS. Use Move up and Move down in the page's actions instead.
  • Some messages are read twice or include something old. Adding a section reads its result twice, and choosing where a section goes reads two instructions. When a journey finishes, the announcement can include an earlier reply. In setup, "Local AI ready" is read before the start-up steps after you switch the runtime, and it is read with "Starting local AI" when you choose the model that is already running.
  • Some text runs together for NVDA and JAWS: a page's name and its path in the page list, and the parts of a model's card in setup.
  • The six service templates are each a Tab stop, although screen readers are told they are options in a list.
  • With JAWS (version 0.7.1): the Sections list's hints are read twice, and "Not selected" before every section; changing Interface zoom in Settings is silent; and in Projects, Start with another design system reads the previous heading.
• Keyboard focus: after you choose where to add a section, focus moves into the preview's page while the section is generated.
• Windows: 0.7.2 fixes the following on Windows, but the fixes have not yet been checked there with NVDA or JAWS, in a Contrast theme or at Windows text size 200%, so they may still happen:
  • NVDA may read some questions and tour steps more than once, and cut off the confirmations after Delete and Undo in the Sections list.
  • JAWS may read a question dialog as a lone button, without the question, as it did with the system dialogs in 0.7.1.
  • In a light Contrast theme, unavailable buttons may be faint.
  • At Windows text size 200% with the interface also zoomed to 200%, some parts of the workspace may not fit the window.

  If you still have version 0.7.1, everything 0.7.2 fixes is still present in it; the 0.7.2 release notes list those fixes, and Settings → Updates brings the app up to 0.7.2.

  On every Windows version, after the last control in the window, Tab makes one stop that nothing is announced for, before it returns to the top. This comes from the Windows web view the app runs in. There is no menu bar on Windows: every command is in the command palette and the interface. Windows' Transparency effects setting has not yet been tested.

• Menus on macOS: the menu item Show Share & Export is read without its "&". The menus have not yet been checked with VoiceOver.
• System display settings: on macOS, the app has been checked in an installed release candidate with Increase contrast and Reduce transparency both on. Reduce transparency on its own has been checked by automated tests only.
• Contrast and focus:
  • Some dimmed text may be below 4.5:1: the setup steps not reached yet, and the accessibility panel's issue rows while a fix is being generated. This was worked out from the colour values and has not been measured.
  • In a Windows Contrast theme, a Share & Export button that is busy may look available. This was found in the code and has not been seen in a test.
  • The focus outline on the handle that resizes the page list is thin. Whether it is visible enough has not yet been checked by eye.
• Small windows: in a window narrower than about 770 pixels, the header's labels and the model and project names shorten to one line; their full text is still available to assistive technology. At 200% interface zoom in a small window (1024 × 800), the chat box has no room for its hint about / and @.
• Structure: the expanded page list is a region without a name, and the window's title is always "Prompt to Page", not the project's name.
• Exports: the assessment-evidence export (EVIDENCE.html) has a main region and a level-1 heading for each page it includes.
• Smaller details:
  • a page reference inserted with @ in the chat box shows the page's internal ID until you send the message;
  • when you move a section, the position announced counts every section on the page, although a section only moves within its own group;
  • an error in a form field opens the whole troubleshooting panel, instead of being shown at the field.
• 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 before each release. Any new violation fails the run.
• 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, that every control the app dims when it is unavailable stays readable in a Contrast theme, keyboard focus after opening and closing panels, and the wording of announcements.
• End-to-end tests emulate Windows Contrast themes, light and dark, and check that selected and pressed controls and notifications stay visible and readable. Others check that a control you move to inside the preview is scrolled into view, that the interface reflows at 200% zoom and with wider text spacing, that small buttons are at least 24 × 24 pixels, that the app follows the contrast and transparency settings, and how the app's dialogs appear in the accessibility tree. The interface-zoom check also runs in WebKit, the engine the macOS app uses.
• Before each release, the installed macOS build is driven through the macOS accessibility interface, with real key presses. For 0.7.2 this ran on the release candidates from 29 September to 5 October 2026. It covered keyboard journeys, focus after actions and in dialogs, the menu bar, interface zoom at 200%, and Increase contrast, with the owner switching the setting. On 30 September it also covered VoiceOver, whose speech was read from its caption panel. The last two release candidates, the second of them the published build, were checked on 4 and 5 October: the core flows on both of the app's local AI runtimes, focus after Undo, Apply and Dismiss, notifications and the menu bar.
• The installed Windows app is tested from the keyboard. On 27 and 28 September 2026 that covered version 0.7.1:
  • NVDA 2026.2 and JAWS 2026;
  • the Night sky and Desert Contrast themes, with the owner switching them;
  • Windows text size 200%, with the interface zoomed up to 200%;
  • the UI Automation tree, with Accessibility Insights for Windows.

  Between 30 September and 4 October, the 0.7.2 release candidates were re-tested with NVDA, both Contrast themes, text size 200% and the UI Automation tree. On 5 and 6 October the released 0.7.2 build was checked from the keyboard, without a screen reader: the core flows, focus after Undo, Apply and Dismiss, check-answers playback, notifications, and the layout with the interface zoomed to 200%. An AI agent ran every Windows test, not a person who uses a screen reader.

• On 26 September 2026 the installed Windows build of 0.7.0 was tested with NVDA 2026.2 and the Night sky and Desert Contrast themes, following a written test script. An AI agent ran the test. It found one blocking and 14 major problems, and 0.7.1 fixed all of them, and most of the minor ones.

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 last updated on 6 October 2026 for version 0.7.2. It will be reviewed when 0.7.2's Windows fixes have been checked with NVDA, JAWS and a Contrast theme, after people who use screen readers have tested the app, and whenever a release changes the app's accessibility.