- From: White, Jason J <jjwhite@ets.org>
- Date: Thu, 28 Apr 2022 14:01:59 +0000
- To: Scott Hollier <scott.hollier@accessibility.org.au>, "public-rqtf@w3.org" <public-rqtf@w3.org>
- Message-ID: <BL0PR07MB80198A3C0E5AB632DE03A716ABFD9@BL0PR07MB8019.namprd07.prod.outlook.com>
Thank you, Scott, for working on the announcement text. Can you send it in the original Mediawiki format (with your revisions included, of course)? It arrived as part of your e-mail message in HTML. We need the Mediawiki format so it can be inserted into the wiki page. I think there are still revisions to be made. For example, the Abstract and Status are supposed to be taken from the draft (as in, the abstract of the original document). The GitHub location for comments has changed to https://github.com/w3c/remote-meetings/issues and the label is no longer needed, as the document now resides in a separate repository. Josh is no longer a W3C staff contact, so this should be updated. I’m probably missing additional details. I hope these comments are valuable as the text is revised for submission. From: Scott Hollier <scott.hollier@accessibility.org.au> Sent: Thursday, 28 April 2022 1:18 To: public-rqtf@w3.org Subject: [EXTERNAL] Remote Meetings announcement draft CAUTION: This email originated from outside of our organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. To the RQTF I’ve had a go at updating the info that Roy sent through for the second public working draft, see below. Scott. ———announcement of remote meetings——— Any notes for us working on the announcements, such as important points to get across: The accessibility requirements of standard remote meeting delivery rely on three distinct elements: * The accessibility of the remote meeting platform; * The accessibility of content that is shared during the meeting; and * The accessibility awareness of host participants when the remote meeting is taking place. The accessibility challenges faced by people with disabilities participating in remote meetings depends on how these three elements interact. While W3C has applicable guidance across several standards and Notes relating to real-time communication and XR, it is this level of complexity that this document endeavours to address Status of announcements below: Ready for review Doc Abstract & Status The impact of COVID-19 has seen a substantial increase in usage of remote meeting platforms. Before 2020, software-based remote meeting applications were available, but not necessarily viewed as critical. The shift to remote meetings from a complementary tool to a replacement for face-to-face contact, has driven significant innovation in this space, including improvements in the provision of accessibility for people with disabilities. Yet despite the rapid growth of remote meeting platforms and innovation, there has been little formalized guidance to date on how to ensure remote meetings are accessible. Part of the issue lies with determining who is ultimately responsible for ensuring accessibility. To take the provision of captions as an example, it is necessary for a remote meeting platform to support captions, a process put in place to create captions, and the meeting host and users need to know how to ensure they are included. This demonstrates, the shared responsibility across different audiences, for remote meetings to be accessible. It is with this in mind that in October 2021, a first public working draft on the accessibility of remote meetings was created to gather important accessibility considerations in the one publication. In the first review a significant amount of feedback was received which has greatly enhanced the guidance provided. This guidance has been added and is now available for review in a second public working draft. This draft is sectioned into different audience groups and includes guidance on vendor procurement planning. It is critical for organizations to make informed decisions about the accessibility of remote meeting platforms they choose to use. The document covers the need for remote meeting platforms to adhere to accessibility standards in their development, and the need to ensure content used in a remote meeting is accessible to all participants. There is also guidance for hosts and users to ensure all accessibility features are made available for an online, or hybrid meeting. The Research Questions Task Force<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2FWAI%2FAPA%2Ftask-forces%2Fresearch-questions%2F&data=05%7C01%7Cjjwhite%40ets.org%7C89f60a699b43443de8a508da28d686b6%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637867199108250269%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=CnjFaN8RmMTDXsqIEbWZYZpkR3LteJwynSc%2FjGil7%2Bc%3D&reserved=0> (RQTF) of the Accessible Platform Architectures<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2FWAI%2FAPA%2F&data=05%7C01%7Cjjwhite%40ets.org%7C89f60a699b43443de8a508da28d686b6%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637867199108250269%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=iXx0d5Wd%2BdQWXjREpWmEA7lWxjCG%2FfD8K32SEkZ1Uoo%3D&reserved=0> (APA) Working Group is actively looking at how best to support these different audiences, while also ensuring that guidance is linked back to relevant W3C standards where applicable. The Second Public Working Draft of Accessibility of Remote Meetings<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2FTR%2Fremote-meetings%2F&data=05%7C01%7Cjjwhite%40ets.org%7C89f60a699b43443de8a508da28d686b6%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637867199108250269%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=NF0qC0a3mA8jmh5z1RhqOxiybpJGsjGYnwqtPo%2BAJZ8%3D&reserved=0> is published to provide guidance on the question ‘What needs to be done, and who needs to do it, for an accessible remote meeting to occur?’. This has led to the research and development of both technical and non-technical guidance for different audiences to support the addressing of this question. Thus, by encompassing the entire process of delivering accessible meetings (not just the technical aspects of Web standards and software implementation), this work builds on and complements the recently published RTC Accessibility User Requirements<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2FTR%2Fraur%2F&data=05%7C01%7Cjjwhite%40ets.org%7C89f60a699b43443de8a508da28d686b6%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637867199108250269%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=vQMgsCvgGeNr3oFzsbD9kOMIlMxlEjzPd2zIy8sOiLM%3D&reserved=0>. We welcome your feedback! Review and comments on the draft are encouraged. The Task Force welcomes additional research-based evidence, comments on the document, and responses to the editor’s notes included in the draft. WAI E-mail - Accessibility of Remote Meetings (Second PWD) For Review: Accessibility of Remote Meetings - Second Public Working Draft Dear WAI Interest Group, W3C WAI invites you to comment on the Second Public Working Draft of the Note: Accessibility of Remote Meetings https://www.w3.org/TR/remote-meetings/<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2FTR%2Fremote-meetings%2F&data=05%7C01%7Cjjwhite%40ets.org%7C89f60a699b43443de8a508da28d686b6%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637867199108250269%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=NF0qC0a3mA8jmh5z1RhqOxiybpJGsjGYnwqtPo%2BAJZ8%3D&reserved=0> Background: Remote meeting is an umbrella term used to describe real-time discussions or presentations held between two or more parties online. A remote meeting generally requires the use of an online meeting platform on an online device such as a computer, smartphone or digital assistant that allows participants to interact with each other. Typical features of remote meeting platforms include the use of audio communication via an online microphone or traditional telephone, video communication via an online camera, a chat feature for text-based communication and the ability to share content. This can include the sharing of a participant’s computer screen, the sharing of an on-screen presentation with media-rich content such as slides and videos, and the transferring of files. In broad terms, the accessibility requirements of standard remote meeting delivery rely on three distinct elements: * The accessibility of the remote meeting platform; * The accessibility of content that is shared during the meeting; and * The accessibility awareness of host participants when the remote meeting is taking place. * The accessibility challenges faced by people with disabilities participating in remote meetings will depend on how these three elements interact. The issues faced by people with disabilities will vary depending on the implementation of accessibility requirements and current limitations of remote meeting software. While W3C has applicable guidance across several standards and Notes relating to real-time communication and XR, it is this level of complexity that this document endeavours to address. *Learn more from this blog post*: Accessibility of Remote Meetings – Call for Review https://www.w3.org/blog/2021/10/accessibility-of-remote-meetings-call-for-review/<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2Fblog%2F2021%2F10%2Faccessibility-of-remote-meetings-call-for-review%2F&data=05%7C01%7Cjjwhite%40ets.org%7C89f60a699b43443de8a508da28d686b6%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637867199108250269%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=80sluerFSIRrIs%2BBiX4fefKYuVqPaU5gf7YO8fOn%2FvA%3D&reserved=0> For in-progress updates to the document, see the Editors' Draft at: https://w3c.github.io/apa/remote-meetings/<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fw3c.github.io%2Fapa%2Fremote-meetings%2F&data=05%7C01%7Cjjwhite%40ets.org%7C89f60a699b43443de8a508da28d686b6%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637867199108250269%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=99dI8%2BLYj7Hnt36tIBD%2BZyuzRx2lhcHf1ZBbv6HRmpM%3D&reserved=0> To comment, please open a new issue in the APA GitHub repository: https://github.com/w3c/apa/issues/new<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fapa%2Fissues%2Fnew&data=05%7C01%7Cjjwhite%40ets.org%7C89f60a699b43443de8a508da28d686b6%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637867199108250269%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ZFtoi36W%2B1p%2B0HeyoicC1O8ThdkhvqrBcvwIunc0izk%3D&reserved=0> Please add the label MEETINGS. Create separate GitHub issues for each topic, rather than commenting on multiple topics in a single issue. If it’s not feasible for you to use GitHub, send comments in e-mail to: public-apa@w3.org<mailto:public-apa@w3.org> Please send comments by *TBA*. Thank you in advance for your comments. Regards, Janina Sajka, APA Working Group Co-Chair Becky Gibson, APA Working Group Co-Chair Jason White, Research Questions Task Force Facilitator Scott Hollier, Research Questions Task Force Facilitator Steve Noble, Pearson Joshue O'Connor, W3C Emerging Web Technology Specialist Michael Cooper, W3C Staff Contact for APA Working Group W3C News - Accessibility of Remote Meetings Heading: Second Public Working Draft: Accessibility of Remote Meetings * SPWD (note) — Second Public Working Draft The Accessible Platform Architectures Working Group ([3]<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2FWAI%2FAPA%2F&data=05%7C01%7Cjjwhite%40ets.org%7C89f60a699b43443de8a508da28d686b6%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637867199108250269%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=iXx0d5Wd%2BdQWXjREpWmEA7lWxjCG%2FfD8K32SEkZ1Uoo%3D&reserved=0>) has published a Second Public Working Draft of Accessibility of Remote Meetings [4]<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2FTR%2Fremote-meetings%2F&data=05%7C01%7Cjjwhite%40ets.org%7C89f60a699b43443de8a508da28d686b6%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637867199108250269%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=NF0qC0a3mA8jmh5z1RhqOxiybpJGsjGYnwqtPo%2BAJZ8%3D&reserved=0>. Remote meeting is an umbrella term used to describe real-time discussions or presentations held between two or more parties online. The issues faced by people with disabilities will vary depending on the implementation of accessibility requirements and current limitations of remote meeting software. While W3C has applicable guidance across several standards and Notes relating to real-time communication and XR, it is this level of complexity that this document endeavours to address. Comments are welcome through TAB. tweet - Accessible Meetings SPWD below from Josh -- needs editing for character count and twitter Accessibility of Remote Meetings has been updated to a Second Public Working Draft: https://www.w3.org/TR/remote-meetings/<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2FTR%2Fremote-meetings%2F&data=05%7C01%7Cjjwhite%40ets.org%7C89f60a699b43443de8a508da28d686b6%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637867199108250269%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=NF0qC0a3mA8jmh5z1RhqOxiybpJGsjGYnwqtPo%2BAJZ8%3D&reserved=0> The Accessibility of Remote meetings document looks at the issues faced by people with disabilities accessing meetings remotely. ________________________________ This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited. Thank you for your compliance. ________________________________
Received on Thursday, 28 April 2022 14:02:17 UTC