14:49:48 RRSAgent has joined #maturity 14:49:52 logging to https://www.w3.org/2025/04/30-maturity-irc 14:49:52 RRSAgent, make logs Public 14:49:53 please title this meeting ("meeting: ..."), Fazio 14:50:12 meeting: Maturity Model Task Force 14:50:59 chair: David Fazio 14:51:05 present+ 14:51:16 Agenda+ New Business 14:51:16 Agenda+ Github Issue #228 Syncing proof points in the MM document and the assessment tool 14:51:16 Agenda+ Github Issue #193 Appendix Roles need updating (feature request) 15:01:02 janina has joined #maturity 15:01:19 present+ 15:05:02 CharlesL has joined #maturity 15:05:11 present+ 15:06:45 jkline has joined #maturity 15:06:58 present+ 15:07:21 stacey has joined #Maturity 15:07:23 Neha4 has joined #maturity 15:07:25 present+ 15:07:34 scribe+ 15:08:01 zakim, next item 15:08:01 agendum 1 -- New Business -- taken up [from Fazio] 15:08:40 janina: will miss next week 15:09:45 zakim, next item 15:09:45 agendum 2 -- Github Issue #228 Syncing proof points in the MM document and the assessment tool -- taken up [from Fazio] 15:11:55 jeff: left off at procurement tab line 14, there was an error for language - should have been subheadings, so discussing the language on that. Process to validate accessibility claims...where did we leave that? Subtitle area, so no language associated, just title 15:17:30 jeff: left off trying to align on the language in line 15. started editing the line and boiled it down in assessment tool. Ended up proof of a11y testing as proposed language to go in both 15:17:39 jeff: everyone ok with that today? 15:19:01 yes 15:19:40 jeff: 15 - use what's in assessment tool. proof of a11y testing. in discussion last week do we really need to say manual and automatic? what was in the doc was too much. 15:19:50 jeff: so we're going to use this one? OK 15:21:01 jeff: line 16, we had different language, dev lifecycle criteria integration and dev reviews. Then reviews of d3v lifecycle a11y...really saying contract language has specific lang for how to handle development. Typically, a review at every checkpoint to make sure a11y work is being done. Just a difference of language there 15:21:30 Neha4: doc lang makes more sense, review both things, lifecycle and development. in assessment tool, just mentioning dev reviews not lifecycle. so doc makes more sense 15:21:48 jeff: in doc, added in procurement checkpoints...maybe that's it? 15:21:53 Fazio: yeah 15:22:46 jeff: if you're ok with it, we can move procurement checkpoint lang from line 20 to replace lang in line 16. delete line 20 15:23:24 CharlesL: mark as reference instead of delete 15:24:03 jeff: next one is the same- warranties and remedies includes a11y. I think in the one in the assessment tool is fine. This is line 17 15:24:07 CharlesL: agree 15:25:20 jeff: next two are identical. No work. Line 20 will go away. So a11y in procurement program management, all line items covered, just diff language. 15:25:30 Fazio: do we just say program is evaluated for a11y? 15:27:06 jeff: would like to give a little more direction 15:27:49 jeff :program management is sub topic heading, within that process and policies, lifecycle of contracts, metrics, and defined process for addressing complaints 15:28:00 Fazio: itemizing instead of being broad 15:28:35 jeff: ok with the new language? 15:28:50 jeff: processes and polices evaluated for a11y integration 15:28:54 agreed 15:29:27 jeff: next line, the word a11y isnt' in there anywhere. add "for a11y" at the end 15:29:54 CharlesL: maybe just includes a11y? 15:30:21 jeff: contract lifecycle management includes a11y...requirements or criteria? what do you think? 15:30:26 jeff: requirements 15:30:28 agreed 15:30:57 jeff: procurement related dash a11y metric - i like what's in the doc. 15:30:58 agreed 15:31:22 jeff: defined process for identifying a11y complaints..or issue management process for a11y...I could go either way 15:31:27 CharlesL: I like the doc 15:31:34 Neha4: i like the doc version 15:32:05 jeff: going to change it a little bit and add a11y in there. issues complaints? 15:32:20 Fazio: is someone saying procurement process isn't accessible? or a11y information isn't in it? 15:32:54 jeff: when you buy something and you deploy, and there's an issue, has to go abck to vendor for remediation 15:33:06 CharlesL: something in contract needs to have info about how to raise with the vendor. 15:33:20 jeff: where is it and how does it get tracked. all those things 15:33:33 Fazio: do we add "with the vendor" in there 15:35:27 Fazio: should we say warranty includes...remediating complaints? 15:36:15 jeff: remedy could be a lot of things. this is really more on individuals...complaining about issues/problems. maybe need to put the word "users" in here somehow 15:36:31 ...defined process for identifying user a11y complaints 15:38:14 jeff: you as the owner of what gets deployed needs to have a process for documenting, remediating, communicating to the vendor... 15:38:31 Fazio: i think what's missing is coordinating with the vendor, not internally 15:38:39 jeff: will add with vendor 15:39:20 jeff: that's it, the bottom one is standard lang for dimensions, goals, metrics. Need to add procurement training one in. 15:39:32 fazio: last tab - culture? 15:40:11 jeff: don't worry abotu line 8- it's a dup. line 9 - i like what's in assessment tool for wording. 15:40:15 CharlesL: agreed 15:41:40 jeff: use assessment language 15:42:12 jeff: next one, business strategy and a11y as market differentiator. I like what's in the assessment tool for this one. 15:42:34 jeff: asking about promotion a little prescriptive. 15:42:41 CharlesL: delete completely? 15:42:59 Fazio: or rephrase...a11y part of business strategy? Telling them how is not what we should do 15:43:18 CharlesL: remove market differentiator. 15:43:42 Fazio: digital a11y is included in business strategy. 15:44:35 jeff: digital a11y for disability inclusion included in core values...i like whats's in the tool better. 15:44:52 Fazio: can't we say digital a11y is included in core values? 15:45:58 jeff :digital a11y included in code of conduct... 15:46:04 Fazio: can you do that? 15:46:28 janina: you can, i think w3c has it as an example in theirs 15:46:38 jeff: start with code of conduct or digital a11y? 15:46:53 jeff: to be consistent, use assessment tool version 15:47:09 jeff: disability focus in DEI activities. 15:47:19 Fazio: we gotta reword that one 15:48:04 janina: it's not in w3c code of conduct (going back to prior line item) 15:48:40 Fazio: take out DEI line item 15:49:04 jeff: community of practice line - for consistency should stay in and use assessment tool language. 15:50:27 Fazio: we might need this word in the glossary/key terms. Ok it's in there 15:50:45 jeff: use assessment tool lang? 15:50:47 agreed 15:51:31 pick up line item 15 in culture. Highlighted in red for next time 15:52:20 Fazio: need to talk about some github issues. next week might be a short meeting. When janina is back discuss publishing, then maybe take a break. 15:53:58 zakim, end meeting 15:53:58 As of this point the attendees have been Fazio, janina, CharlesL, jkline, stacey 15:54:00 RRSAgent, please draft minutes 15:54:01 I have made the request to generate https://www.w3.org/2025/04/30-maturity-minutes.html Zakim 15:54:08 I am happy to have been of service, stacey; please remember to excuse RRSAgent. Goodbye 15:54:08 Zakim has left #maturity 15:54:20 present+ 19:06:06 CharlesL has left #maturity