Accessibility Statement

1. Our Commitment

We believe accessibility is a baseline, not a feature. Prompito is designed from the ground up to work for users of all abilities, whether you navigate by keyboard, use a screen reader, rely on voice control, or have low vision.

Our target is WCAG 2.1 Level AA conformance across the Prompito Chrome extension and all pages on prompito.com. Where we fall short, we want to know, and we commit to fixing it.

2. What We've Implemented

Chrome Extension (bubble and popup)

• The floating bubble pill is keyboard-focusable with role="button" and activates on Enter and Space
• The expanded panel carries role="dialog" and aria-label so screen readers announce it correctly
• All phase transitions are announced via an aria-live region with plain-language status text, e.g. "Step 2 of 3: The AI has finished responding. Click Check it to evaluate the output."
• aria-busy="true" is set during API calls so screen readers know content is loading
• The cycle progress bar carries role="progressbar" with aria-valuenow, aria-valuemin, and aria-valuemax
• The global enable toggle carries role="switch" with aria-checked synced on every change
• All icon-only controls have aria-label, minimize, close, brand icon, loading spinner
• After each phase transition, keyboard focus moves automatically to the primary action button
• Decorative elements are marked aria-hidden="true" throughout
• The industry switcher dropdown uses role="listbox" with aria-selected on each option
• The privacy warning banner uses role="alert" for immediate screen reader announcement
• All form inputs in the popup carry explicit aria-label attributes
• The delete account confirmation uses role="alert" and aria-describedby
• Visible :focus-visible rings on every interactive element, keyboard users always see where they are

Website pages (prompito.com)

• Skip-to-main-content link on every page, keyboard users bypass the navigation header
• aria-label="Site navigation" on every <nav> element
• aria-current="page" on the active navigation link
• All data tables use scope="col" on header cells
• All sidebar navigation uses aria-label="Table of contents"
• Content areas use <main> with id="main-content" as the skip link target
• All SVG brand icons carry aria-hidden="true" and focusable="false"
• Colour contrast ratios meet or exceed WCAG 2.1 AA (4.5:1 for normal text, 3:1 for large text)
• All pages specify lang="en" and force light colour scheme to prevent unintended dark mode inversion

3. WCAG 2.1 AA Coverage

The table below documents our conformance status against the WCAG 2.1 Level AA success criteria most relevant to our product type.

4. Known Limitations

We are transparent about what is and is not within our control.

Third-party AI platform interfaces

Prompito operates as a layer on top of ChatGPT (OpenAI), Claude (Anthropic), and Gemini (Google). The accessibility of those platforms, their input fields, response areas, and navigation, is governed entirely by those companies and is outside our control. If you experience accessibility issues with those interfaces, we encourage you to report them directly to OpenAI, Anthropic, or Google respectively.

Claude artifact iframes

When Claude generates an artifact displayed in a sandboxed iframe, Prompito cannot read its contents, this is a hard browser security boundary (cross-origin isolation), not an accessibility limitation. Prompito handles this with the ARTIFACT_VERIFY flow, which provides a structured alternative path that is fully keyboard-accessible.

Shadow DOM and focus management

The Prompito bubble is injected using a closed shadow DOM to prevent style conflicts with AI platform pages. In rare cases, certain screen reader and browser combinations may experience minor inconsistencies navigating between the host page and the Prompito shadow DOM. If you encounter this, please report it to us, we treat these reports as high priority.

Automated focus movement

After phase transitions, Prompito moves keyboard focus to the primary action button. This only occurs when a keyboard interaction triggered the transition. If you find this behaviour disorienting in any specific flow, please let us know.

5. Assistive Technologies Referenced During Development

Our accessibility implementation was developed with the following assistive technology and browser combinations in mind:

• NVDA with Chrome on Windows
• JAWS with Chrome on Windows
• VoiceOver with Safari on macOS
• VoiceOver with Chrome on iOS (mobile)
• Keyboard-only navigation on Chrome (Windows and macOS)

If you use an assistive technology not listed here and encounter issues, please contact us. We will investigate and update our implementation accordingly.

6. How to Use Prompito With a Keyboard

Every function in Prompito is reachable by keyboard alone. Here is how to navigate the key interactions:

Opening the bubble

Tab to the Prompito pill in the bottom-right corner of any supported AI platform page. Press Enter or Space to open it.

Enhancing a prompt

When your prompt crosses the activation threshold, the pill label changes to "Enhance →". Tab to it and press Enter or Space to trigger enhancement.

Using the enhanced prompt

After enhancement loads, focus moves automatically to the "Use this prompt" button. Press Enter to insert it into the AI input field.

Checking the AI output

When the AI finishes responding, focus moves to the "Check it" button. Press Enter to trigger evaluation.

Minimising and closing

Tab to the − (minimise) or × (close) buttons in the panel header and press Enter.

Switching industry profile

Tab to the industry switcher in the bubble header. Press Enter to open the dropdown. Use arrow keys or Tab to navigate options. Press Enter to select.

Extension popup

Click the Prompito icon in your browser toolbar or use your browser's keyboard shortcut to open extensions. All settings, toggles, and actions are fully keyboard-navigable within the popup.

Keyboard shortcut, manual output check

You can manually trigger an output evaluation by selecting any text on the page and pressing Ctrl+Shift+P (Windows) or Cmd+Shift+P (Mac).

7. Feedback and Contact

We welcome accessibility feedback. If you find something that doesn't work, is hard to use, or could be improved for assistive technology users, please tell us. We review all accessibility reports and respond within 5 business days.

When reporting an issue, it helps to include:

• The assistive technology and version you are using
• Your browser and operating system
• Which AI platform you were on (ChatGPT, Claude, or Gemini)
• A description of what you were trying to do and what happened instead

8. Enforcement

If you are not satisfied with our response to an accessibility complaint, you have the right to escalate to the relevant authority in your jurisdiction:

• European Union: Your national authority responsible for enforcing the European Accessibility Act
• United Kingdom: The Equality and Human Rights Commission (EHRC)
• United States: The US Department of Justice Civil Rights Division

We encourage you to contact us first, we genuinely want to fix issues, and direct contact is the fastest path to resolution.