CARVIEW

MOTORHOMES

Select Language

HTTP/2 301 date: Tue, 07 Oct 2025 23:24:16 GMT content-length: 0 location: https://www.w3.org/WAI/standards-guidelines/shared-experiences/ cf-ray: 98b126ac0b3f8087-BLR x-request-id: 98b126ac0b3f8087 strict-transport-security: max-age=15552000; includeSubdomains; preload content-security-policy: frame-ancestors 'self' https://cms.w3.org/ https://cms-dev.w3.org/; upgrade-insecure-requests cf-cache-status: EXPIRED set-cookie: __cf_bm=3GpjbjFzo725.JDwqeScVtQqTv3KtgUiZ2Q41qMpdIc-1759879456-1.0.1.1-Wj18Nr2QDYgFBa13fD7lIj_OL3gYPClGBhYutIFRUT1N2.m4r5PdSnbyUMY4.H.QLenstZ331xqg4cuIyG3ciqwcKMIV1mWDgsGcFYPf6Cc; path=/; expires=Tue, 07-Oct-25 23:54:16 GMT; domain=.w3.org; HttpOnly; Secure; SameSite=None vary: Accept-Encoding server: cloudflare alt-svc: h3=":443"; ma=86400 HTTP/2 200 date: Tue, 07 Oct 2025 23:24:17 GMT content-type: text/html; charset=utf-8 content-encoding: gzip last-modified: Tue, 07 Oct 2025 17:39:09 GMT access-control-allow-origin: * expires: Tue, 07 Oct 2025 18:23:53 GMT cache-control: max-age=600 x-proxy-cache: MISS x-github-request-id: 417C:A0A56:1A2DE9:1C418F:68E55860 via: 1.1 varnish x-served-by: cache-iad-kjyo7100048-IAD x-cache: MISS x-cache-hits: 0 x-timer: S1759860833.093718,VS0,VE20 vary: Accept-Encoding x-fastly-request-id: 10d3b1b6c7183cddba96324e523bb7f99e4b7f8b x-backend: www-mirrors x-request-id: 98af5ffe5be6f472 strict-transport-security: max-age=15552000; includeSubdomains; preload content-security-policy: frame-ancestors 'self' https://cms.w3.org/ https://cms-dev.w3.org/; upgrade-insecure-requests cf-cache-status: HIT server: cloudflare cf-ray: 98b126adfb9f8087-BLR alt-svc: h3=":443"; ma=86400 [Archived] Shared Web Experiences: Barriers Common to Mobile Device Users and People with Disabilities | Web Accessibility Initiative (WAI) | W3C

Shared Web Experiences:
Barriers Common to Mobile Device Users and People with Disabilities

If you want current information on mobile accessibility — that is, people with disabilities using content on mobile devices, see https://www.w3.org/WAI/mobile/

This page is archived. We do not plan to update it. It was developed in 2008. Much of the information is still relevant today. It is useful for understanding that:

Many of the issues around designing for mobile devices are addressed by designing for people with disabilities.
When you address accessibility, you improve the mobile experience. This can help in presenting your business case for accessibility.

Background

People with disabilities using computers have similar interaction limitations as people without disabilities who are using mobile devices. Both experience similar barriers when interacting with websites and web applications. There is also significant overlap between the design solutions for both. For more background, see:

An introduction to the overlap between W3C guidelines for accessibility and best practices for mobile devices: Web Content Accessibility and Mobile Web: Making a Website Accessible Both for People with Disabilities and for Mobile Devices
Introduction to Web Accessibility
How People with Disabilities Use the Web

A comprehensive comparison between MWBP and WCAG is provided in Relationship between Mobile Web Best Practices (MWBP) and Web Content Accessibility Guidelines (WCAG).

Introduction

The barriers on this page are grouped under four principles: perceivable, operable, understandable and robust. These principles lay the foundation necessary for anyone to access and use web content, as described in Understanding the Four Principles of Accessibility section of Introduction to Understanding WCAG 2.0. (Mobile devices vary widely and not all the barriers are present on all models.)

This page includes links to some relevant solutions in:

Web Content Accessibility Guidelines (WCAG) 2.0
Web Content Accessibility Guidelines (WCAG) 1.0 Note: W3C WAI recommends using WCAG 2.0, instead of WCAG 1.0.
Mobile Web Best Practices 1.0
Mobile Web Application Best Practices

The information below is also available in tabular format.

Perceivable
Operable
Understandable
Robust
- Invalid or unsupported markup
- Scripting required to generate content

Perceivable

Information and user interface components must be presentable to users in ways they can perceive.

Experiences discussed below are also available in tabular format.

Non-text objects (images, sound, video) with no text alternative

User cannot perceive important information or loses information due to lack of alternative.

Disabilities Context: User who is blind cannot perceive content that include non-text objects. Furthermore, information not available to user whose browser, assistive technology, other user agent doesn’t support object.

WCAG 2.0 Success Criteria: 1.1.1 Non-text content.

WCAG 1.0 checkpoint: 1.1.

Mobile Context: User can be billed for download volume so images might be turned off to save costs. Some mobile user agents have limited support for non-text objects so user loses information. Some user agents also shrunk images in size to fit the device’s screen which can make images meaningless.

MWBP 1.0 Best Practice: NON_TEXT_ALTERNATIVES and OBJECTS_OR_SCRIPT.

Operable

User interface components and navigation must be operable.

Experiences discussed below are also available in tabular format.

Understandable

Information and the operation of user interface must be understandable.

Experiences discussed below are also available in tabular format.

Robust

Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.

Experiences discussed below are also available in tabular format.

Original Source | Taken Source

Background

Introduction

Contents

Perceivable

Operable

Understandable

Robust