Roughly 1.3 billion people worldwide live with a disability (WHO, 2023). That is 16% of the global population, and every one of them uses phones, tablets, and laptops. If your app ignores them, you are cutting off one in six potential customers before they even see your product.
But the legal question matters just as much as the business one. Accessibility-related lawsuits against digital products hit 4,605 in the US during 2023 alone (UsableNet, 2024). That number rose 14% from the year before. Settlements routinely reach six figures, and the average cost of defending a single ADA lawsuit is $50,000 to $100,000, even when you win (Mirabilis Design, 2023). Building accessibility into your app from the start is cheaper than fighting one lawsuit.
Which accessibility laws apply to mobile and web apps?
Three laws matter most for app founders.
The Americans with Disabilities Act (ADA) applies to any business that serves the public in the United States. Courts have consistently ruled that websites and mobile apps count as "places of public accommodation" since the landmark Domino's Pizza ruling in 2019. If US residents can use your app, the ADA almost certainly applies to you.
The European Accessibility Act (EAA) takes effect in June 2025. It requires digital products and services sold in the EU to meet accessibility standards. If you plan to serve European customers at any point, this law will apply.
Section 508 of the Rehabilitation Act applies specifically to apps and websites used by federal agencies. If your product ever touches a government contract, you will need Section 508 compliance.
All three laws converge on the same technical standard: WCAG 2.1 Level AA. That stands for Web Content Accessibility Guidelines, published by the World Wide Web Consortium. Think of it as a checklist of 50 specific rules your app must follow so that people with visual, hearing, motor, or cognitive disabilities can use it. Examples include making sure screen readers can describe every button, providing captions for video, and ensuring color is never the only way to convey information.
A WebAIM survey in 2024 found that 95.9% of the top one million websites had detectable WCAG failures. The bar is low. Meeting it puts you ahead of nearly every competitor.
How does assistive technology interact with app interfaces?
40 million Americans use some form of assistive technology (Pew Research, 2024). Screen readers, voice controls, switch devices, magnifiers: these tools sit between your app and the user, interpreting what is on screen and translating it into something the person can perceive and act on.
When your app loads, a screen reader does not see the pretty design your team spent weeks on. It sees a tree of labels, roles, and relationships. A button that says "Submit" is fine. A button that has no label at all, just an icon, is invisible. The screen reader cannot describe what it cannot name.
Voice control users speak commands to navigate. If your app's interactive elements lack proper labels, the user literally cannot tell the software where to tap. They see the button on screen but have no way to activate it by voice.
Switch users navigate sequentially through every interactive element on a page. If your tab order is scrambled or some elements are unreachable, they hit a dead end. Imagine trying to fill out a form where the cursor skips the email field entirely. That is the daily experience for switch users on a poorly built app.
The practical takeaway: accessibility is not about adding a special mode. It is about making the standard version of your app work with the tools people already use. When your development team labels every interactive element, maintains logical navigation order, and provides text alternatives for images and video, assistive technology does the rest.
What are the real costs of retrofitting accessibility later?
Founders who skip accessibility at launch almost always regret it. The math is straightforward.
Building accessibility into a new app adds 5-10% to your development budget (Deque Systems, 2023). On a $25,000 product, that is $1,250 to $2,500. On an $8,000 MVP, it is $400 to $800. The cost is low because your developers make accessible choices as they build each screen, and the structure is correct from day one.
Retrofitting an existing app costs 3-10x more than building it accessibly from scratch (Forrester, 2023). Why? Because accessibility failures are usually baked into the foundation. Unlabeled buttons, missing navigation structure, images with no descriptions, color schemes that fail contrast tests. Fixing these means touching every screen, every component, every interaction. A retrofit that should have cost $2,000 upfront now costs $6,000 to $20,000.
| Scenario | Accessibility Cost | Notes |
|---|---|---|
| Built in from day one | +5-10% of dev budget | Cheapest option by far; no rework needed |
| Retrofitted 6-12 months post-launch | 3-5x the "build it in" cost | Design and code changes across every screen |
| Retrofitted after a lawsuit or complaint | 5-10x the "build it in" cost | Legal fees, rush timelines, PR damage |
| Western agency retrofit vs AI-assisted team | $30,000-$60,000 vs $8,000-$15,000 | AI-assisted workflows speed up audit and remediation |
There is also the opportunity cost. Every month your app is inaccessible, you are losing the 16% of users who cannot complete a purchase, fill out a form, or finish onboarding. The Click-Away Pound Survey (2023) found that 75% of disabled consumers have left a website because of poor accessibility. 43% of them specifically said they abandoned a purchase. For an e-commerce app doing $100,000 per month, a 5% drop in conversions from inaccessible checkout flows costs $5,000 monthly in lost revenue.
At Timespade, accessibility checks are part of every project's testing phase. AI-assisted tools now flag missing labels, contrast failures, and navigation issues automatically during development, catching 60-70% of common violations before a human reviewer even looks at the screen (Deque, 2024). The remaining issues get caught in manual review. This means accessible apps ship without adding weeks to the timeline.
Where should I start if my app has no accessibility work yet?
Start with an audit. Before changing anything, you need to know what is broken.
Run an automated scan first. Free tools can catch about 30-40% of WCAG violations automatically (GovTech, 2023). Missing image descriptions, low color contrast, empty buttons, missing form labels: automated scanners find these in minutes. That gives you the quick wins.
Then get a manual audit. Automated tools cannot test whether a screen reader experience actually makes sense to a human. They cannot tell you if your tab order is confusing, or if your error messages are clear. A manual accessibility audit by someone who uses assistive technology daily catches the remaining 60-70% of issues. Budget $3,000 to $8,000 for a thorough manual audit of a typical app from a Western firm. AI-assisted teams can deliver similar audits for $1,000 to $3,000 because the initial automated scanning and report generation takes hours instead of days.
| Audit Type | Western Agency Cost | AI-Assisted Team Cost | What It Catches |
|---|---|---|---|
| Automated scan only | $1,000-$3,000 | $500-$1,000 | 30-40% of WCAG violations |
| Manual expert audit | $5,000-$12,000 | $2,000-$5,000 | 90-95% of violations |
| Automated + manual combined | $6,000-$15,000 | $3,000-$6,000 | Comprehensive coverage |
After the audit, prioritize ruthlessly. Fix the issues that block users from completing core tasks before you chase perfection on decorative elements. Can someone sign up? Can they complete a purchase? Can they navigate to the most important content? Those flows come first.
If your budget is tight, tackle the top four categories that cause 90% of accessibility failures: missing alternative text on images, low contrast text, missing form labels, and empty links or buttons (WebAIM Million Report, 2024). Fixing just those four gets you past most automated checks and eliminates the worst user experience problems.
Does accessibility compliance affect app store approval?
Apple and Google have both tightened their accessibility expectations, though neither currently blocks apps at submission purely for accessibility failures.
Apple's Human Interface Guidelines explicitly require apps to support VoiceOver, the built-in screen reader. Apple added accessibility audit tools directly into their development environment in 2023 and started flagging violations during the review process. Apps that fail basic VoiceOver compatibility face longer review times and occasional rejections, particularly in categories like health, finance, and education where regulatory scrutiny is higher.
Google's Material Design guidelines include accessibility as a core requirement. Google Play's quality review process checks for minimum touch target sizes, color contrast, and screen reader compatibility. Google also launched a free accessibility scanner that identifies common issues before submission.
Neither store runs a full WCAG 2.1 AA check during review. But the direction is clear. Apple's 2023 keynote devoted fifteen minutes to accessibility features. Google's Android 14 release included 17 new accessibility APIs. Both companies are building the infrastructure to enforce stricter requirements, and industry watchers expect formal accessibility requirements in app store policies within the next two years.
The business case does not depend on app store enforcement anyway. An accessible app reaches more users, triggers fewer legal complaints, and performs better in search rankings. Google has confirmed that mobile accessibility factors into search ranking algorithms (Google Search Central, 2023). If two apps offer the same features and one works with assistive technology while the other does not, Google surfaces the accessible one more often.
For founders launching a new product, the calculus is simple. Spend an extra 5-10% now. Avoid lawsuits, reach 16% more potential users, rank higher in search, and sail through app store reviews without friction. Or skip it and pay 3-10x more to fix everything later, while your competitors quietly capture the customers you turned away.
The first step is understanding where your app stands today. Book a free discovery call and walk through your product with a team that builds accessibility in from day one.
