When OnPath Testing joined the ClearCaptions project in early 2017, the goal was clear: support a growing development team with disciplined system testing that ensured stability, usability, and real-world reliability. This accessibility phone case study shows how comprehensive QA practices helped the ClearCaptions Blue phone scale successfully to thousands of users.
Project Overview: QA Support From Day One
OnPath Testing entered the engagement as an external QA partner to complement an already active development effort. While developers understood the importance of quality, the project required structured end-to-end testing to validate complex interactions between software, hardware, and telecom infrastructure.
Initially, the mandate focused on manual validation. Over time, the scope expanded as new risks and dependencies emerged. This evolution played a key role in ensuring broad user acceptance and long-term product success.
White Paper: How OnPath Unlocked a Stalled Software Project
Learn how QA can do more than find bugs — read our white paper to learn how OnPath’s approach reduces stress, restores momentum, and protects ROI through strategic alignment and faster release cycles.
About ClearCaptions and the Blue Phone
ClearCaptions is a U.S.-based technology company dedicated to improving communication for individuals with hearing loss. Its flagship product, the ClearCaptions Blue phone, delivers real-time captions during phone calls while maintaining a familiar desktop phone experience.
The device combines a touchscreen-driven application with physical hardware and live telephony services. This combination made integrated system validation essential, as failures could originate from software logic, hardware components, or network behavior.
Why System-Level Validation Was Critical
The Blue phone operates as an Android-based application embedded within a physical device. Users interact with both digital and analog elements, including handsets, speakerphones, and traditional telephone networks.
QA validation covered scenarios such as:
- Dial tone behavior during on-hook and off-hook states
- DTMF tone accuracy
- Automatic call initiation timing
- Interaction with PSTN and router-based services
This complexity meant that only full-system quality testing could accurately assess real-world behavior.
Background: Building the QA Team and Process
QA engagement began several months into development. While not ideal, this timing still allowed OnPath to quickly establish structured processes. The initial QA team consisted of three manual test engineers, scaling later to five testers and a QA Manager as development expanded.
Automation was evaluated but deprioritized because the product relies on human perception and live interaction—factors that are difficult to simulate programmatically.
Project Goals and Expanding QA Scope
The original goal was straightforward: provide immediate quality feedback and testing coverage. However, deeper involvement revealed gaps that required broader QA ownership.
Key challenges included:
- Lack of formal change and requirements management
- Insufficient internal testing tools
- Communication breakdowns between engineering, sales, and support
- Unclear ownership of defects across sprints
Addressing these issues was central to ClearCaptions Blue phone reaching 10,000 users with QA support from OnPath.
Methodology and Tools Used
The team followed a two-week sprint cadence and received builds at the end of each cycle. JIRA and Confluence served as core defect and documentation platforms, while early test tracking relied on spreadsheets.
As test coverage expanded, the team transitioned to TestRail for scalable test management. This shift improved visibility, reporting accuracy, and execution discipline—critical for ongoing end-to-end testing.
Outbound references for context:
- Agile QA best practices
- System testing methodologies
- Accessibility testing standards
Overcoming Regression and Communication Challenges
Recurring regression issues emerged as a major risk. Features validated in one sprint often broke in the next. To address this, QA implemented a structured prioritization approach:
- Smoke and compliance tests ran immediately after each build
- Targeted testing focused on sprint-specific changes
- Regression and scenario-based testing were followed before sprint closure
In parallel with testing improvements, QA leadership enhanced cross-team communication by creating automated dashboards and shared reporting views. These changes reduced confusion and improved support readiness.
Results: Measurable Growth and Stability
With structured QA support, the ClearCaptions Blue phone reached nearly 10,000 users and logged over 70,000 sessions within ten months of launch. Week-over-week growth reached 155%, reflecting strong user adoption within a niche audience.
The QA team managed nearly 2,000 test cases across nine suites, producing thousands of actionable defect reports that informed ongoing development.
Evaluation and Lessons Learned
This accessibility phone case study demonstrates how disciplined integrated system validation supports complex, real-world products. While the project succeeded, one key lesson emerged: migrating earlier to professional test management tools would have reduced risk even further.
Ultimately, success came from meeting release milestones, maintaining transparency, and restoring trust across teams—hallmarks of effective QA leadership.
Frequently Asked Questions (FAQs)
Why was system testing critical for the ClearCaptions Blue phone?
Because the product combines software, hardware, and live telephony services, failures could occur across multiple layers.
What made this accessibility phone case study unique?
The need to validate real-time captions, audio behavior, and physical interactions created uncommon testing challenges.
Why was automation limited in this project?
Many behaviors required human perception, making manual validation more effective than scripted automation.
How did QA reduce regression issues?
By prioritizing smoke tests, targeted validation, and structured regression cycles each sprint.
What tools supported full-system quality testing?
JIRA, Confluence, TestRail, and custom dashboards enabled tracking, reporting, and collaboration.
What is the key takeaway from this case study?
Strong QA processes and communication can scale complex accessibility products successfully.
