Skip to main content

The Compliance Hub

Your central resource for understanding accessibility regulations and requirements.

The Mobile App Blindspot: Why Web Scanners Fail

Most compliance tools are built for websites. They cannot "see" inside your mobile apps (iOS & Android), leaving you with a false sense of security and hidden risks.

Meaningful mobile compliance means testing the way people actually use the app: with VoiceOver and TalkBack running, real fingers on real targets, and the actual requirements in front of you. The regulations in this hub tell you what applies; the standards behind them tell you what to test.

Apps Are Not Websites

Web scanners read HTML code like a document. Mobile apps are complex software. You cannot use a document scanner to test complex software; it simply misses the errors.

Mouse vs. Finger

A mouse pointer is tiny (1 pixel). A finger is large. Automated tools often pass buttons that are mathematically correct in code but impossible for a human finger to tap without errors.

Simulation vs. Reality

Web widgets try to "simulate" how a blind user navigates. But on mobile, blind users use specific tools (VoiceOver & TalkBack) that behave completely differently. If you don't test with the real tools, you don't know if it works.

Key Regulations

European Accessibility Act (EAA)

EU-wide regulation requiring accessibility statements for digital products by June 2025.

Americans with Disabilities Act (ADA)

US law prohibiting discrimination, with Title III applying to websites and digital services.

Section 508

US federal requirement for accessible electronic and information technology.

WCAG 2.1

International guidelines for web content accessibility (Level A, AA, AAA).

EN 301 549

European standard for accessibility requirements for ICT products and services.

UK Accessibility Regulations

Public sector bodies accessibility requirements and private sector guidelines.

Quick Reference