CARVIEW

MOTORHOMES

Select Language

HTTP/2 200 date: Wed, 08 Oct 2025 23:30:31 GMT content-type: text/html; charset=utf-8 content-encoding: gzip last-modified: Fri, 07 Oct 2016 19:51:11 GMT cache-control: max-age=31536000 expires: Thu, 08 Oct 2026 23:30:31 GMT vary: Accept-Encoding,Origin access-control-allow-origin: * x-backend: www-mirrors x-request-id: 98b96d31dd06a9b7 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: BYPASS set-cookie: __cf_bm=acNyKBbxiBRjfQO2dta4L5BJ1l4IE6MVHwF79pegD9Q-1759966231-1.0.1.1-Nyl2sQuQBCn7o6CSZh51BOb3JeH1csOKf5kXqqe.VDAceZvQXkfmM1KtL4gEp0KVQGUBpFvxRP_N211fRPS6SkTGC4_a5bNtXaA52nvAvwI; path=/; expires=Thu, 09-Oct-25 00:00:31 GMT; domain=.w3.org; HttpOnly; Secure; SameSite=None server: cloudflare cf-ray: 98b96d31dd06a9b7-BLR alt-svc: h3=":443"; ma=86400 F10: Failure of Success Criterion 2.1.2 and Conformance Requirement 5 due to combining multiple content formats in a way that traps users inside one format type | Techniques for WCAG 2.0

Skip to Content (Press Enter)

On this page:

F10: Failure of Success Criterion 2.1.2 and Conformance Requirement 5 due to combining multiple content formats in a way that traps users inside one format type

Important Information about Techniques

See Understanding Techniques for WCAG Success Criteria for important information about the usage of these informative techniques and how they relate to the normative WCAG 2.0 success criteria. The Applicability section explains the scope of the technique, and the presence of techniques for a specific technology does not imply that the technology can be used in all situations to create content that meets WCAG 2.0.

Applicability

Applies when content creates a situation where the user can enter the content using the keyboard, but cannot exit the content using the keyboard.

This failure relates to:

Description

When content includes multiple formats, one or more user agents or plug-ins are often needed in order to successfully present the content to users. For example, a page that includes XHTML, SVG, SMIL and XForms may require a browser to load as many as three different plug-ins in order for a user to successfully interact with the content. Some plug-ins create a common situation in which the keyboard focus can become "stuck" in a plug-in, leaving a keyboard-only user with no way to return to the other content.

Examples

A plug-in traps the user A user tabs into a plug-in and is unable to return to content outside the plug-in content with the keyboard. The user has to restart their browser in order to regain control and navigate to a new page and is unable to access any content that appears beyond the plug-in content.

Resources

No resources available for this technique.

Tests

Procedure

Using a keyboard, navigate through the content.
Check to see that the keyboard focus is not "trapped" and it is possible to move keyboard focus out of the plug-in content without closing the user agent or restarting the system.

Expected Results

If the keyboard focus becomes "trapped," then this failure condition applies and content fails the Success Criterion and conformance requirement 5.

This Web page is part of Techniques and Failures for Web Content Accessibility Guidelines 2.0 (see the latest version of this document). The entire document is also available as a single HTML file. See the The WCAG 2.0 Documents for an explanation of how this document fits in with other Web Content Accessibility Guidelines (WCAG) 2.0 documents. To send public comments, please follow the Instructions for Commenting on WCAG 2.0 Documents.

Original Source | Taken Source