Accessibility statement.

01Our commitment

BooksGPT, Inc. is committed to making both our marketing site (booksgpt.ai) and our application (app.booksgpt.ai) usable by everyone, regardless of ability or assistive technology. We believe accessibility is a feature, not a checkbox, and we maintain it the same way we maintain anything else customers depend on. We test, we measure, we fix.

02Standard we target

Our conformance target is Web Content Accessibility Guidelines (WCAG) 2.1 Level AA, published by the W3C. This is the standard referenced by US Section 508, the EU Web Accessibility Directive, and the UK Public Sector Bodies Accessibility Regulations.

We also voluntarily comply with the relevant portions of WCAG 2.2 where they apply to a books-software workflow (target size, dragging movements, focus appearance). When WCAG 3.0 reaches a stable Candidate Recommendation, we plan to evaluate against it as well.

03Scope

This statement covers:

• Marketing site at booksgpt.ai, including all pages reachable from the main navigation, footer, and articles.
• Application at app.booksgpt.ai, including the dashboard, transactions, invoicing, reports, settings, and year-end handoff flows.
• API documentation at docs.booksgpt.ai.
• Email templates we send transactionally (invoices, monthly close, refund receipts).

Out of scope for this statement: PDFs produced by you for your CPA (those follow your input formatting), third-party services we link to, and inline AI-generated content where you have not approved it.

04How we test

We test in three layers:

• Automated. Axe DevTools, Lighthouse, and Pa11y run in CI on every pull request. Builds fail on any Critical or Serious violation introduced by the change.
• Manual. Every shipped feature gets a keyboard-only walkthrough, a screen-reader walkthrough on VoiceOver and NVDA, and a 200% zoom check.
• Third-party audit. A WAS-certified accessibility auditor reviews the full product against WCAG 2.1 AA each quarter. The most recent audit was completed on April 4, 2026.

05Known limitations

We do not believe perfect accessibility is real. Honest list of where we are not yet conformant:

06Accessibility features

What we build in by default:

• Keyboard navigation. Every interactive element is reachable by Tab. Focus indicators are visible at 3:1 contrast minimum. Skip-to-content link on every page.
• Semantic HTML. Real headings (h1 through h4), real landmarks (header, nav, main, footer), real lists. ARIA only where native semantics fall short.
• Color contrast. Body text at 7:1 (AAA). Large text and UI components at 4.5:1 minimum (AA). Our accent green sits at the high end of contrast for green colors at this brightness.
• Reduced motion. We respect prefers-reduced-motion on the marketing site, app, and emails. The live-dot pulse and countdown digits are the two exceptions we are working to fix (see known limitations).
• Resize and zoom. The site reflows cleanly at 200% browser zoom and 400% on a 1280-pixel viewport. Tables become scrollable horizontally rather than truncating.
• Forms. Every input has an associated label. Errors are announced to screen readers and described in text, not by color alone.
• Alternative text. Decorative images carry empty alt. Informative images carry meaningful alt. SVG icons used as the sole content of a link carry an aria-label.
• Captions and transcripts. Our product walkthrough videos carry closed captions and a downloadable transcript.

07Tested assistive tech

We regularly test BooksGPT against:

• Screen readers. VoiceOver on macOS 14 and iOS 17. NVDA on Windows 11 with Firefox and Chrome. JAWS 2025 on Windows 11 with Chrome.
• Speech recognition. macOS Voice Control. Windows Speech Recognition. Dragon Professional Individual 16.
• Switch control. Apple Switch Control via the on-screen keyboard and a single external switch.
• High-contrast. Windows High Contrast modes (Black and White). macOS Increase Contrast.
• Zoom and magnification. macOS Zoom up to 8x. ZoomText on Windows.

08Audit cadence

We commission an external WCAG 2.1 AA audit every quarter. The auditor's report is shared with us, we publish a summary on this page within 30 days, and we maintain a public log of resolved findings. If you would like the full audit report (we share it under NDA on request), email [email protected].

09Reporting an issue

If you find something on booksgpt.ai or app.booksgpt.ai that is not accessible to you, please tell us. We will not ask you to debug. We will fix it.

• Email: [email protected]. Replies within 1 business day, fix targets within 14 days for AA-blocking issues.
• Phone: 1-800-BOOKS-AI (1-800-266-5724). 9am to 6pm Pacific, Monday to Friday.
• Mail: BooksGPT, Inc. Attn: Accessibility, 1455 Market St #600, Oakland, CA 94612.

When reporting, helpful (but not required) details: the URL where you hit the barrier, the assistive tech you were using, what you were trying to do, and what happened instead. We will credit you in the release notes when we ship the fix if you would like.

10Formal complaints

If we do not resolve your report to your satisfaction, you can escalate:

• United States. File a complaint with the US Department of Justice under the Americans with Disabilities Act at ada.gov.
• European Union. File with your national accessibility enforcement body listed at ec.europa.eu.
• United Kingdom. File with the Equality and Human Rights Commission at equalityhumanrights.com.

We will not retaliate, deprioritize, or otherwise penalize you for filing a complaint. We genuinely want to know when we have fallen short.