Skip to content

Accessibility Statement

PromptAbide aims to meet WCAG 2.1 AA. Here is what we have done, where we still fall short, and how to reach us.

Last updated:

1.Our commitment#

We want PromptAbide to work for everyone, including people who use screen readers, keyboard navigation, magnification, voice control or other assistive technology. Our target is to conform to the Web Content Accessibility Guidelines (WCAG) 2.1, level AA.

2.What we do#

  • Use semantic HTML, headings and landmarks, and label buttons, forms and icons for screen readers.
  • Support full keyboard navigation with visible focus.
  • Offer light and dark themes, and keep text contrast readable in both.
  • Respect your system’s “reduce motion” setting: scroll and entrance animations are turned off when it is on.
  • Build layouts that work from small phones to large screens, and at 200% zoom.
  • Check new features with automated accessibility tests and manual keyboard testing.

3.Known limitations#

  • User content. Images and outputs posted by users may not have useful text descriptions, and some AI outputs, such as generated images or audio, have no text equivalent.
  • Rich text editor. Some formatting controls in the editor may be hard to use with some screen readers.
  • Browser extension. The share sheet is drawn over third-party AI sites, whose own accessibility we do not control.
  • Embedded third-party content, such as sign-in pages from Google or GitHub, follows those providers’ standards.

4.Tell us about a barrier#

If something on PromptAbide is hard or impossible for you to use, or you need content in a different format, email hello@promptabide.com. Tell us the page, what you were trying to do, and the browser and assistive technology you use. We aim to reply within 5 business days and to fix problems as quickly as we can.