The Legal Shield for B2B Security

1. The Global Legal Landscape

Security gatekeeping (like CAPTCHAs) represents the highest-risk surface area for digital accessibility lawsuits. If a user with a disability cannot pass a mandatory security check, they are fundamentally blocked from accessing your service. This is a direct violation of international law.

• United States (ADA & Section 508): Title III of the Americans with Disabilities Act has been definitively interpreted by courts to mandate web accessibility. Gatekeeping features that rely purely on vision or fine motor skills without an equivalent alternative are prime targets for predatory litigation.
• European Union (EAA): The European Accessibility Act (now in full effect) enforces strict penalties, including service blocks within the EU, for digital services that fail to provide accessible pathways.
• Global Standard (WCAG 2.1/2.2 AA): WCAG Success Criterion 1.1.1 (Non-text Content) specifically dictates that CAPTCHAs must provide alternative forms of verification for different sensory perceptions.

2. The Failure of Legacy Alternatives

For years, the industry standard fallback for visual puzzles (like selecting crosswalks) was the Audio CAPTCHA. However, audio CAPTCHAs have proven to be a failed architecture:

• Cognitive Friction: Deciphering distorted audio through background noise is immensely difficult for users with cognitive or hearing impairments.
• Mobile Hostility: Audio CAPTCHAs frequently break on mobile browsers, conflicting with native screen reader audio routing.
• Language Barriers: Audio challenges are rarely localized accurately, alienating non-native speakers.

3. The TapHuman Paradigm Shift

TapHuman mitigates this legal liability entirely by designing accessibility into every game from the ground up, rather than bolting on an audio fallback as an afterthought.

Instead of forcing a visually impaired user to solve a separate puzzle, our games include native keyboard navigation and screen reader support. Users with disabilities play the same game through equivalent, accessible input methods — Tab to select elements, Arrow keys to move, and Space or Enter to interact.

4. Mobile-First Screen Reader Support

A critical failing of legacy accessibility implementations is the assumption that visually impaired users are on desktop computers with physical keyboards (using Tab and Enter). In reality, mobile screen readers (iOS VoiceOver and Android TalkBack) dominate.

Our games use native HTML5 interactive elements (<button>, <canvas> with ARIA roles) that work natively with mobile screen readers. VoiceOver users on iPhone can navigate game elements with swipe gestures and activate them with double-tap, while TalkBack users on Android use equivalent touch exploration. No physical keyboard is required.

5. Proof-of-Work as the Security Layer

With accessible game controls, how does the system prevent bots from simply completing the game programmatically?

The security layer is not the game itself — it's the cryptographic Proof-of-Work running in the background. While a human plays the game (via any input method — mouse, touch, or keyboard), the SDK asynchronously solves a computationally expensive SHA-256 puzzle. This makes automated attacks economically unviable regardless of the input method used.

• Automated Bots: Even if a bot could navigate the game DOM, it must also solve the Proof-of-Work puzzle, which requires real computational resources. Combined with the polymorphic game rotation (different game on each load), the cost of scripting and maintaining bot attacks becomes prohibitive.
• Human Users: Legitimate users — including those using screen readers or keyboard navigation — complete the game naturally while the Proof-of-Work runs transparently in the background. The accessible controls add zero additional friction.