![]() ![]() G94: Providing short text alternative for non-text content that serves the same purpose and presents the same information as the non-text content Sufficient Techniques for 1.1.1 - Non-text Content Situation A: If a short description can serve the same purpose and present the same information as the non-text content: Sensory: If non-text content is primarily intended to create a specific sensory experience, then text alternatives at least provide descriptive identification of the non-text content.ĬAPTCHA: If the purpose non-text content is to confirm that content is being accessed by a person rather than a computer, then text alternatives that identify and describe the purpose of the non-text content are provided, and alternative forms of CAPTCHA using output modes for different types of sensory perceptionĪre provided to accommodate different disabilities.ĭecoration, Formatting, Invisible: If non-text content is pure decoration, is used only for visual formatting, or is not presented to users, then it is implemented in a way that it can be ignored by assistive technology. Test: If non-text content is a test or exercise that must be presented in non-text format, then text alternatives at least provide descriptive identification of the non-text content. (Refer to Guideline 1.2 for additional requirements for media.) Time-Based Media: If non-text content is time-based media, then text alternatives at least provide descriptive identification of the non-text content. (Refer to Guideline 4.1 for additional requirements for controls and content that accepts user input.) (Level A) Understanding Success Criterion 1.1.1Ĭontrols, Input: If non-text content is a control or accepts user input, then it has a name that describes its purpose. 4.1 Compatible: Maximize compatibility with current and future user agents, including assistive technologiesġ.1.1 All non-text content that is presented to the user has a text alternative that serves the equivalent purpose, except for the situations listed below.Make Web pages appear and operate in predictable ways Make text content readable and understandable Provide ways to help users navigate, find content and determine where they are 2.3 Seizures: Do not design content in a way that is known to cause seizures.Provide users enough time to read and use content Make all functionality available from a keyboard To see and hear content including separating foreground from background ) without losing information or structure 1.3 Adaptable: Create content that can be presented in different ways (for example simpler layout.1.2 Time-based Media: Provide alternatives for synchronized time-based media.1.1 Text Alternatives: Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language.See also Sufficient and Advisory Techniques. Authors are encouraged to seek relevant advice about current best practice to ensure that Web content is accessible, as far as possible, to this community. Note that even content that conforms at the highest level (AAA) will not be accessible to individuals with all types, degrees, or combinations of disability, particularly in the cognitive language and learning areas. Authors are encouraged to apply all techniques that they are able to, including the advisory techniques, in order to best address the needs of the widest possible range of users. In addition to the 'sufficient techniques', there are also advisory techniques that go beyond WCAG 2.0's requirements. If techniques are used other than those listed by the Working Group, then some other method for establishing the technique's ability to meet the success criteria would be needed. Anyone can submit new techniques at any time. The "sufficient techniques" listed below are considered sufficient to meet the success criteria however, it is not necessary to use these particular techniques. Note that all techniques are informative - you don't have to follow them. See the Overview of WCAG 2.0 Documents for an introduction to WCAG 2.0 and supporting documents, including more information about this document. You can customize the list by selecting the technologies that apply to your Web project, and the levels and techniques that you want included in the list. The "Understanding" links go to descriptions, examples, and resources. It also lists techniques to meet the requirements, which link to more details. This document lists all of the requirements (called "success criteria") from the latest Web Content Accessibility Guidelines (WCAG) 2.0 Working Draft. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |