14:28:40 <RRSAgent> RRSAgent has joined #maturity
14:28:44 <RRSAgent> logging to https://www.w3.org/2026/06/17-maturity-irc
14:28:44 <Zakim> RRSAgent, make logs Public
14:28:45 <Zakim> please title this meeting ("meeting: ..."), Fazio
14:29:00 <Fazio> meeting: Maturity Model Task Force
14:29:12 <Fazio> chair: David Fazio
14:29:43 <Fazio> regrets: Jeff Adams, Stacey Swineheart
14:53:31 <Fazio> Agenda+ New Business
14:53:31 <Fazio> Agenda+ Github Issue #323 Review Suggested Language to Strengthen Procurement Dimension
14:53:31 <Fazio> Agenda+ Continue with GitHub Issues 328 & 334: Abstract & About Section Definitions
15:00:28 <janina> janina has joined #maturity
15:00:32 <Dr_Keith> Dr_Keith has joined #maturity
15:00:42 <Dr_Keith> present+
15:01:13 <jkline> jkline has joined #maturity
15:01:20 <janina> present+
15:01:23 <jkline> present+
15:01:53 <Mark_Miller> Mark_Miller has joined #Maturity
15:02:03 <Crispy> Crispy has joined #maturity
15:02:04 <CharlesL> CharlesL has joined #maturity
15:02:09 <Crispy> present+
15:02:14 <Sheri_B-H> Sheri_B-H has joined #maturity
15:02:15 <CharlesL> present+
15:02:22 <Sheri_B-H> present+
15:03:04 <Crispy> scribe+
15:03:08 <Mark_Miller> present+
15:04:25 <Crispy> Zakim, next item
15:04:25 <Zakim> agendum 1 -- New Business -- taken up [from Fazio]
15:04:27 <SusiPallero> SusiPallero has joined #maturity
15:04:31 <SusiPallero> Present+
15:05:47 <Crispy> MM CSUN session to be repeated for ICCHP in Czech Republic
15:06:03 <Neha> Neha has joined #maturity
15:06:42 <Crispy> David to be doing a session on Learning management systems
15:07:22 <Crispy> Date of Conf July 16-17th
15:07:43 <Neha> present+
15:08:07 <Crispy> jkline - created a whitepaper on MM and W3C version superiority, posted on LI for access download
15:08:34 <Crispy> It's out there, go take a look
15:09:14 <Crispy> David, can you post a direct link for us, and to put in the minutes?
15:09:31 <Crispy> jkline - doesn't have a link at present
15:09:41 <Crispy> Go to LI
15:10:06 <Crispy> Zakim, next item
15:10:06 <Zakim> agendum 2 -- Github Issue #323 Review Suggested Language to Strengthen Procurement Dimension -- taken up [from Fazio]
15:10:23 <Sheri_B-H> Here are the three concepts
15:10:23 <Sheri_B-H> 1) Jeff's language
15:10:23 <Sheri_B-H> Procurement is a strategic process focused on finding and acquiring cost-effective products needed by an organization. Activities in procurement include sourcing, negotiation, and selection of goods and services. The majority of an organization's ICT assets result from procurement transactions and contracts. Therefore, accessibility criteria must
15:10:23 <Sheri_B-H> be integrated as an essential consideration of procurement processes, contract language, etc. This ensures that an organization will be more capable of providing accessible products, services, and workplaces while reducing time, cost and risks of deploying inaccessible IT deliverables. Additionally, when an organization communicates to product
15:10:25 <Sheri_B-H> vendors that accessibility requirements are part of the product selection criteria, it can help incentivize product developers to improve their future product offerings.
15:10:25 <Sheri_B-H> 2) not sure where this came from, think it is existing language?
15:10:25 <Sheri_B-H> When accessibility criteria are integrated as an essential consideration of procurement processes and contract language, an organization can be more capable of providing accessible products, services, and workplaces. It can save time through more efficient production of accessible content, and avoid unnecessary time spent in remediation of
15:10:26 <Sheri_B-H> inaccessible content created by tools that do not support accessibility. Additionally, if an organization communicates its product selection criteria to product vendors, it can help incentivize product developers to improve their future product offerings.
15:10:26 <Sheri_B-H> 3) missing concepts identified by Sheri
15:10:26 <Sheri_B-H> and reduce the need for accommodations and increase disabled employment which will make accessibility throughout the organization easier
15:10:27 <Sheri_B-H> Here is what I came up with:
15:10:43 <Sheri_B-H> Procurement is a strategic process focused on finding and acquiring cost-effective products needed by an organization. Procurement activities include sourcing, negotiating, and selecting goods and services. The majority of an organization’s ICT assets, including open source software, are obtained through procurement transactions and contracts.
15:10:43 <Sheri_B-H> Therefore, accessibility criteria must be integrated as an essential consideration of procurement processes, contract language, etc. This ensures that an organization will be better able to provide accessible products, services, and workplaces while reducing the time, cost, and risk of deploying inaccessible IT deliverables.  Adhering to
15:10:43 <Sheri_B-H> accessibility principles in procurement saves time by enabling more efficient production of accessible content and by avoiding unnecessary remediation of inaccessible content created by tools that do not support accessibility. It also reduces the need for accommodations and increases employment among people with disabilities, thereby making
15:10:45 <Sheri_B-H> accessibility more ingrained within an organization. Additionally, when an organization communicates to product vendors that accessibility requirements are part of the product selection criteria, it can incentivize other organizations to improve their future offerings.
15:10:54 <Crispy> Sheri - above is pasted from Sheri's email sent around last week
15:12:54 <Crispy> Can be broken into 2 paragraphs maybe?
15:13:45 <Crispy> Janina - suggesting a slight amendment to the arrangement
15:13:47 <Dr_Keith> I'd recommend removing the "Therefore"  in "Therefore, accessibility criteria must be integrated as an essential consideration of procurement processes, contract language..."
15:15:14 <Sheri_B-H> combining the two sentences: Because the majority of an organization’s ICT assets, including open source software, are acquired through procurement transactions and contracts, accessibility criteria must be integrated as an essential consideration within procurement processes and contract language.
15:15:40 <Sheri_B-H> plus change IT to ICT
15:15:41 <Dr_Keith> +1
15:15:45 <Crispy> +1
15:15:46 <Sheri_B-H> and break into two paragraphs
15:15:53 <Mark_Miller> +1
15:18:21 <Crispy> jkline - questions the use of "solicitation"
15:18:37 <Crispy> Responded to by David and Sheri
15:18:44 <Sheri_B-H> Procurement is a strategic process focused on finding and acquiring cost-effective products needed by an organization. Procurement activities include sourcing, negotiating, and selecting goods and services through a solicitation or purchasing process. Because the majority of an organization’s ICT assets, including open source software, are
15:18:44 <Sheri_B-H> acquired through procurement transactions and contracts, accessibility criteria must be integrated as an essential consideration within procurement processes and contract language. This ensures that an organization will be better able to provide accessible products, services, and workplaces while reducing the time, cost, and risk of deploying
15:18:44 <Sheri_B-H> inaccessible ICT deliverables.
15:18:44 <Sheri_B-H> Adhering to accessibility principles in procurement saves time by enabling more efficient production of accessible content and by avoiding unnecessary remediation of inaccessible content created by tools that do not support accessibility. It also reduces the need for accommodations and increases employment among people with disabilities, thereby
15:18:46 <Sheri_B-H> making accessibility more ingrained within an organization. Additionally, when an organization communicates to product vendors that accessibility requirements are part of the product selection criteria, it can incentivize other organizations to improve their future offerings.
15:18:46 <Crispy> Final Para from Sheri with feedback
15:18:51 <Fazio> q?
15:19:03 <jkline> jkline has joined #maturity
15:20:13 <Crispy> David to message Judy with the above
15:21:37 <Crispy> Zakim, next item
15:21:37 <Zakim> agendum 3 -- Continue with GitHub Issues 328 & 334: Abstract & About Section Definitions -- taken up [from Fazio]
15:22:52 <Crispy> Mark - Started How to Use the MM last week but got side tracked.
15:22:53 <kirkwood> kirkwood has joined #maturity
15:25:19 <Crispy> Susana - has idea of putting an example on how the MM can be used, to help ppl understand what is useful for metrics and identify the steps. What info needs to be compiled for future use.
15:26:05 <Fazio> q?
15:26:18 <Crispy> David - Mentioned that we do not specificy what someone should use, who to use for audit for example
15:26:57 <Crispy> Mark - agrees with idea of examples to help use of the MM
15:27:34 <Fazio> q?
15:28:05 <Crispy> jkline - can we have a resources page
15:28:23 <Crispy> David - we have a wiki for anything to do with the taskforce
15:29:03 <SusiPallero> q+
15:29:10 <Crispy> jkline - from the starts we tried making sure not to tell ppl how to do things
15:29:53 <Crispy> David agrees, and that we can use proof points
15:29:55 <Neha> q+
15:30:14 <Crispy> ack SusiPallero
15:31:35 <Crispy> Susi - Add suggested info to wiki
15:31:39 <Crispy> David agrees
15:31:59 <Crispy> jkline - would we want to reference the wiki?
15:32:04 <Crispy> David sees no issue
15:32:12 <SusiPallero> ack
15:32:26 <Crispy> we will wait until it starts getting populated
15:32:35 <Crispy> ack Neha
15:32:44 <Sheri_B-H> q+
15:33:03 <Crispy> ack Sheri_B-H
15:33:18 <janina> q+
15:34:08 <Crispy> Discussion of being careful whats put in the wiki
15:34:10 <Crispy> ack janina
15:34:49 <Crispy> Janina - Wiki is for help towards what we need to do - collect resources there.
15:35:25 <Fazio> q?
15:36:09 <Crispy> David - please submit case studies, etc for the wiki. Please add resources
15:37:20 <Fazio> q?
15:38:45 <Fazio> ack Crispy
15:39:02 <Fazio> Crispy using MM at Toyota
15:42:11 <Fazio> q?
15:42:14 <Crispy> Zakim, next item
15:42:14 <Zakim> I do not see any more non-closed or non-skipped agenda items, Crispy
15:42:28 <Crispy> zakim, previous item
15:42:28 <Zakim> I don't understand 'previous item', Crispy
15:42:40 <janina> agenda?
15:42:57 <Crispy> zakim, item number 2
15:42:57 <Zakim> I don't understand 'item number 2', Crispy
15:43:06 <janina> zakim, take up item 2
15:43:06 <Zakim> agendum 2 -- Github Issue #323 Review Suggested Language to Strengthen Procurement Dimension -- taken up [from Fazio]
15:43:16 <janina> zakim, take up item 3
15:43:17 <Zakim> agendum 3 -- Continue with GitHub Issues 328 & 334: Abstract & About Section Definitions -- taken up [from Fazio]
15:44:27 <Crispy> Mark - Define what the sections should be like
15:44:54 <Crispy> Wflow for applying the MM, recording findings that can be used at each step
15:45:16 <Crispy> assessment spreadsheet and workflow
15:45:27 <janina> q+
15:45:27 <Crispy> operational roles that apply during use
15:45:51 <Crispy> A worked example
15:45:58 <Crispy> Recommended practices
15:46:12 <Crispy> the 5 bullet points in scope
15:46:16 <Crispy> ack janina
15:46:51 <Fazio> q?
15:47:02 <Crispy> Janina - Spreadsheet cannot go in the narrative
15:47:12 <Crispy> Mark - it was from the AI, not to be used
15:48:37 <Crispy> David - David and Sheri originally wrote this
15:48:57 <Crispy> Sheri - Should be interesting to see the Claude update
15:49:03 <Mark_Miller> •	A short document map orienting the reader to what's in §2, §3, and §2.4 (the assessment spreadsheet).
15:49:03 <Mark_Miller> •	An assessment workflow (scope → identify proof points → gather evidence → determine maturity level → record and act).
15:49:03 <Mark_Miller> •	Operational rules pulled forward from §2 that apply during use: cumulative levels, Optimize-requires-full-completion, N/A handling.
15:49:03 <Mark_Miller> •	A worked example (Communications dimension at Launch level).
15:49:05 <Mark_Miller> •	Recommended practices (cross-functional review team, engaging people with disabilities, reassessing on a cadence).
15:49:13 <Mark_Miller> These are what AI suggested.
15:50:51 <janina> Look at: https://bit.ly/a11yedge for the graphic
15:53:47 <Crispy> Mark - Figure out placement as we go
15:54:01 <Crispy> Mark - start with Out of Scope next week
15:56:40 <Crispy> Zakim, end meeting
15:56:40 <Zakim> As of this point the attendees have been Dr_Keith, janina, jkline, Crispy, CharlesL, Sheri_B-H, Mark_Miller, SusiPallero, Neha
15:56:42 <Zakim> RRSAgent, please draft minutes
15:56:44 <RRSAgent> I have made the request to generate https://www.w3.org/2026/06/17-maturity-minutes.html Zakim
15:56:52 <Zakim> I am happy to have been of service, Crispy; please remember to excuse RRSAgent.  Goodbye
15:56:52 <Zakim> Zakim has left #maturity
15:57:12 <Crispy> Dismiss
15:57:28 <Crispy> Zakim dismiss RRSAgent
16:00:45 <Crispy> Crispy has left #maturity
16:34:57 <kirkwood> kirkwood has joined #maturity
17:28:53 <kirkwood> kirkwood has joined #maturity