RE: Authoring Tool Accessibility Guidelines in Accessibility of Remote Meetings page

To Jason

Thanks for following up on this and apologies again that I couldn't make the call this week.  I have a monthly church council meeting that finishes at 9pm when our meeting starts and the agenda for that was pretty packed this month!

There's two issues for me with ATAG 2.0 in this. As I understand it, ATAG 2.0 is about ensuring authoring tools that produce web content can be used by people with disabilities (Part A) and produce accessible content (Part B). However, the outputs from remote meetings aren't published on the web as such, but rather distributed to participants either before or after the meeting. They could be published on the web, but this is a step that the user would require and not a direct output of using remote meeting software. I take the point that tools like Office and other authoring tools absolutely need to conform to ATAG Part A and B hence therapies of ATAG, but if it applies here I think there needs to be a greater explanation about summarising ATAG briefly, explaining how it connects and then having the current points.

The second issue is that there's an inference that ATAG directly applies to the remote meeting software which I find a bit confusing. As it stands, we have a Remote Meetings wiki and a section about ATAG. On the surface it would seem then that ATAG must directly apply to remote meetings as it has its own section, like WCAG has its own section with specific SC that apply to remote meetings. However, as zoom, teams etc are not an authoring tools as I understand it, i.e. it doesn't produce web content, it's confusing to me that the section doesn't currently explain that ATAG is not directly talking about remote meeting software, instead taking people on a journey to say 'here's ATAG, then ATAG applies to development of meeting materials like document production, then document production can be used by meetings, therefore ATAG is important'. .

Also ATAG is usually targeted at the developer sofa authoring tools, but in the context of remote meetings, are developers of remote meeting software also going to be developing authoring tools to produce materials?  It's a bit muddled for me as to who this advice is for. I'm assuming consumers ensuring that an ATAG-compliant tool is  used for resources, but then this advice is provided in other places so I'm not sure as to why ATAG is important to  discuss in this context.

To address this, I think the ATAG reference should clearly state up front that while remote meeting software is not an authoring tool (if you agree that's the case) and therefore ATAG does not apply to that aspect what is important is that people creating materials for remote meetings use an ATAG 2.0-compliant tool, i.e. E one that people with disabilities can use and one that produces accessible content.

Thanks for the opportunity to share my thoughts - or at least my own confusion!

Scott.



[Scott Hollier logo]Dr Scott Hollier
Digital Access Specialist
Mobile: +61 (0)430 351 909
Web: www.hollier.info<http://www.hollier.info/>

Technology for everyone

Keep up with digital access news by following @scotthollier on Twitter<https://twitter.com/scotthollier> and subscribing to Scott's newsletter<mailto:newsletter@hollier.info?subject=subscribe>.

From: White, Jason J <jjwhite@ets.org>
Sent: Thursday, 14 May 2020 2:54 AM
To: Scott Hollier <scott@hollier.info>; Judy Brewer <jbrewer@w3.org>; public-rqtf@w3.org
Subject: Authoring Tool Accessibility Guidelines in Accessibility of Remote Meetings page

Hi Scott,

Thank you for your thoughtful comments. I took an action at the RQTF meeting today to work on the relationship with Authoring Tool Accessibility Guidelines 2.0.

The Remote Meetings page currently notes the following areas of applicability of ATAG 2.0 (quoted below):

*         Authoring tools that partly or fully conform to ATAG 2.0 at any level of conformance are the preferred environment in which to create documents, presentations, multimedia and other materials disseminated to participants in remote meetings.
*         Authoring tools included in or associated with platforms used for remote meetings, such as real-time document editing environments that allow content to be created and edited collaboratively during a meeting, should implement ATAG 2.0.

The first case is meant to cover authoring tools used to prepare materials disseminated during the meetings (e.g., presentations). The second case addresses collaborative editing tools used during meetings (e.g., for live writing or editing of a document during a meeting, where all participants receive the changes in real time).

What would you like to see included by way of clarification? I could summarize provisions of ATAG 2.0, but this would lengthen the Remote Meetings document considerably. None of the ATAG 2.0 Guidelines stood out as particularly important; they're all applicable to authoring tools arising under both of the scenarios noted above.

Let's clarify what is needed, then I'll update the Remote Meetings page appropriately.

From: Scott Hollier <scott@hollier.info<mailto:scott@hollier.info>>
Date: Wednesday, May 13, 2020 at 03:05
To: Judy Brewer <jbrewer@w3.org<mailto:jbrewer@w3.org>>, White, Jason J <jjwhite@ets.org<mailto:jjwhite@ets.org>>, public-rqtf@w3.org<mailto:public-rqtf@w3.org> <public-rqtf@w3.org<mailto:public-rqtf@w3.org>>
Subject: RE: Meeting agenda for 13 May 2020
To Judy

I've just had a read through - it's looking good but I guess still lots to do. I've just e-mailed through an apology for today's meeting unfortunately, but I'll keep an eye on the minutes and I'm happy to take an action to help separate out host/presenter info and address some of the other notes.

One thing that jumped out of me as I read through it - in regards to ATAG, it didn't seem clear to me in the explanation as to why this should be included and on what basis a remote meeting platform is considered an authoring tool in terms of creating web content. I was wondering if it were worth specifically focusing on ATAG 2.0 Part A elements to clarify how developers need to ensure the tool is accessible.

Scott.


[Scott Hollier logo]Dr Scott Hollier
Digital Access Specialist
Mobile: +61 (0)430 351 909
Web: www.hollier.info<https://nam01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.hollier.info%2F&data=02%7C01%7Cjjwhite%40ets.org%7Cde8a8eee1fb446182bdd08d7f70bfc55%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637249503168676763&sdata=QkpNFaXXdnc2i4aeboxX711xV8Lza%2BlEFV%2BHGsvVthU%3D&reserved=0>

Technology for everyone

Keep up with digital access news by following @scotthollier on Twitter<https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftwitter.com%2Fscotthollier&data=02%7C01%7Cjjwhite%40ets.org%7Cde8a8eee1fb446182bdd08d7f70bfc55%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637249503168686758&sdata=p7Fx57rmPkEEtW%2FvCdvxummODiHFyhbSFxOx9thU%2B2w%3D&reserved=0> and subscribing to Scott's newsletter<mailto:newsletter@hollier.info?subject=subscribe>.

From: Judy Brewer <jbrewer@w3.org<mailto:jbrewer@w3.org>>
Sent: Wednesday, 13 May 2020 1:53 PM
To: White, Jason J <jjwhite@ets.org<mailto:jjwhite@ets.org>>; public-rqtf@w3.org<mailto:public-rqtf@w3.org>
Subject: Re: Meeting agenda for 13 May 2020


I have updated the Accessibility of Remote Meetings page, here:

    https://www.w3.org/WAI/APA/task-forces/research-questions/wiki/Accessibility_of_Remote_Meetings<https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2FWAI%2FAPA%2Ftask-forces%2Fresearch-questions%2Fwiki%2FAccessibility_of_Remote_Meetings&data=02%7C01%7Cjjwhite%40ets.org%7Cde8a8eee1fb446182bdd08d7f70bfc55%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637249503168686758&sdata=zoVuMCnBDAbOIINdRCLGUfX5dNCcd%2BhpZ2UgVZBlpVo%3D&reserved=0>#Gap_identification

and would like to talk through and get feedback on the updated content and next steps.

Thank you

 - Judy
On 5/11/2020 9:12 AM, White, Jason J wrote:
Meeting Logistics

  *   Time: Wednesday, 13 May 2020 at 9:00am Boston time (1300 UTC) - please verify what this corresponds to in your time zone.
  *   teleconference logistics (including Zoom password) are on the Web page at
https://www.w3.org/2017/08/telecon-info_rqtf<https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2F2017%2F08%2Ftelecon-info_rqtf&data=02%7C01%7Cjjwhite%40ets.org%7Cde8a8eee1fb446182bdd08d7f70bfc55%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637249503168686758&sdata=wTeadj7tRQWfgLqdr8ThW4bXyxnTMNWqFsY6tmH0QEM%3D&reserved=0>.

Agenda
Note:
The purpose is to continue discussion of the topics considered at last week's meeting.

Topics

1.      Accessibility of remote meetings. Please see the notes collected on the page at
https://www.w3.org/WAI/APA/task-forces/research-questions/wiki/Accessibility_of_Remote_Meetings<https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2FWAI%2FAPA%2Ftask-forces%2Fresearch-questions%2Fwiki%2FAccessibility_of_Remote_Meetings&data=02%7C01%7Cjjwhite%40ets.org%7Cde8a8eee1fb446182bdd08d7f70bfc55%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637249503168696754&sdata=K6xKIiLjIRVZotVm3c4iiInZRXLRUjUrDSMOOBBXZEA%3D&reserved=0>

2.      Addressing open issues on recent publications.
XAUR issues in GitHub: https://github.com/w3c/apa/labels/xaur<https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fapa%2Flabels%2Fxaur&data=02%7C01%7Cjjwhite%40ets.org%7Cde8a8eee1fb446182bdd08d7f70bfc55%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637249503168696754&sdata=eylNF4fiyEDskbEI1KvKy8sJZywE7SuP8DJILPlgj1U%3D&reserved=0>
RTC issues in GitHub: https://github.com/w3c/apa/labels/rtc<https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fapa%2Flabels%2Frtc&data=02%7C01%7Cjjwhite%40ets.org%7Cde8a8eee1fb446182bdd08d7f70bfc55%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637249503168706747&sdata=dRoCoNGeSyOBk2vWgGIxuCZ8SGO02DriNC1uinNvvec%3D&reserved=0>

3.    Topics for discussion at TPAC 2020, based on the development of our two working drafts.

Additional References

  *   WebXR Standards and Accessibility Architecture Issues:
https://www.w3.org/WAI/APA/wiki/WebXR_Standards_and_Accessibility_Architecture_Issues<https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2FWAI%2FAPA%2Fwiki%2FWebXR_Standards_and_Accessibility_Architecture_Issues&data=02%7C01%7Cjjwhite%40ets.org%7Cde8a8eee1fb446182bdd08d7f70bfc55%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637249503168706747&sdata=%2Bf7NJOFyxkOZ6cTB4gu1MOA8fw%2FFal5S5dpeX97iyoY%3D&reserved=0>
  *   Research Questions Task Force - main wiki page that refers to work in progress and other documents: https://www.w3.org/WAI/APA/task-forces/research-questions/wiki/Main_Page<https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2FWAI%2FAPA%2Ftask-forces%2Fresearch-questions%2Fwiki%2FMain_Page&data=02%7C01%7Cjjwhite%40ets.org%7Cde8a8eee1fb446182bdd08d7f70bfc55%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637249503168716741&sdata=iQfd3%2FU9ANYRT6oXq4A%2FxU7GXtok2d%2F7p3%2F4l4F8x2g%3D&reserved=0>
  *   APA Working Group - Verticals to Track: https://www.w3.org/WAI/APA/wiki/Verticals_to_Track<https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2FWAI%2FAPA%2Fwiki%2FVerticals_to_Track&data=02%7C01%7Cjjwhite%40ets.org%7Cde8a8eee1fb446182bdd08d7f70bfc55%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637249503168716741&sdata=QxHtuFdub0NnfJivmy8ilgSeA%2FJJn8JW7vWTGSBPZ2g%3D&reserved=0>

  *   Minutes of previous meeting: https://www.w3.org/2020/05/06-rqtf-minutes.html<https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2F2020%2F05%2F06-rqtf-minutes.html&data=02%7C01%7Cjjwhite%40ets.org%7Cde8a8eee1fb446182bdd08d7f70bfc55%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637249503168726735&sdata=3UyqNFKPcuDKfmUi%2FIXv9QptsvPObnnirolK9SPYqN8%3D&reserved=0>





________________________________

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.

________________________________


________________________________

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.

________________________________

--

Judy Brewer

Director, Web Accessibility Initiative

at the World Wide Web Consortium (W3C)

105 Broadway, Room 7-128, MIT/CSAIL

Cambridge MA 02142 USA

www.w3.org/WAI/<https://nam01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.w3.org%2FWAI%2F&data=02%7C01%7Cjjwhite%40ets.org%7Cde8a8eee1fb446182bdd08d7f70bfc55%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637249503168726735&sdata=w8ulK5HO74FU3ijur4wiTv1GEG%2BfgY01uW07%2F3WiYQo%3D&reserved=0>

________________________________

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.

________________________________