![]() 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 For that, the following VM option should be set: 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) If nothing of the above helps, it's recommended to manually set the IDE-managed HiDPI mode to prevent the auto-switch. Disable display scaling on high DPI settings.If it helps, set the Editor font size appropriately (Settings > Editor > Color Scheme > Color Scheme Font) Change the IDE font size (Settings > Appearance & Behavior > Appearance > Override default fonts).Logout/login a Windows session (in case a monitor scale factor has been manually changed).In order to try to resolve those issues, the following actions may help (some or all): ![]()
0 Comments
Leave a Reply. |