A website evaluated only on desktop leaves mobile accessibility issues undetected, and vice versa. Websites need a mobile and desktop audit because each environment renders content differently, introduces different interaction patterns, and produces different WCAG conformance issues. An audit conducted in one environment alone cannot account for the accessibility gaps that exist in the other.
WCAG 2.1 AA and WCAG 2.2 AA both include criteria that apply specifically to touch interfaces, screen orientation, and pointer inputs. These criteria are only meaningfully evaluated on mobile. At the same time, desktop keyboard navigation and screen reader behavior surface issues that do not appear on a phone or tablet.
| Factor | Detail |
|---|---|
| Why both environments | Each environment produces distinct accessibility issues that only appear during evaluation in that context |
| WCAG criteria coverage | Several WCAG 2.1 AA and 2.2 AA criteria specifically target mobile interactions like touch, orientation, and pointer cancellation |
| Common desktop issues | Keyboard traps, missing focus indicators, screen reader labeling gaps |
| Common mobile issues | Touch target sizing, orientation lock, content reflow at narrow viewports |
| Conformance standard | WCAG 2.1 AA is the most widely referenced standard for audits; 2.2 AA adoption is growing |
| Audit approach | An accessibility audit across both environments is the only way to determine WCAG conformance |
What Makes Mobile and Desktop Accessibility Different?
Desktop users interact with a keyboard and mouse. Mobile users interact with touch gestures, and screen readers on mobile (VoiceOver on iOS, TalkBack on Android) behave differently than their desktop counterparts like NVDA or JAWS.
A navigation menu might be fully keyboard-accessible on desktop but completely inaccessible on mobile because the hamburger toggle does not respond to assistive technology. A form that works well with NVDA might announce field labels incorrectly through VoiceOver. These are not edge cases. They are common issues that Accessible.org auditors identify regularly.
Responsive design changes layout, hides elements, and introduces new interactive patterns at different viewport widths. A modal that traps focus correctly on a wide screen might lose that behavior entirely when the layout shifts for a phone.
Which WCAG Criteria Apply Only to Mobile?
WCAG 2.1 introduced several success criteria that specifically address mobile interactions. Orientation (1.3.4) requires that content not be locked to a single display orientation unless that orientation is essential. Pointer Cancellation (2.5.2) addresses how touch events fire. And Target Size criteria in both WCAG 2.1 AA and WCAG 2.2 AA set minimum dimensions for interactive elements.
These criteria cannot be meaningfully evaluated on a desktop browser. An auditor needs a real mobile device or, at minimum, a mobile emulator paired with assistive technology to assess conformance accurately.
Can Automated Scans Cover Both Environments?
Automated scans flag approximately 25% of accessibility issues, and most scanning tools only evaluate the desktop rendering of a page. Even when a scan is configured for a mobile viewport, it cannot assess touch interactions, gesture-based navigation, or mobile screen reader compatibility.
A scan might confirm that an image has alt text, but it cannot determine whether a swipe gesture on mobile correctly moves focus through a carousel. That distinction is why an accessibility audit across both environments is the only way to determine full WCAG conformance.
What Happens If You Only Audit One Environment?
Organizations that audit only desktop miss every mobile-specific issue. For many websites, mobile traffic accounts for the majority of visits. An ADA compliance claim built on a desktop-only evaluation carries real risk because it leaves an entire category of user interaction unevaluated.
Accessibility Tracker Platform data from Accessible.org clients confirms that mobile-specific issues make up a meaningful portion of total WCAG conformance gaps. Ignoring them does not make the issues disappear from the audit report. It means they were never identified in the first place.
How Does a Dual-Environment Audit Work?
The auditor evaluates the same set of pages and components in both desktop and mobile environments. On desktop, the evaluation covers keyboard navigation, screen reader output (typically NVDA or JAWS with Chrome or Firefox), and visual presentation at standard viewport widths.
On mobile, the auditor evaluates touch interactions, screen reader output through VoiceOver or TalkBack, content reflow, orientation behavior, and touch target sizing. The audit report documents issues by environment so the remediation team knows exactly where each issue occurs.
Accessible.org conducts every audit across both environments. The cost and pricing for a dual-environment evaluation is built into the standard approach to accessibility audits rather than treated as an add-on.
Does This Affect ADA Compliance?
ADA website compliance expectations are tied to the full user experience, not a single device. The DOJ’s ADA Title II web accessibility rule references WCAG 2.1 AA as the standard, and that standard includes mobile-specific criteria. Title III demand letters and lawsuits also reference the mobile experience when the website is accessed on a phone.
An organization that can demonstrate WCAG conformance across both desktop and mobile has stronger documentation for compliance. One that has only evaluated desktop has a gap in its compliance story.
Is a mobile audit more expensive than desktop?
At Accessible.org, both environments are included in the standard audit pricing. Some providers charge separately for mobile evaluation, which can increase the total cost. Confirm with any vendor whether mobile is included before commissioning an audit.
How often should both environments be re-evaluated?
After any significant redesign, platform migration, or content update that changes interactive components. Regular re-evaluation keeps the conformance documentation current and prevents issues from accumulating between audit cycles.
Do mobile apps need the same type of audit?
Mobile apps are evaluated against the same WCAG standard but require a dedicated app audit rather than a website audit. The evaluation methodology differs because native app components behave differently than web content rendered in a mobile browser.
A website that has only been evaluated in one environment has only been partially evaluated. Mobile and desktop audits together are what produce a complete picture of WCAG conformance.
Contact Accessible.org to schedule an accessibility audit that covers both mobile and desktop environments.
