The False Promise of Automated Accessibility Testing: Why Manual Audits Still Matter

Introduction: The Testing Methodology Crisis in Digital Accessibility

The accessibility testing landscape faces a fundamental paradox. Despite sophisticated automated testing tools, comprehensive standards like WCAG 2.1, and emerging frameworks such as the W3C's ACT Rules Format 1.1, 96.3% of websites still fail basic accessibility checks. This persistent failure rate, documented across multiple industry studies, reveals a critical gap between our testing methodologies and their real-world effectiveness in creating accessible experiences for disabled users.

The promise of automated accessibility testing has been compelling: comprehensive coverage, consistent results, integration into development workflows, and cost-effective scalability. Organizations have invested heavily in automated testing solutions, believing they could achieve accessibility compliance through technological efficiency. Yet recent Department of Justice settlements and accessibility audits reveal that automated testing alone consistently misses barriers that significantly impact disabled users' ability to access digital services.

This research examines the tension between automated testing capabilities and manual audit practices, analyzing why neither approach alone delivers the accessibility outcomes that disabled users need and organizations require for genuine compliance. Through analysis of recent enforcement patterns, industry practices, and emerging standards, we identify the specific limitations of each methodology and propose a framework for hybrid approaches that leverage the strengths of both.

The stakes of resolving this testing methodology crisis extend beyond compliance. As digital services become essential infrastructure for healthcare, education, employment, and civic participation, ineffective testing approaches perpetuate systematic exclusion of disabled people from full social and economic participation. Organizations that develop more effective testing methodologies will not only reduce legal exposure but also expand their customer base and improve user experiences for all users.

Current State of Accessibility Testing: A Tale of Two Approaches

The Rise and Limitations of Automated Testing

Automated accessibility testing has evolved significantly over the past decade. Tools like axe-core, WAVE, and Lighthouse now integrate seamlessly into development workflows, providing immediate feedback on technical accessibility violations. The W3C's recent publication of ACT Rules Format 1.1 represents a major step toward standardizing automated testing approaches, creating "a common language for automated tools and manual audits" that addresses the historical problem of inconsistent results across testing platforms.

The appeal of automated testing is undeniable. Development teams can run thousands of tests in minutes, catching obvious violations before code reaches production. Automated tools excel at detecting:

• Missing alternative text on images
• Insufficient color contrast ratios
• Missing form labels
• Keyboard navigation barriers
• Semantic HTML structure problems
• Focus management issues

These capabilities have transformed accessibility testing from a manual, time-intensive process to an integrated part of continuous integration pipelines. Organizations can now monitor accessibility across hundreds of pages simultaneously, track compliance metrics over time, and catch regressions before they impact users.

However, automated testing's greatest strength—its ability to detect technical violations—also reveals its fundamental limitation. Automated tools cannot evaluate whether accessibility features actually work for disabled users in real-world contexts. They can detect that alternative text exists but cannot assess whether it provides meaningful information. They can verify that keyboard navigation is technically possible but cannot evaluate whether the navigation sequence makes logical sense to users.

Recent analysis of accessibility litigation reveals this gap starkly. DOJ settlements consistently highlight barriers that automated tools miss:

• Shopping cart functionality that technically meets WCAG requirements but creates unusable workflows for screen reader users
• Product filtering systems with proper ARIA labels that nonetheless confuse users with cognitive disabilities
• Form validation that provides programmatic error messages but delivers them in ways that interrupt assistive technology users' mental models

Manual Audits: The Irreplaceable Human Element

Manual accessibility audits, conducted by experienced accessibility professionals using assistive technologies, remain the gold standard for comprehensive accessibility evaluation. Manual auditors can:

• Evaluate user experience workflows across multiple pages
• Test with actual assistive technologies in realistic usage scenarios
• Assess cognitive load and usability for users with different disabilities
• Identify context-dependent barriers that automated tools cannot detect
• Evaluate whether technical compliance translates to functional accessibility

The recent DOJ settlement with a major banking institution illustrates manual auditing's irreplaceable value. While the bank's automated testing showed WCAG compliance for their mobile authentication system, manual testing revealed that the multi-factor authentication flow created impossible barriers for users with certain motor disabilities. The technical implementation met automated testing criteria, but the user experience excluded disabled customers from essential banking services.

Manual audits also excel at evaluating emerging accessibility requirements that automated tools haven't yet addressed. The W3C's new Cognitive Accessibility Research Modules identify barriers in "voice systems, navigation, online safety, and decision-making" that require human judgment to evaluate. As one accessibility professional noted, "Cognitive accessibility barriers often emerge from the interaction between multiple technically compliant elements—something only human evaluators can assess."

However, manual audits face significant practical limitations:

• Scale constraints: Manual audits typically cover 10-50 pages, while modern applications may have thousands of unique page states
• Cost considerations: Comprehensive manual audits can cost $15,000-$50,000 for enterprise applications
• Time requirements: Thorough manual audits require 2-6 weeks, incompatible with rapid development cycles
• Expertise scarcity: Qualified manual auditors are in short supply, creating bottlenecks for organizations seeking comprehensive evaluation

The Integration Challenge: Why Hybrid Approaches Struggle

Many organizations recognize the need for both automated testing and manual audits but struggle to integrate these approaches effectively. Common integration failures include:

Sequential rather than complementary approaches: Organizations often treat automated testing and manual audits as separate phases rather than complementary methodologies. This creates gaps where automated testing misses issues that manual audits would catch, but manual audits don't occur until after automated testing is "complete."

Conflicting priorities and timelines: Development teams optimizing for automated testing metrics may inadvertently create barriers that manual auditors later identify. Without integrated feedback loops, these conflicts persist across development cycles.

Resource allocation mismatches: Organizations may invest heavily in automated testing tools while under-investing in manual audit capacity, creating imbalanced evaluation approaches that miss critical usability barriers.

The ACT Rules Revolution: Standardizing What Can Be Standardized

Understanding ACT Rules Format 1.1

The W3C's ACT Rules Format 1.1 represents a significant advance in accessibility testing standardization. Published in 2024, this standard addresses a longstanding problem in accessibility testing: different tools often produced conflicting results for the same content, creating confusion for development teams and compliance officers.

ACT Rules provide "a common language for automated tools and manual audits," establishing standardized test procedures, expected outcomes, and failure criteria. The format includes:

• Precise rule definitions that eliminate ambiguity about what constitutes a violation
• Standardized test procedures that ensure consistent evaluation across different tools
• Clear applicability criteria that specify when rules should be applied
• Comprehensive test cases that validate tool implementation accuracy

Early adoption of ACT Rules has already shown promising results. Organizations using ACT Rules-compliant tools report more consistent testing results across different platforms and reduced time spent reconciling conflicting automated testing reports.

The Promise and Limitations of Standardization

ACT Rules Format 1.1 solves critical problems in automated testing consistency, but standardization cannot address the fundamental limitations of automated evaluation. The rules format excels at standardizing technical checks—ensuring that all tools consistently identify missing alt text or insufficient color contrast. However, it cannot standardize the human judgment required to evaluate whether accessibility features create usable experiences.

Consider the evaluation of form error messages. ACT Rules can standardize the detection of:

• Whether error messages are programmatically associated with form fields
• Whether error messages are announced by screen readers
• Whether error messages meet color contrast requirements

However, ACT Rules cannot evaluate:

• Whether error messages provide helpful guidance for completing the form successfully
• Whether the timing of error message delivery aligns with users' mental models
• Whether the language used in error messages is appropriate for users with cognitive disabilities

This limitation becomes particularly significant in e-commerce contexts, where recent litigation has focused on shopping cart and checkout processes. Federal courts consistently find liability in cases where technical accessibility compliance exists but user workflows remain inaccessible. As one recent settlement noted, "compliance with WCAG technical requirements does not ensure that disabled customers can complete purchases independently."

Strategic Implementation of ACT Rules

Organizations implementing ACT Rules most effectively treat standardization as a foundation for more sophisticated testing approaches rather than a complete solution. Leading practices include:

Baseline establishment: Using ACT Rules-compliant tools to establish consistent baseline measurements across all digital properties, ensuring that technical violations are caught systematically.

Integration points: Incorporating ACT Rules-based testing into continuous integration pipelines while preserving dedicated time for manual evaluation of user workflows.

Metrics alignment: Using standardized ACT Rules results to track progress over time and compare accessibility maturity across different product teams or business units.

Vendor evaluation: Requiring ACT Rules compliance from accessibility testing vendors to ensure consistent evaluation approaches across different tools and services.

Case Study Analysis: When Automated Testing Fails Real Users

E-Commerce Platform: The Shopping Cart Accessibility Gap

A recent DOJ settlement with a major e-commerce platform illustrates the critical gap between automated testing success and user experience failure. The organization had invested significantly in automated accessibility testing, achieving 95% compliance scores across their platform using industry-standard tools.

Automated testing successfully identified and resolved:

• Image alt text compliance across 50,000+ product images
• Color contrast issues in the site's design system
• Keyboard navigation functionality throughout the shopping experience
• Form label associations in checkout processes

Despite these automated testing successes, manual evaluation revealed systematic barriers that prevented disabled customers from completing purchases:

Dynamic content updates: The shopping cart used AJAX to update quantities and totals without properly announcing changes to screen reader users. While automated tools verified that ARIA live regions existed, they couldn't evaluate whether the announcements provided meaningful information about cart changes.

Multi-step checkout flow: The checkout process technically met WCAG requirements for form labeling and error handling, but the workflow created cognitive load that particularly impacted users with attention disabilities. Automated tools verified technical compliance but couldn't assess the cumulative usability impact.

Third-party payment integration: The payment processor's embedded iframe met automated testing criteria but created focus management problems that trapped keyboard users. This barrier only emerged during realistic usage scenarios that automated tools couldn't simulate.

The settlement required comprehensive manual user testing with disabled customers, revealing that automated testing had created a false sense of accessibility compliance while significant barriers persisted.

Healthcare Portal: Patient Safety Meets Accessibility

A healthcare system's patient portal provides another compelling example of automated testing limitations. The organization achieved strong automated testing scores but faced DOJ enforcement action after disabled patients reported barriers accessing essential health information.

Automated testing successfully addressed:

• PDF document accessibility across thousands of patient education materials
• Form accessibility for appointment scheduling and prescription refills
• Navigation consistency across different portal sections
• Mobile responsiveness for assistive technology compatibility

However, manual evaluation identified critical barriers that automated testing missed:

Medication management complexity: The prescription refill interface technically met WCAG requirements but created workflows that were particularly challenging for users with cognitive disabilities managing multiple medications. Automated tools couldn't evaluate the cognitive load of complex medication management tasks.

Appointment scheduling context: The calendar interface passed automated accessibility tests but failed to provide adequate context for screen reader users about appointment types, provider information, and scheduling constraints. This information was visually available but not programmatically accessible in meaningful ways.

Emergency information access: Critical health alerts met technical accessibility requirements but weren't prioritized appropriately for assistive technology users, potentially delaying access to time-sensitive health information.

The healthcare system's response illustrates effective integration of automated and manual testing approaches. They maintained automated testing for technical compliance while implementing quarterly manual evaluations focusing on patient workflow usability.

Municipal Government: Civic Participation Barriers

Recent analysis showing that 78% of municipal websites fail basic WCAG standards reveals another dimension of testing methodology failures. Many cities have implemented automated testing tools but continue to exclude disabled residents from digital civic participation.

A mid-sized city's experience illustrates common patterns. Their automated testing implementation successfully:

• Standardized accessibility evaluation across 200+ city web pages
• Integrated accessibility checks into content management workflows
• Reduced technical violations by 60% over 18 months
• Provided measurable compliance metrics for city leadership

Despite these automated testing improvements, manual evaluation revealed persistent barriers to civic participation:

Public meeting access: Online meeting agendas and minutes met technical accessibility requirements but weren't structured in ways that helped screen reader users efficiently locate relevant information. The linear presentation of lengthy documents created significant barriers to civic engagement.

Service application processes: Permit applications and service requests passed automated accessibility tests but created user experience barriers for residents with disabilities. Multi-step processes that were technically accessible nonetheless excluded residents who needed different interaction approaches.

Emergency communication: Alert systems met automated testing criteria but failed to deliver emergency information effectively to residents using assistive technologies, creating potential safety risks during community emergencies.

The Cognitive Accessibility Challenge: Where Automation Falls Short

Understanding Cognitive Accessibility Barriers

The W3C's new Cognitive Accessibility Research Modules highlight a critical limitation in current testing methodologies: cognitive accessibility barriers often cannot be detected through automated testing. These barriers emerge from the interaction between multiple elements, requiring human judgment to evaluate their cumulative impact on users with cognitive and learning disabilities.

Cognitive accessibility challenges include:

• Information processing barriers: Content that meets technical readability standards but presents information in ways that overwhelm users with attention disabilities
• Navigation complexity: Site structures that are technically accessible but create mental mapping difficulties for users with intellectual disabilities
• Decision-making support: Interfaces that provide required information but don't scaffold decision-making processes for users who need additional cognitive support
• Error recovery: Systems that meet technical error handling requirements but don't provide the contextual guidance needed for successful task completion

Automated Testing Limitations for Cognitive Accessibility

Automated tools excel at detecting technical violations but struggle with cognitive accessibility evaluation because:

Context dependency: Cognitive accessibility barriers often depend on the specific context of use, user goals, and task complexity—factors that automated tools cannot fully simulate.

Cumulative effects: Individual elements may be technically compliant while their combination creates cognitive overload. Automated tools evaluate elements individually rather than assessing cumulative cognitive impact.

Subjective usability: Cognitive accessibility often depends on subjective factors like clarity, helpfulness, and appropriateness that require human judgment to evaluate.

User diversity: Cognitive disabilities encompass a wide range of conditions with different accommodation needs. Automated tools cannot account for this diversity in evaluation approaches.

Manual Evaluation Strategies for Cognitive Accessibility

Effective cognitive accessibility evaluation requires manual approaches that automated testing cannot replicate:

User workflow analysis: Manual evaluators can assess whether task flows align with users' mental models and provide appropriate scaffolding for complex processes.

Content comprehensibility: Human evaluators can assess whether content is genuinely helpful and appropriately structured for users with different cognitive processing needs.

Error prevention and recovery: Manual testing can evaluate whether error handling approaches actually help users recover successfully rather than just meeting technical requirements.

Decision support evaluation: Manual evaluators can assess whether interfaces provide appropriate support for users who need additional time or guidance for decision-making processes.

Organizational Implications: Building Effective Testing Programs

The Resource Allocation Challenge

Organizations face difficult decisions about allocating limited accessibility resources between automated testing tools and manual audit capacity. Recent industry analysis reveals common misallocation patterns:

Over-investment in automation: Organizations may invest heavily in automated testing tools while under-investing in the manual evaluation capacity needed to catch usability barriers that automated tools miss.

Under-investment in integration: Many organizations purchase both automated tools and manual audit services but fail to invest in the integration processes needed to leverage both approaches effectively.

Skill development gaps: Organizations may implement sophisticated automated testing without developing internal capacity to interpret results and integrate findings with manual evaluation insights.

Effective Hybrid Testing Strategies

Organizations achieving genuine accessibility progress employ hybrid testing strategies that leverage the strengths of both automated and manual approaches:

Automated testing for technical compliance: Using automated tools to catch technical violations systematically across all digital properties, ensuring baseline compliance with WCAG requirements.

Manual evaluation for user experience: Focusing manual audit resources on critical user workflows, complex interactions, and accessibility barriers that require human judgment to evaluate.

Integrated feedback loops: Creating processes that allow manual audit findings to inform automated testing configuration and automated testing results to guide manual evaluation priorities.

Continuous monitoring approaches: Implementing automated testing for ongoing monitoring while scheduling regular manual evaluations to assess user experience quality and identify emerging barriers.

Building Internal Testing Capacity

Sustainable accessibility testing requires building internal organizational capacity rather than relying solely on external tools and services:

Cross-functional testing skills: Training UX designers, developers, and QA professionals to conduct basic manual accessibility evaluation, reducing dependence on external specialists for routine testing tasks.

Assistive technology familiarity: Ensuring that internal teams have hands-on experience with screen readers, voice control software, and other assistive technologies used by disabled customers.

User research integration: Incorporating disabled users into regular user research processes rather than treating accessibility as a separate evaluation domain.

Workflow integration: Embedding both automated and manual accessibility testing into standard development workflows rather than treating accessibility as an additional process layer.

Legal and Compliance Considerations

DOJ Enforcement Patterns and Testing Implications

Recent DOJ settlements reveal enforcement patterns that highlight the limitations of automated-testing-only approaches to compliance:

User experience focus: DOJ settlements increasingly focus on whether disabled users can actually complete essential tasks, not just whether technical requirements are met. This emphasis requires evaluation approaches that automated testing alone cannot provide.

Workflow-based violations: Many recent settlements identify barriers in multi-step processes like shopping cart checkout, loan applications, or patient portal navigation—barriers that emerge from the interaction between multiple technically compliant elements.

Ongoing monitoring requirements: DOJ settlements often require ongoing accessibility monitoring and user testing, suggesting that one-time automated testing is insufficient for demonstrating compliance commitment.

Third-party integration responsibility: Organizations are being held responsible for accessibility barriers in third-party integrations, even when those integrations pass automated testing. This requires manual evaluation of integrated user experiences.

Compliance Documentation Strategies

Effective compliance documentation requires evidence from both automated testing and manual evaluation:

Automated testing for systematic coverage: Automated testing provides documentation of systematic evaluation across all digital properties, demonstrating comprehensive technical compliance efforts.

Manual evaluation for user focus: Manual audit documentation demonstrates commitment to user experience quality and identifies proactive efforts to address barriers beyond technical requirements.

User feedback integration: Documentation of user testing with disabled customers provides evidence of genuine commitment to accessibility outcomes rather than just compliance processes.

Remediation tracking: Combined automated and manual testing enables comprehensive tracking of barrier identification, remediation efforts, and outcome verification.

Future Directions: Evolving Testing Methodologies

Emerging Technologies in Accessibility Testing

Several emerging technologies show promise for bridging the gap between automated testing efficiency and manual evaluation quality:

AI-powered usability evaluation: Machine learning approaches that can simulate user workflows and identify potential usability barriers, though these remain in early development stages.

Automated user journey testing: Tools that can simulate realistic user workflows across multiple pages, catching barriers that emerge from interaction between technically compliant elements.

Assistive technology simulation: More sophisticated automated testing that can better simulate screen reader, voice control, and other assistive technology interactions.

Cognitive load assessment: Automated approaches for evaluating cognitive complexity and information processing demands, though these require significant additional development.

Integration with Broader Quality Assurance

The future of accessibility testing lies in better integration with broader quality assurance and user experience evaluation:

User experience testing integration: Incorporating accessibility evaluation into standard user experience research rather than treating it as a separate domain.

Performance testing alignment: Recognizing that accessibility and performance often intersect, particularly for users with disabilities who may be more impacted by slow loading times or complex interactions.

Security testing coordination: Ensuring that security measures don't inadvertently create accessibility barriers, requiring coordination between security and accessibility testing approaches.

Content strategy integration: Aligning accessibility testing with content strategy and information architecture evaluation to address cognitive accessibility systematically.

Standards Evolution and Testing Implications

Evolving accessibility standards will require continued adaptation of testing methodologies:

WCAG 3.0 development: The next version of WCAG may include more subjective evaluation criteria that require human judgment, potentially shifting the balance between automated and manual testing.

Cognitive accessibility standards: As cognitive accessibility requirements become more specific, testing methodologies will need to evolve to address barriers that currently require entirely manual evaluation.

Platform-specific requirements: As accessibility requirements expand beyond web content to mobile apps, voice interfaces, and emerging technologies, testing approaches will need to adapt to new contexts.

International harmonization: Efforts to harmonize accessibility requirements across different jurisdictions may create opportunities for more standardized testing approaches while preserving flexibility for context-specific evaluation.

Practical Implementation Framework

Phase 1: Foundation Building

Automated testing infrastructure: Implement ACT Rules-compliant automated testing tools integrated into development workflows, focusing on catching technical violations systematically.

Baseline manual evaluation: Conduct comprehensive manual audits of critical user workflows to identify barriers that automated testing misses and establish priorities for ongoing manual evaluation.

Team skill development: Train internal teams in basic manual accessibility testing techniques and assistive technology use to reduce dependence on external specialists.

Integration process design: Develop processes for integrating automated testing results with manual evaluation findings, ensuring that both approaches inform remediation priorities.

Phase 2: Systematic Integration

Workflow-based testing protocols: Develop testing protocols that combine automated technical checks with manual evaluation of complete user workflows, particularly for critical business processes.

User research integration: Incorporate disabled users into regular user research processes, using their feedback to validate both automated testing results and manual evaluation findings.

Continuous monitoring systems: Implement systems that use automated testing for ongoing monitoring while scheduling regular manual evaluations based on content changes, user feedback, and business priorities.

Documentation and tracking: Establish documentation systems that track both automated testing results and manual evaluation findings, providing comprehensive evidence of accessibility efforts for compliance purposes.

Phase 3: Optimization and Innovation

Advanced integration techniques: Experiment with emerging technologies that bridge automated and manual testing approaches, while maintaining proven methodologies for critical evaluation tasks.

Community engagement: Develop ongoing relationships with disabled user communities to inform testing priorities and validate accessibility improvements.

Industry collaboration: Participate in industry efforts to improve testing methodologies and share lessons learned about effective integration of automated and manual approaches.

Continuous improvement: Regularly evaluate testing methodology effectiveness based on user feedback, compliance outcomes, and business results, adapting approaches as standards and technologies evolve.

Conclusion: Beyond the False Promise to Genuine Progress

The persistent 96.3% failure rate of websites on basic accessibility checks, despite widespread adoption of automated testing tools, reveals the false promise at the heart of current accessibility testing approaches. Automated testing, while valuable for detecting technical violations, cannot evaluate whether accessibility features create genuinely usable experiences for disabled users. Manual audits, while irreplaceable for assessing user experience quality, cannot provide the systematic coverage and continuous monitoring that modern digital properties require.

The path forward requires abandoning the false choice between automated testing efficiency and manual audit quality. Organizations achieving genuine accessibility progress employ hybrid methodologies that leverage automation for systematic technical compliance while preserving human judgment for complex usability evaluation. This integration is not merely additive—it requires fundamental changes in how organizations approach accessibility testing, resource allocation, and compliance documentation.

The W3C's ACT Rules Format 1.1 provides a foundation for more consistent automated testing, but standardization cannot address the fundamental limitations of automated evaluation. Cognitive accessibility barriers, workflow usability problems, and context-dependent issues will continue to require human judgment and user testing with disabled people. The challenge lies not in choosing between automated and manual approaches, but in integrating them effectively to serve both compliance requirements and user needs.

Recent DOJ enforcement patterns underscore the urgency of resolving this testing methodology crisis. Federal settlements increasingly focus on whether disabled users can actually complete essential tasks, not just whether technical requirements are met. Organizations that continue to rely primarily on automated testing for accessibility compliance face both legal exposure and the ethical failure of excluding disabled users from digital participation.

The organizations that will succeed in creating genuinely accessible digital experiences are those that treat testing methodology integration as a strategic capability rather than a compliance burden. They invest in building internal capacity for both automated and manual evaluation, engage disabled users in ongoing testing processes, and view accessibility testing as part of broader user experience and quality assurance efforts.

As digital services become essential infrastructure for healthcare, education, employment, and civic participation, the stakes of effective accessibility testing extend far beyond compliance. The testing methodologies we develop today will determine whether disabled people can participate fully in an increasingly digital society. The false promise of automated testing efficiency must give way to the genuine progress that comes from combining technological capabilities with human judgment in service of human rights.

The future of accessibility testing lies not in perfect automation, but in thoughtful integration of automated efficiency with manual insight, systematic technical evaluation with user-centered design, and compliance requirements with genuine inclusion. Organizations that master this integration will not only reduce legal exposure but also expand their customer base, improve user experiences for all users, and contribute to a more accessible digital world.

For accessibility professionals, legal counsel, compliance officers, and development teams, the imperative is clear: move beyond the false promise of automated testing alone toward hybrid methodologies that serve both compliance requirements and disabled users' needs. The technology exists, the standards are evolving, and the legal environment demands action. What remains is the organizational commitment to implement testing approaches that match the complexity and importance of accessibility in digital society.

The 96.3% failure rate is not inevitable—it is the result of testing methodologies that prioritize efficiency over effectiveness, technical compliance over user experience, and automated convenience over human needs. Organizations ready to address this testing methodology crisis will find competitive advantages, reduced legal exposure, and the satisfaction of creating digital experiences that truly serve all users. The question is not whether to integrate automated and manual testing approaches, but how quickly and effectively organizations can make this integration a core capability.

In an era where digital exclusion increasingly means social and economic exclusion, accessibility testing methodology is not a technical detail—it is a fundamental question of justice, inclusion, and human rights in digital society. The false promise of automated testing efficiency has delayed progress long enough. The time for genuine, integrated approaches to accessibility testing is now.