Guide

FAQs

1. How does the integration process work and how long does it take to get set up?

Answer: The TestParty integration process typically takes 3 one-hour meetings to complete the full setup. During these sessions, we'll configure each tool (Pregame IDE extension, Bouncer PR bot, and Spotlight scanner) in your development environment. For enterprise clients, the complete setup usually takes about a week, though with proper permissions it can be done in just a few hours. The main steps are: connecting your GitHub/GitLab/BitBucket repository, installing our tools, and configuring scanning parameters for your specific needs.

2. What's the difference between TestParty and overlay solutions like AccessiBe or AudioEye?

Answer: Unlike overlay solutions that add a widget on top of your website, TestParty fixes accessibility issues at the source code level. Overlays can only address surface-level issues like color contrast or text size, but cannot fix structural problems like heading order or improperly tagged frames. TestParty integrates directly into your development workflow to identify and fix issues before they reach production, providing true WCAG compliance rather than a cosmetic solution.

3. How much does TestParty cost and what pricing models are available?

Answer: TestParty pricing is based on your e-commerce revenue tier or number of projects. For e-commerce sites, pricing ranges from $0-1M revenue tier up to $100M+ tiers. We offer volume discounts starting at 25% off for 3+ sites. Annual contracts provide better rates than monthly billing. We also offer custom enterprise pricing and can price-match competitors when appropriate. Contact sales for a detailed quote based on your specific needs.

4. Can TestParty scan our entire website or is it limited to a certain number of pages?

Answer: TestParty can scan your entire website without page limitations. Unlike competitors who limit scanning to 5-15 pages, we scan all pages you specify via sitemap or URL list. Our system can scan approximately 5,000 pages in 5 minutes, and even sites with 100,000+ pages can be fully scanned in about 2 hours during nightly scans.

5. How quickly can we achieve WCAG compliance using TestParty?

Answer: For standard implementations, TestParty can help you achieve WCAG compliance within 2 weeks of setup. This includes initial scanning, issue identification, and remediation support. For sites requiring more complex fixes or custom development work, the timeline may extend based on your team's capacity to implement the recommended changes.

6. What reports and documentation does TestParty provide?

Answer: TestParty automatically generates comprehensive accessibility reports including:

  • ACRs (Accessibility Conformance Reports) and VPATs generated in 1-2 minutes

  • Daily scanning reports with issue details, screenshots, and fix instructions

  • Executive summaries and designer-specific views

  • Exportable reports for vendors and legal documentation

  • Compliance tracking dashboards showing progress over time

7. Does TestParty require access to our source code?

Answer: For full functionality, TestParty integrates with your version control system (GitHub, GitLab, BitBucket) to provide development-time fixes. However, our Spotlight scanner can work with just public URLs for production monitoring. The level of access depends on which tools you implement - Pregame requires IDE integration, Bouncer needs repository access for PR reviews, while Spotlight only needs your website URLs.

8. How does TestParty handle manual testing requirements?

Answer: While TestParty automates the majority of WCAG testing, we acknowledge that some criteria require manual testing (like focus order and certain keyboard navigation patterns). Our platform clearly identifies which issues can be automatically tested versus those requiring manual review. We're developing AI-enabled voiceover and keyboard testing tools to expand automated coverage.

9. What legal protection does TestParty offer against ADA lawsuits?

Answer: While TestParty doesn't offer direct legal insurance like some competitors, our continuous monitoring and compliance approach significantly reduces lawsuit risk. We've seen customers who do get sued settle for 90% less (e.g., $2,000 instead of $20,000) due to documented good-faith compliance efforts. Our detailed reporting provides strong evidence of ongoing accessibility maintenance.

10. Can TestParty integrate with our existing development workflow and tools?

Answer: Yes, TestParty is designed to integrate seamlessly with modern development workflows:

  • IDE support through Pregame extension (VS Code and others)

  • CI/CD integration via GitHub Actions, GitLab CI, or custom YAML files

  • Ticketing system integration (Jira, Azure DevOps)

  • API access for custom integrations

  • Slack/Teams notifications for issue alerts

11. How does TestParty identify and fix accessibility issues?

Answer: TestParty uses AI-powered scanning to identify WCAG violations across three stages:

  1. Development: Pregame provides real-time accessibility "spell check" in your IDE

  2. Pre-production: Bouncer reviews pull requests and suggests specific code fixes

  3. Production: Spotlight continuously monitors live sites and generates detailed fix instructions with screenshots showing exact issue locations

12. What's included in the Proof of Concept (PoC) process?

Answer: A typical PoC runs for 2-6 weeks and includes:

  • Initial setup of one project with selected TestParty tools

  • Configuration for scanning a subset of critical pages

  • Training for your development team

  • Weekly check-ins to review findings and adjust configuration

  • Final assessment of accessibility improvements and ROI analysis

13. Can TestParty handle complex, custom-built sites or just standard platforms?

Answer: TestParty works with any web-based platform, from simple Shopify sites to complex custom applications. We support:

  • Standard e-commerce platforms (Shopify, Magento, WooCommerce)

  • Custom frameworks (React, Vue, Angular, Next.js)

  • Enterprise CMS systems (Drupal, WordPress)

  • Headless architectures and progressive web apps

  • Multi-site and multi-language implementations

14. How does TestParty handle PDF accessibility?

Answer: Currently, TestParty focuses on web accessibility and does not provide automated PDF remediation. We experimented with PDF-to-accessible-HTML conversion but found technical limitations with Adobe's locked-down format. For organizations with extensive PDF content, we recommend partnering with specialized PDF remediation services while using TestParty for web content.

15. What support and training does TestParty provide?

Answer: TestParty offers comprehensive support including:

  • Onboarding sessions with dedicated customer success managers

  • Developer documentation and API guides

  • Weekly office hours for technical questions

  • Slack/Teams channel for real-time support

  • Regular check-ins during the first month

  • Ongoing training as new features are released

  • Access to our knowledge base at docs.testparty.ai