Re: Maturity Model Group Note Message

We will address all comments at this week’s meeting. For perspective, I am pasting the message, from Shawn Henry, that Janina suggested we emulate:

Dear WAI Interest Group,

W3C WAI invites you to comment on a Draft W3C Group Note:
     Collaboration Tools Accessibility User Requirements
https://www.w3.org/TR/ctaur/


This is the planned last draft before we publish it as a W3C Group Note.

Overview:

Collaboration Tools Accessibility User Requirements ("CTAUR") covers accessibility user needs, requirements, and scenarios for collaborative content creation and development tools. It addresses features and capabilities unique to interactive, real-time, or asynchronous collaborative applications. This includes co-editing, revision tracking, and in-line comments.

The solutions identified in this document are intended to influence the evolution of future accessibility guidelines, technical specifications, or features of collaboration tools and assistive technologies. They are relevant to software developers who contribute to developing the collaborative experience.

(the acronym CTAUR we pronounce as: see-tower)

Seeking input:

We encourage broad review from a cross-disability perspective. This draft incorporates substantial revisions made in response to comments on the previous Working Drafts by various stakeholders, including W3C's Cognitive and Learning Disabilities Accessibility Task Force (COGA <https://www.w3.org/groups/tf/cognitive-a11y-tf>). These comments led to adding significant requirements and clarifying the document's scope. We especially request comments on the following issues and questions:

1. We came to understand the collaborative editing environment in terms of managing complexity. We observed that many word processing, spread sheet, software development, and media development environments are themselves intrinsically complex. To this, collaborative tooling adds a further layer of complexity: the management of proposed, accepted, and rejected edits from multiple participants. Does this framing make sense? Is its importance clearly communicated by the document?
2. Do we delineate between the content creation elements of software and those relating to managing collaboration sufficiently? Is the distinction meaningfully communicated? Do you agree with this scoping?
3. We inserted a section in our Introduction on Social Considerations. This brief section is included to communicate which stakeholders we regard responsible for which aspects of collaborative efforts. Is this helpful?
4. We created a glossary to define the term "WYSIWYG" in response to a comment. Are there other terms we use you would like defined in the glossary?

Comments:

To comment, please open a new issue in the document's GitHub repository:
https://github.com/w3c/ctaur/issues/new

Please 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-rqtf@w3.org<mailto:public-rqtf@w3.org?Subject=Re%3A%20For%20Wide%20Review%3A%20Collaboration%20Tools%20Accessibility%20User%20Requirements%20%20(%22CTAUR%22)&In-Reply-To=%3C85f8bb77-ebb1-4009-acdb-10190148e38b%40w3.org%3E&References=%3C85f8bb77-ebb1-4009-acdb-10190148e38b%40w3.org%3E> Please:
* put your comments in the body of the message, not as an attachment
* start your e-mail subject line with: [CTAUR]

Please send comments by 30 September 2024.

Regards,
Shawn Lawton Henry for:
Scott Hollier and Jason White, Research Questions Task Force (RQTF) Facilitators
Janina Sajka and Matthew Atkinson, Accessible Platform Architectures (APA) Working Group Co-Chairs
Roy Ran, W3C Staff Contact for APA Working Group


--
Shawn Lawton Henry
W3C Web Accessibility Initiative (WAI) Program Lead
W3C Accessibility Education and Communications Lead
www.w3.org/People/Shawn
Received on Wednesday, 17 July 2024 14:52:22 UTC

  *   This message: Message body<https://lists.w3.org/Archives/Public/public-wai-announce/2024JulSep/0001.html#start>
  *   Previous message: Shawn Henry: "For Wide Review: Guidance on Applying WCAG 2 to Non-Web Information and Communications Technologies (WCAG2ICT)"<https://lists.w3.org/Archives/Public/public-wai-announce/2024JulSep/0000.html>

  *   Mail actions:
     *   respond to this message<mailto:public-wai-announce@w3.org?Subject=Re%3A%20For%20Wide%20Review%3A%20Collaboration%20Tools%20Accessibility%20User%20Requirements%20%20(%22CTAUR%22)&In-Reply-To=%3C85f8bb77-ebb1-4009-acdb-10190148e38b%40w3.org%3E&References=%3C85f8bb77-ebb1-4009-acdb-10190148e38b%40w3.org%3E>


     *   mail a new topic<mailto:public-wai-announce@w3.org>
  *   Contemporary messages sorted:
     *   by date<https://lists.w3.org/Archives/Public/public-wai-announce/2024JulSep/index.html#msg1>


     *   by thread<https://lists.w3.org/Archives/Public/public-wai-announce/2024JulSep/thread.html#msg1>


     *   by subject<https://lists.w3.org/Archives/Public/public-wai-announce/2024JulSep/subject.html#msg1>


     *   by author<https://lists.w3.org/Archives/Public/public-wai-announce/2024JulSep/author.html#msg1>
  *   Help:
     *   how to use the archives<https://lists.w3.org/Help/>


     *   search the archives<https://www.w3.org/Search/Mail/Public/search?type-index=public-wai-announce&index-type=t>
This archive was generated by hypermail 3.0.0<https://github.com/hypermail-project/hypermail/>: Wednesday, 17 July 2024 14:52:22 UTC


From: Angela Barker <angela.barker@ukg.com>
Date: Monday, August 12, 2024 at 1:12 PM
To: Charles LaPierre <charlesl@benetech.org>, Jeff Kline <jeffrey.l.kline@gmail.com>, David Fazio <dfazio@helixopp.com>, Maturity Model TF <public-maturity@w3.org>
Subject: Re: Maturity Model Group Note Message
Agreed with Jeff’s edits and the note about not calling a lot of attention to the scoring. Cheers, Angela _______________________________ Angela Barker (she/her/hers), CPACC | Director, Accessibility
External (angela.barker@ukg.com<mailto:angela.barker@ukg.com>)
  Report This Email<https://protection.inkyphishfence.com/report?id=bmV0b3JnZnQ4NDM0NDAvZGZhemlvQGhlbGl4b3BwLmNvbS8yYjE3YWI2MDIwYjg1NDcwNmYyNGRkOWQ5ZGQ3NjkyMS8xNzIzNDkzNTY3LjY1#key=87feaee4c13d8db3e48e6f5cabfdfefc>  FAQ<https://www.godaddy.com/help/report-email-with-advanced-email-security-40813>  GoDaddy Advanced Email Security, Powered by INKY<https://www.inky.com/protection-by-inky>

Agreed with Jeff’s edits and the note about not calling a lot of attention to the scoring.

Cheers,
Angela

_______________________________
Angela Barker (she/her/hers), CPACC | Director, Accessibility | UKG
Ultimate Kronos Group
M: +1 602 317 6737
Phoenix, Arizona

UKG.com<https://shared.outlook.inky.com/link?domain=www.ukg.com&t=h.eJw1jUEOgyAURK9iWDeA8AV15VWgIBqsEMTQtOndW5o2s5q8yZsnOtOGxgYtOcdjJKSUgk_v8DXcCLo0yFe42xySm3MPHIASM6vHGqbFbus9xPjdMt1KpQVlVPcdSCpmBsYMnxgpBtaSVjIOA--ExKKrZlvNand2U1ir5G2afseVmkr__fUGs28xrA.MEUCIAw8qEGrC6_6PSlks4hQUu-N8iXI-TUMvDvPRxns_IBeAiEAj8pUH-20QBF4eysgKn-TOEnPERWLWJ22aZSwRD8fBFY> | Our purpose is people.
Follow UKG: LinkedIn<https://shared.outlook.inky.com/link?domain=www.linkedin.com&t=h.eJw1jcsOgyAQRX_FsG54iSCu_BUoqAQKhGLsI_33SpNmMovJuXPuG-wlgKkDW635PiF0HAcMLnprXITXdEPnZhWfaPcruHTAt3C0NZV1qSPrGcPILOrl0rzZ4B4p598b1UQozTHFehyYwHyhzBh5jhFcUoKIoD2T_cAF5EMz22ZWcbVBQa2Kt2U-O5usUdPo__58AQRtOCA.MEUCIQDYkCDC2BmH07ttUVxxY9ijy5g8mB3Iry6QSYU0yBIGewIgWCuE4rHNCLoUXu9wvFxcsSDziNzFG7tGy-pZ7D82g0M> | YouTube<https://shared.outlook.inky.com/link?domain=www.youtube.com&t=h.eJw1zE0LwiAAxvGvEp5DN-d02ymKLtGIoC7ddOoWe3E5Zb3Qdy-DeE4Pf_i9gLcdKBagcW6cCoTmeYYP450XClamR1XDh0F16LzZXcqTvRz0uryVs98Tp7dTfwTLBWgDMChnbK1dRhJCIiQ1f17NqlHd9W7G8WdhETMuaIQjkaWERVRjImX-nWQ0xzGKGU5InqSUQZoGWQWZD7XqOBTctsqufFsHLFQZ6v-_PzDBPuE.MEUCID_fnSc8Vy6aqVeDjmQr9-soZaybeNh1KSWe0JTtzbabAiEAyNVPqIy_OVc5b3uXo1v_dBgIT9FFLXf2-acxP1aV5Bs> | Twitter<https://shared.outlook.inky.com/link?domain=twitter.com&t=h.eJw1jE0OwiAYRK_SsDaFUn7arrozxrUHgAJtUwSCX6PReHfFxMxq8mbeC-3Zo6FCC0C6DRjDfQWwuZ7iFV_Ox1OY0KFCW5kECzHPDjrWMkawceq5xnGxfn3ElH4PqhuptCCU6I4zSYSjzJj-GyNFTxvcSNqyvuVC1oIXsy1mFWbrVa1V3mwe920uskJNof_-_gAriDPm.MEQCIHDULXXZH98j7x411edZ5lsoE8n0Gqx1Mbz5gKEoBHqFAiA5vgF23aQCSuaHC8qu16XeSXy2QbISnezxjYqYVoQqgA>
Follow me: LinkedIn<https://shared.outlook.inky.com/link?domain=www.linkedin.com&t=h.eJw1jU0OgyAYRK9iWDeAiKCuvAqUTyVQMBRDf9K7t7RpZjWZvDdPdCSPpgZtOe_XiZBSCvY2ODA24HO8EBuICit45Y6i7kDQqUGuEgFyTOuSB95xTolZ1MPGeQNvb3HfvyzTrVRaUEb10HNJxcK4MeMnRoqRtaSVrONj1wuJRV_NUM2_P6xVcpDmw61VVldT139_vQFOUTnm.MEUCIQDLRr0zsQEAPCwgIOP6Y3yySwM6dOBfzdQ7wyf_qLUs6QIgGNT9WdtJa7rE9BBsqA7Y5uBt_w3cOdhZbJ_UZaU236o>

Chair of ADAPT (Accessibility and Disability Allies Partner Together) Employee Resource Group


From: Charles LaPierre <charlesl@benetech.org<mailto:charlesl@benetech.org>>
Date: Monday, August 12, 2024 at 6:41 AM
To: Jeff Kline <jeffrey.l.kline@gmail.com<mailto:jeffrey.l.kline@gmail.com>>, David Fazio <dfazio@helixopp.com<mailto:dfazio@helixopp.com>>, Maturity Model TF <public-maturity@w3.org<mailto:public-maturity@w3.org>>
Subject: [External Origin] Re: Maturity Model Group Note Message
Good points Jeff, I agree, and now that you point them out I am wondering why I didn't catch them 😉


Thanks

Charles

EOM



________________________________
From: Jeff Kline <jeffrey.l.kline@gmail.com<mailto:jeffrey.l.kline@gmail.com>>
Sent: Monday, August 12, 2024 6:35 AM
To: David Fazio <dfazio@helixopp.com<mailto:dfazio@helixopp.com>>; Maturity Model TF <public-maturity@w3.org<mailto:public-maturity@w3.org>>
Subject: Re: Maturity Model Group Note Message


Hi David,



Looks good. I have a few proposed in line edits, and comments below.









Regards,





[A picture containing text, black, clock  Description automatically generated]<https://shared.outlook.inky.com/link?domain=strategicaccessibility.com&t=h.eJw1jMsOgyAUBX_FsG4EEUFd-Ss8rkikYvCa2Db995YmzVmdzGRe5MyRjBVZEPeR0gOzRvDBamvhOIIJMeCjtulOya0ia1E3wJT9jL1ohWDUzfoZ0rRADFfa95_LTaO0kYwz03dCMTlz4dzwnVNy4A1tFG_F0HZS1bIrZShlvXmIujY6r5Cnc_UlVqgr9P_fH5o7N40.MEUCIAQ-fzd5GEWiD2TKwbJVc2UpFZUwdf0BtWXLwCGghr6hAiEAsraIt7U0SE65kJiPWiOEWMTctqj2BOuGQtIHnL56Hm4>

 Jeff@strategicaccessibility.com<mailto:Jeff@strategicaccessibility.com>

 5  1  2   .   4  2  6   .   9   7  7  9



From: David Fazio <dfazio@helixopp.com<mailto:dfazio@helixopp.com>>
Date: Sunday, August 11, 2024 at 11:45 PM
To: Maturity Model TF <public-maturity@w3.org<mailto:public-maturity@w3.org>>
Subject: Maturity Model Group Note Message

I have drafted a message to send leadership when we are ready to publish our Group Note. Please, see below. Feel free to reply with comments. We will discuss on Wednesday.

____________________________________________

Dear WAI Interest Group,



W3C WAI invites you to comment on a Draft W3C Group Note:

Accessibility Maturity Model



https://w3c.github.io/maturity-model/<https://shared.outlook.inky.com/link?domain=w3c.github.io&t=h.eJw1jE0OgyAYBa9iWLd8CAjqyquAIBJRDIX0L717y6J5q5eZzBuVFNDYoDXn8zYC3NmMnc9r0dhH2FUuyefndY_GBkCXBm3VPmyOyS2554xzAmZRLx-n1Qb_iOeJ57gD1a1UWhBKdN9xScRCuTHDb0aKgbbQSsr4wDohsehq2dayOpwNCmuVNpumsrkaq9RU-v-fLwYEOBU.MEQCIF7ucWojW2QMdVVsZCOhoVsaBqVnurtesXYxEpFHzK_MAiAyqQEpKtT0cOw3dhb4x_dsFzRNYZQI1Je8GICoKcXB7Q>



This is the planned last draft before we publish it as a W3C Group Note. <jk> Are we sure we want to commit to this? Its possible we may need another draft…or two after this.IMO <jk>



Overview:



The Accessibility Maturity Model provides a practical methodology for organizations of any size to evaluate, monitor, <jk> implied by the other 2 descriptors<jk> and continuously improve their internal governance through policies, processes, and practices to achieve organizational accessibility goals expectations <jk> too many descriptors. This one is less concrete more aspirational<jk> and requirements.



The contents of this document are intended to provide a framework for identifying <jk>which describes<jk> key elements, within any organization, that impact organization compliance with accessibility goals, expectations, <jk> see comment above<jk>and requirements. Additionally, it informs organizations how to determine whether, and how well, those elements are operating in a manner that supports its overall  digital accessibility initiatives and success.



Requesting feedback:



We encourage broad review from a wide range of organization sizes and industries. This draft incorporates substantial revisions  and refinements made in response to comments on the previous Working Drafts by various stakeholders. Stakeholder feedback has resulted in substantial revisions, and refinement. <jk> Is this statement the same as the one before it?<jk>



We are particularly interested in receiving feedback related to scoring methods for this maturity model. <jk> Scoring is not yet covered in the document, only built into the tool, and not with use instructions, so should we call a lot of attention to that aspect for this release?<jk>



Comments:



To comment, please open a new issue in the document's GitHub repository:



https://github.com/w3c/maturity-model/issues<https://shared.outlook.inky.com/link?domain=github.com&t=h.eJw1zEsOgyAABNCrGNatICCoK68CgkhEIXzSX3r3libNrCaTeS9QogNTA7acQ5ogNDZvRbaLP-CNLPAQuUSbH9fDK-2gTanoBC4N2Ovp1NlHs-aBEkoRVKt4Wj9v2tm7D-GHYNlxIRnCSA495YitmCo1fqM4G3EHO44JHUnPeMv6Kusqi9NoJ1op4q7jXHZTsbqquv77-wMnGTsZ.MEUCIFCGokeOqCt--UM9DvvFUMkbsKkrPT7xxfGKEpiNEBfjAiEA7l1l00TSOMBcsHzxbV0lvZDvHAxNOLvjU-0GNn-YPqs>

Please 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-maturity@w3.org<mailto:public-maturity@w3.org> Please:

put your comments in the body of the message, not as an attachment



start your e-mail subject line with: Maturity Model Draft