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 I did a test meeting with my same host using the same meeting ID and password using the now-updated Zoom app and it worked.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) So, before your meetings, be sure to click Preferences | Check for Updates. Zoom's suggestion was that they don't want to be "intrusive" by notifying users that there is an update available. Called Zoom support after meeting (was 20 minutes late to meeting) and found out they pushed an invisible update yesterday! Then Zoom was telling me "password error!" Gave up and joined by browser (Chrome) with no issues. ![]() So, meeting host changed the meeting password. Had this problem today and tried everything. Solution for me: Zoom pushed an invisible update yesterday with zero notification.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |