![]() ![]() While WCAG 2.0 remains a W3C Recommendation, the W3C advises the use of WCAG 2.1 to maximize future applicability of accessibility efforts. The publication of WCAG 2.1 does not deprecate or supersede WCAG 2.0. ![]() The WG intends that for policies requiring conformance to WCAG 2.0, WCAG 2.1 can provide an alternate means of conformance. Content that conforms to WCAG 2.1 also conforms to WCAG 2.0. WCAG 2.1 extends Web Content Accessibility Guidelines 2.0, which was published as a W3C Recommendation December 2008. See Web Content Accessibility Guidelines (WCAG) Overview for an introduction and links to WCAG technical and educational material. Guidance about satisfying the success criteria in specific technologies, as well as general information about interpreting the success criteria, is provided in separate documents. WCAG 2.1 success criteria are written as testable statements that are not technology-specific. Following these guidelines will also often make Web content more usable to users in general. These guidelines address accessibility of web content on desktops, laptops, tablets, and mobile devices. Following these guidelines will make content more accessible to a wider range of people with disabilities, including accommodations for blindness and low vision, deafness and hearing loss, limited movement, speech disabilities, photosensitivity, and combinations of these, and some accommodation for learning disabilities and cognitive limitations but will not address every user need for people with these disabilities. Web Content Accessibility Guidelines (WCAG) 2.1 covers a wide range of recommendations for making Web content more accessible. This document is also available in non-normative formats, available from Alternate Versions of Web Content Accessibility Guidelines 2.1. Please check the errata for any errors or issues The content disappears when zoomed at 400% as the reflow is not enabled.įor example: A global search field disappears after reflow, without an icon or menu option to reveal a search function or reach an equivalent search page.Web Content Accessibility Guidelines (WCAG) 2.1 W3C Recommendation 05 June 2018 This version: Latest published version: Latest editor's draft: Implementation report: Previous version: Previous Recommendation: Editors: Andrew Kirkpatrick (Adobe) Joshue O Connor (Invited Expert, InterAccess) Alastair Campbell (Nomensa) Michael Cooper ( W3C) WCAG 2.0 Editors (until December 2008): Ben Caldwell (Trace R&D Center, University of Wisconsin-Madison) Loretta Guarino Reid (Google, Inc.) Gregg Vanderheiden (Trace R&D Center, University of Wisconsin-Madison) Wendy Chisholm ( W3C) John Slatin (Accessibility Institute, University of Texas at Austin) Jason White (University of Melbourne) Therefore, a scrollbar is required when there are multiple buttons While editing content the interface needs to show both the toolbar and the content in the viewport.When multi-dimensional scrolling is considered essential for meaning or functionality.This success criterion has two exceptions ![]() Ensure that long URLs and strings of text support reflow.Similarly, a vertical scroll at a height of 256 CSS pixels for horizontal content. Ensure that horizontal scroll isn’t introduced at a width equal to 320 CSS pixels for vertical content.256 CSS pixels is the same as a default viewport of 1024 pixels enlarged 400%.320 CSS pixels is the same as a default viewport of 1280 pixels enlarged 400%.Therefore, it is essential that there is no loss of information or functionality when users augment up to 400% of the original or default size. Users with low vision often need to enlarge text for ease of reading. It is acceptable to provide two-dimensional scrolling for such parts of the content. For web content which is designed to scroll horizontally (e.g., with vertical text), 256 CSS pixels is equivalent to a starting viewport height of 1024 CSS pixels at 400% zoom.Įxamples of content which requires two-dimensional layout are images required for understanding (such as maps and diagrams), video, games, presentations, data tables (not individual cells), and interfaces where it is necessary to keep toolbars in view while manipulating content. Horizontal scrolling content at a height equivalent to 256 CSS pixels.Įxcept for parts of the content which require a two-dimensional layout for usage or meaning.ģ20 CSS pixels is equivalent to a starting viewport width of 1280 CSS pixels wide at 400% zoom. Vertical scrolling content at a width equivalent to 320 CSS pixels Success Criterion 1.4.10 Reflow (Level AA): Content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions for: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |