Most people browse the web on a phone. If your accessibility audit only covers desktop, you are confirming conformance for half of your actual audience. Mobile environments introduce different interaction patterns, different assistive technologies, and different WCAG success criteria that desktop evaluation does not cover. A scoped audit that excludes mobile leaves real issues unidentified and gives a misleading picture of where your site or app stands.
Including mobile in your accessibility audit means evaluating the same pages or screens in a mobile environment, with mobile screen readers, touch gestures, and viewport-specific behaviors factored in. The result is an audit report that reflects how people actually use your product.
| Factor | What It Means for Your Audit |
|---|---|
| Assistive technology | VoiceOver on iOS and TalkBack on Android behave differently than desktop screen readers |
| Interaction model | Touch gestures, swipe navigation, and on-screen keyboards replace mouse and physical keyboard input |
| Viewport behavior | Responsive layouts, reflow, orientation, and zoom criteria apply specifically to mobile |
| User base | A large share of traffic comes from mobile, so excluding it skips most real-world use |
| Audit output | Mobile-specific issues appear in the audit report alongside desktop findings |
What Changes When the Audit Covers Mobile
Mobile is not a smaller desktop. The assistive technology stack is different, the input method is different, and the success criteria that apply most often are not the same ones that surface on a desktop browser.
On desktop, an auditor evaluates with NVDA or JAWS, uses keyboard navigation, and works through a full-size viewport. On mobile, the auditor uses VoiceOver on iOS and TalkBack on Android, navigates by touch gesture, and evaluates how the layout responds to a narrow viewport, rotation, and pinch zoom.
These differences produce different issues. A button that has a visible focus indicator on desktop may be unreachable by swipe on TalkBack. A modal that traps focus correctly with a keyboard may not announce properly to VoiceOver. Reflow and target size issues only show up when the viewport and input method match real mobile use.
Which WCAG Criteria Are Mobile-Sensitive
Several WCAG 2.1 AA and 2.2 AA success criteria apply specifically or most clearly in mobile environments. An auditor working only on desktop cannot evaluate them with the same accuracy.
Reflow (1.4.10) addresses how content adapts to a 320 CSS pixel width without horizontal scrolling. Orientation (1.3.4) confirms content is not locked to portrait or landscape. Pointer Gestures (2.5.1) covers multipoint and path-based gestures that are inherent to touch. Target Size (2.5.8 in 2.2 AA) sets minimum dimensions for touch targets. Touch interaction patterns surface under multiple criteria when evaluated on a real device.
These are not edge cases. They cover the everyday interactions a mobile user relies on, and they need an auditor working in the mobile environment to evaluate accurately.
Why Does Mobile Get Skipped in Audit Scope?
Mobile sometimes gets cut from scope to lower the cost of the audit. Each page or screen evaluated in a separate environment adds to the count, so a desktop-only audit is less expensive than a desktop plus mobile audit.
That tradeoff has real consequences. If a company claims WCAG 2.1 AA conformance based on a desktop-only audit, the claim does not cover how mobile users actually experience the product. For a site or app with meaningful mobile traffic, that is a thin foundation for compliance documentation, an ACR, or a legal defense.
A more accurate path is to scope the audit to reflect how the product is used. If mobile is a primary channel, mobile belongs in the audit.
How Mobile Coverage Strengthens Your Audit Report
The audit report identifies issues with severity, location, and remediation guidance. When mobile is included, the report covers both environments and gives the development team a single source of truth for what to fix.
This matters for prioritization. Mobile-specific issues can be ranked alongside desktop issues using Risk Factor or User Impact prioritization formulas, which lets the team work through the highest-impact items first regardless of environment.
It also matters for documentation. An ACR or accessibility statement that references the audit can accurately reflect conformance across the environments users actually encounter, not a partial view.
Mobile Web and Mobile Apps Are Separate Audits
Mobile web (a responsive website viewed in a mobile browser) and a native mobile app are two different products from an audit perspective. A responsive site evaluated on a phone is part of a web audit. A native iOS or Android app requires a mobile app audit with platform-specific evaluation.
Both can be in scope, but they are counted and priced separately because the work is different. Mapping which products need coverage is part of scoping the project.
FAQ
Should I include mobile in my accessibility audit if most of my users are on desktop?
If mobile traffic is meaningful, yes. Even a smaller share of mobile users will encounter issues that desktop evaluation does not identify, and an ACR or conformance claim is stronger when it reflects both environments.
Does adding mobile double the cost of the audit?
It does not double the cost, but it does increase it. Mobile evaluation adds work per page or screen, so pricing scales with the count of items evaluated in each environment.
Can a scan tell me if my mobile experience is accessible?
No. Scans flag approximately 25% of issues and do not evaluate touch interaction, screen reader behavior, or how content reflows in real use. A manual expert audit is the only way to determine WCAG conformance for mobile.
What screen readers does Accessible.org use for mobile evaluation?
VoiceOver on iOS and TalkBack on Android. These are the two screen readers mobile users actually rely on, and evaluation happens in the real assistive technology environment.
Mobile is where most people meet your product. Including it in the audit gives you a conformance picture that matches how users actually interact with what you have built.
Contact Accessible.org to scope a mobile and desktop accessibility audit.
