GPTree aims to meet WCAG 2.1 Level AA. Much of the product already works well with keyboards and screen readers, and this page lists the known gaps honestly. If anything blocks you, contact us and we will prioritize it.
Corgen LLC, the company behind GPTree, wants everyone to be able to use GPTree, including people who rely on assistive technology. Our target standard is the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA.
GPTree is currently partially conformant with that standard: most of the product meets it, and the known exceptions are listed in Section 3. Accessibility issues are triaged alongside functional bugs, and fixes that unblock core tasks, such as starting a conversation, branching, comparing, and merging, are prioritized first.
- Semantic page structure with landmarks, labeled navigation, and a logical heading order on public pages
- Labeled form fields, with screen-reader announcements for errors and status changes on sign-in, sign-up, and billing screens
- Confirmation dialogs that keep keyboard focus while open and close with the Escape key
- Text alternatives on meaningful images and icons across most of the product
- Keyboard shortcuts for common actions inside the app
- Reduced-motion preferences respected in the homepage animation
- A skip-to-content link on this page, a pattern we are extending across the site
We know about the following gaps. They come from our own accessibility review in July 2026 and are on our active roadmap.
- Parts of the conversation tree currently require a mouse: selecting a branch in the tree sidebar, moving a branch by dragging, and renaming by double click do not yet have keyboard equivalents
- Some dialogs do not yet return keyboard focus to the control that opened them when they close
- Brief popup notifications are not yet announced by screen readers
- Some small secondary text, such as timestamps and labels, does not yet meet the AA contrast ratio
- Product demo videos do not yet have captions or transcripts
Blocked by one of these? Contact us. There is usually a workaround we can walk you through while the fix ships.
We want to hear about any accessibility barrier, big or small. It helps to include the page or feature, what happened, and the browser and assistive technology you use. We aim to respond within five business days.
GPTree is built to work with recent versions of Chrome, Firefox, Safari, and Edge, on desktop and mobile. The mobile and desktop apps reuse the same interface as the web app, so accessibility improvements land everywhere at once.
This statement was prepared on July 16, 2026, based on an internal accessibility review of the product completed the same month. We will update it as the limitations above are fixed.
