Investigating the Appropriateness and Relevance of Mobile Web Accessibility Guidelines
Raphael Clegg-Vinell, Christopher Bailey, Voula Gkatzidou · 2014 · Proceedings of the 11th Web for All Conference (W4A) · doi:10.1145/2596695.2596717
Summary
This paper from AbilityNet and Brunel University examines whether real accessibility issues found during mobile user testing can be effectively mapped to existing guidelines — specifically WCAG 2.0 and the W3C Mobile Web Best Practices (MWBP) 1.0. Five lab-based mobile testing studies were conducted between March and December 2013, evaluating mobile websites and native apps across various platforms. Testers included users with dyslexia, deafness, motor impairments, medium and severe vision impairments, and older adults (50+), with sessions lasting 60-90 minutes using task-based scenarios and think-aloud methodology. The high and medium priority issues from all sessions were categorised into three groups: issues that clearly correspond to WCAG/MWBP guidelines, issues that require expert interpretation to map to guidelines, and issues that cause significant barriers but do not fall under any guideline. The work was motivated by AbilityNet's consultancy practice, where mapping user-reported issues to specific guideline checkpoints helps clients understand and prioritise fixes.
Key findings
The study found that more often than not, real mobile accessibility issues either did not easily map to existing guidelines or required expert interpretation to do so. Several significant gaps were identified. First, unclear icon purpose was reported across three studies at both high and medium priority, yet no WCAG or MWBP checkpoint addresses this — the closest reference is a general usability heuristic. Second, pinch-to-zoom failures appeared in four studies across disability groups (dyslexic, visually impaired, and older users); WCAG 2.0 SC 1.4.4 Resize Text only addresses desktop-based text resizing and does not cover mobile zoom gestures or icon scaling. Third, elements undetected by VoiceOver were mapped to WCAG SC 2.1.1 (Keyboard), but that criterion contains no guidance on touch-based gesture operability. Fourth, neither WCAG nor MWBP provided minimum size requirements for touch targets or text, despite Android and iOS frameworks having their own recommendations. The study also found discord between severity ratings: all contrast issues were rated High Priority by consultants but only AA level in WCAG, potentially confusing developers about prioritisation. Confirmation messages disappearing before users could read them and inadequate button target sizes were additional issues with no guideline coverage.
Relevance
This paper provided early empirical evidence that WCAG 2.0 and MWBP 1.0 were insufficient for mobile accessibility — a gap that W3C has since partially addressed through its "Mobile Accessibility: How WCAG 2.0 and Other W3C/WAI Guidelines Apply to Mobile" guidance and through WCAG 2.1's new success criteria (e.g., 2.5.5 Target Size, 1.3.4 Orientation). The findings remain relevant because they illustrate a fundamental tension in standards-based accessibility: guidelines developed primarily for desktop contexts may not capture the full range of barriers users encounter on touch-based mobile devices. For practitioners conducting mobile accessibility audits, the three-category mapping approach (clear match, expert interpretation needed, no match) is a useful framework for structuring reports and identifying where guidelines have blind spots. The study reinforces that user testing uncovers issues that automated checking and guideline conformance alone cannot detect.
Tags: mobile accessibility · WCAG compliance · accessibility testing · usability testing · accessibility standards · touchscreen accessibility · guidelines
Standards referenced: WCAG 2.0 · MWBP 1.0 · BS 8878