14:30:28 RRSAgent has joined #maturity 14:30:33 logging to https://www.w3.org/2026/06/03-maturity-irc 14:30:33 RRSAgent, make logs Public 14:30:34 please title this meeting ("meeting: ..."), Fazio 14:31:00 meeting: Maturity Model Task Force 14:31:07 Agenda+ New Business 14:31:07 Agenda+ Github Issue #323 Review Suggested Language to Strengthen Procurement Dimension 14:31:07 Agenda+ Continue with GitHub Issues 328 & 334: Abstract & About Section Definitions 14:31:19 chair: David Fazio 14:31:26 present+ 14:57:56 Neha has joined #maturity 14:58:48 Fazio has joined #maturity 14:59:20 meeting: Maturity Model Task Force 14:59:29 chair: David Fazio 14:59:40 JeffAdams-UN has joined #maturity 14:59:58 Mark_Miller has joined #Maturity 15:00:18 present+ 15:00:37 present+ 15:01:43 SusiPallero has joined #maturity 15:01:50 Dr_Keith has joined #maturity 15:02:25 Present+ 15:04:38 scribe+ 15:05:13 Sheri_B-H has joined #maturity 15:05:18 scribe+ 15:05:24 (backing up Susi) 15:07:25 present+ 15:07:41 janina has joined #maturity 15:07:45 present+ 15:07:59 zakim, next item 15:07:59 agendum 1 -- New Business -- taken up [from Fazio] 15:09:18 Susi was authorized to add classes on maturity model to her program at the University of Barcelona 15:10:27 CharlesL has joined #maturity 15:10:39 present+ 15:12:20 classes are available on zoom, you can hear it in English or Spanish 15:13:35 zakim, next item 15:13:35 agendum 2 -- Github Issue #323 Review Suggested Language to Strengthen Procurement Dimension -- taken up [from Fazio] 15:15:34 Mark_Miller he will be working along with Jeff on the structure of the abstract to define it and develop 15:15:55 there's an email with suggestions that we will go through starting with Procurement 15:16:12 https://github.com/w3c/maturity-model/issues/323 15:16:13 https://github.com/w3c/maturity-model/issues/323 -> Issue 323 Strengthen motivation for procurement language (by judbrew) [Editorial] 15:17:53 .... 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:17:53 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:17:58 .... 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:17:58 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:18:01 JeffAdams-UN is reading outloud the issue 323 The current text seems to under-motivate the strategic importance of procurement policy in an organization's accessibility ecosystem, and as feedback towards improving the offerings of product vendors. Please consider clarifying "When accessibility criteria..." sentence and expanding the motivations 15:18:01 along the following lines. 15:19:02 Sheri_B-H suggests not needing accomodations if you procure accessible software 15:19:41 it also allows more people with disabilities to join the company and bring up the accessibility topic more 15:19:53 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. 15:19:53 The majority of an organization's ICT assets result from procurement transactions and contracts. Therefore, accessibility criteria must 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 15:19:53 reducing time, cost and risks of deploying inaccessible IT deliverables. Additionally, when an organization communicates to product vendors that accessibility requirements are part of the product selection criteria, it can help incentivize product developers to improve their future product offerings. 15:22:20 Fazio suggests adding what Sheri proposed about reducing the need of accommodations when we procure accessibility software 15:22:23 Sheri_B-H 15:22:52 suggests finding something in the middle and merge both perspectives 15:23:13 add accommodation reduction 15:23:45 zakim, next item 15:23:45 agendum 3 -- Continue with GitHub Issues 328 & 334: Abstract & About Section Definitions -- taken up [from Fazio] 15:24:44 Issue 328: The abstract could benefit from a clearer description of what the model can do: 15:24:44 "help you measure where you are as an organisation or department. 15:24:44 At the moment it reads quite “salesy”." added by iadawn 15:25:22 Issue 334: "The “About the Accessibility Maturity Model” section could be much simplified and, again, less “salesy”. 15:25:22 Also, it doesn’t quite reflect what the AMM can help you achieve - first and foremost it is a way of measuring organisational maturity. This section seems to suggest that it will sort out all your organisational accessibility issues." added by iadawn 15:26:32 there's 2 issues as iadawn think these should be addressed separately because Abstract and About have two different purposes and are different sections 15:27:31 Mark_Miller is presenting a proposal for Abstract and Revised How to Use 15:28:51 How to Use the AMM Structure proposed is "Purpose" "Scope" "Out of Scope" 15:29:15 Sheri_B-H suggests working examples 15:30:22 q? 15:30:27 maybe at bottom of section 1 as a subsection 15:31:50 Fazio suggest it might be an appendix with an interlink 15:32:50 Sheri_B-H risk of people missing all the rest of the content and the terms for going to the example before they keep reading 15:32:57 q+ 15:33:43 We agree on adding a link to the examples 15:33:57 q? 15:34:10 ack JeffAdams-UN 15:34:15 q+ 15:36:00 Sheri_B-H suggests that if the link is taking to the spreadsheet it can be a subsection like 2.5 15:38:17 janina don't lock the language around the spreadsheet 15:38:54 we don't want people to think the spreadsheet is the only way of doing it 15:39:12 +1 15:39:47 Mark_Miller suggests a new section "section 3" and the majority of the group agrees 15:41:06 q+ 15:42:10 Sheri_B-H suggests a section 3 in between the dimensions and the example 15:43:54 +1 to Sheri suggestion 15:46:39 The group is discussing about the spreadsheet, how to improve it and maintain it or migrating it to a different format, but addressing it is not part of the AMM just a tool with suggestions and examples on how to apply the AMM 15:51:17 janina The point of worked example can be left out as it doesn't belong in this document 15:54:35 Susi: can we write articles and include links to them in the maturity model 15:55:13 david: We can't have an appearance of endorsement. Articles can link into the maturity model, but the model can't link to articles 15:55:23 janina: we could do the example as a separate document 15:56:08 janina: it could be in the wiki, part of the package, but it can't be in the model itself 15:56:46 zakim, end meeting 15:56:46 As of this point the attendees have been Fazio, Mark_Miller, Neha, SusiPallero, JeffAdams-UN, janina, CharlesL 15:56:48 RRSAgent, please draft minutes 15:56:50 I have made the request to generate https://www.w3.org/2026/06/03-maturity-minutes.html Zakim 15:56:57 I am happy to have been of service, SusiPallero; please remember to excuse RRSAgent. Goodbye 15:56:57 Zakim has left #maturity 16:17:01 CharlesL has left #maturity 18:28:00 janina has left #maturity