- From: Bradley-Montgomery, Rachael <rmontgomery@loc.gov>
- Date: Thu, 13 Oct 2022 15:18:25 +0000
- To: "janina@rednote.net" <janina@rednote.net>
- CC: public-cognitive-a11y-tf <public-cognitive-a11y-tf@w3.org>, AGWG Chairs <group-ag-chairs@w3.org>, "group-apa-chairs@w3.org" <group-apa-chairs@w3.org>
Hello Janina,
Thank you for those clarifications.
COGA is actively working on feedback but will not be able to provide it until the first week of November.
AG chairs have some concerns about the publication schedule. We would like to better understand the background and next steps before this goes forward. I will send an email to both chair groups to start a quick discussion.
Thank you,
Rachael
On 10/13/22, 10:37 AM, "janina@rednote.net" <janina@rednote.net> wrote:
Hi Jennie, All:
The scope of the Collaboration Tools Accessibility User Requirements
document is defined descriptively. In other words we discuss certain
characteristics that distinguish content creation from communications
technologies. Thus, Google/Microsoft docs, sheets, etc are in scope, as
is github; because all of these focus on the creation of content in real
time and/or asyncronously. The document section to look at for this is
here:
https://w3c.github.io/ctaur/#introduction
Communication tools such as IRC, Slac, Zoom,
etc are covered in the already published RTC AUR and the Accessible
Meetings Note documents.
Hope this helps!
Please note we're currently in an APA CfC to publish the current draft
as FPWD, because RQTF will take a break during November and December.
Work will resume on this document in January, and COGA comments will be
most welcome. That would any comments on scope, just as on any other
aspect of the draft.
Best,
Janina
Delisi, Jennie (MNIT) writes:
> Hi Janina,
> I’m a bit behind in a task for COGA. Hoping you are able to respond in the next day or so. Please copy the task force on this response (copied here as well).
> We are working on feedback on the Collaboration Tool Accessibility document. We have a question about scope for this document.
> Can you provide more information about which tools could be examples that are covered in the document?
> Also, can you provide more information about the types of tools that are out of scope?
> Thank you,
> Jennie
>
> Jennie Delisi, MA, Certified Professional in Web Accessibility (CPWA)
> Accessibility Analyst | Office of Accessibility
> Minnesota IT Services | Partners in Performance
> 658 Cedar Street
> St. Paul, MN 55155
> O: 651-201-1135
> Information Technology for Minnesota Government | mn.gov/mnit<http://mn.gov/mnit>
> [Minnesota IT Services Logo]
> [Facebook logo]<https://www.facebook.com/MN.ITServices>[LinkedIn logo]<https://www.linkedin.com/company/minnesota-it-services/>[Twitter logo]<https://twitter.com/mnit_services>
>
--
Janina Sajka (she/her/hers)
Accessibility Consultant https://linkedin.com/in/jsajka
The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Co-Chair, Accessible Platform Architectures http://www.w3.org/wai/apa
Linux Foundation Fellow
https://www.linuxfoundation.org/board-of-directors-2/
Received on Thursday, 13 October 2022 15:18:39 UTC