- From: White, Jason J <jjwhite@ets.org>
- Date: Thu, 29 Jul 2021 14:00:13 +0000
- To: Scott Hollier <scott@hollier.info>, Janina Sajka <janina@rednote.net>
- CC: "public-rqtf@w3.org" <public-rqtf@w3.org>
I'm well into the process already. For now, I have created a branch in my local copy of the APA repository, converted the document to HTML, and added required markup for ReSpec (including section elements). I haven't changed the structure of the document yet. Who should be named as editors or as authors? Scott, me, probably Judy (as author or editor?) - anyone else? I have meetings this morning, but I will return to this today. -----Original Message----- From: Scott Hollier <scott@hollier.info> Sent: Thursday, 29 July 2021 0:56 To: Janina Sajka <janina@rednote.net>; White, Jason J <jjwhite@ets.org> Cc: public-rqtf@w3.org Subject: [EXTERNAL] RE: Plans for our Accessibility of Remote Meetings document To Jason and Janina Agree to move the contents to HTML. IS there anything I can do to help this process? For example, if I gtook the wiki and applied proper structure to it in a Word document and then we looked to convert that to HTML, would that help or hinder the cprocess? Happy to do it if that helps. Scott. Dr Scott Hollier Digital Access Specialist Mobile: +61 (0)430 351 909 Web: https://nam10.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.hollier.info%2F&data=04%7C01%7Cjjwhite%40ets.org%7C60cc913babe148f5285008d9524d22ef%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637631313641619974%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=6JYMUy31Ge3aH3I80bnCj4dqtF0b2QjrPd4zAeY2BMk%3D&reserved=0 Technology for everyone Keep up with digital access news by following @scotthollier on Twitter. -----Original Message----- From: Janina Sajka <janina@rednote.net> Sent: Thursday, 29 July 2021 4:58 AM To: White, Jason J <jjwhite@ets.org> Cc: public-rqtf@w3.org Subject: Re: Plans for our Accessibility of Remote Meetings document Hi, Jason: I'm in favor of moving to html, but let's let respec do the levels and just put our content in section elements. Janina White, Jason J writes: > If we are agreed that the document should be converted to HTML, I can perform the conversion and edit the results. > I’ve looked at what would be involved. I think the heading structure is currently inconsistent (i.e., use of h1, h2, h3 etc.), and it ought to be improved. Everything else should be relatively straightforward. > > From: White, Jason J > Sent: Wednesday, 28 July 2021 11:18 > To: public-rqtf@w3.org > Subject: Plans for our Accessibility of Remote Meetings document > > Dear colleagues, > At the meeting today, the two leading options for further development of the Accessibility of Remote Meetings document appeared to be: > > 1. To create a Note-track deliverable. > 2. To develop it as a W3C/WAI Resource. > No one expressed support for leaving it as a Wiki page. My personal view is that it is a publication opportunity which we should pursue. > Both options involve converting the document to a suitable HTML format. To answer a question that Janina raised at the meeting, I quickly ran Pandoc to convert the existing wiki page to HTML. The resulting markup is generally of good quality (XHTML 5). There would be some markup editing needed, of course, but it wouldn’t be extensive. > W3C Notes use ReSpec; I don’t know what the format requirements are for WAI Resources, but I wouldn’t expect them to be difficult to satisfy. If ReSpec can be used for a WAI Resource, then we could convert to HTML and ReSpec format even before deciding what type of document (Note or Resource) we ultimately wanted to publish. Thus, as expected, the conversion into whatever HTML format we need should be a not greatly time-consuming, once-only operation. > It seems to me there was a balance of opinion at the meeting today (not necessarily a consensus) that we should seek wide review of this document, when ready, as we would a Note-track publication. Proceeding toward a Working Group Note would give us a more formal development process and established procedures for documenting and resolving issues. I don’t know what processes are associated with developing WAI Resources, as I’ve never been associated with one. It is my understanding that a Note implies a greater level of W3C review, and may thus be preferable from the perspective of individuals and organizations who wish to cite it in their work. Both types of document can be revised relatively easily, if I understand correctly. Would a Resource still undergo the same Call for Consensus by APA to proceed to publication? > Is there any advantage in this case to publishing as a WAI Resource rather than as a Working Group Note? > We appear to be leaning toward wanting the formal process in order to produce a high-quality publication (regardless of what the final status is). > > ________________________________ > > 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. > > ________________________________ -- Janina Sajka https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flinkedin.com%2Fin%2Fjsajka&data=04%7C01%7Cjjwhite%40ets.org%7C60cc913babe148f5285008d9524d22ef%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637631313641619974%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=%2BAHPbMZUFFvC6Do8cDJLo9CD3FV1zhFtgmTtM8KbKwo%3D&reserved=0 Linux Foundation Fellow Executive Chair, Accessibility Workgroup: https://nam10.safelinks.protection.outlook.com/?url=http%3A%2F%2Fa11y.org%2F&data=04%7C01%7Cjjwhite%40ets.org%7C60cc913babe148f5285008d9524d22ef%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637631313641619974%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=BoE3tIHRzVF4bpdhe3tnqV6x82tYjqjuH%2F6g8u9IdI4%3D&reserved=0 The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI) Co-Chair, Accessible Platform Architectures https://nam10.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.w3.org%2Fwai%2Fapa&data=04%7C01%7Cjjwhite%40ets.org%7C60cc913babe148f5285008d9524d22ef%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637631313641629973%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=vaJso%2BkjLBgWI06YsPXubue8%2F4myv%2F%2BN%2BaG4ula0J%2Fc%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. ________________________________
Received on Thursday, 29 July 2021 14:00:30 UTC