W3C

– DRAFT –
Maturity Model Task Force

06 May 2026

Attendees

Present
CharlesL, Crispy, Fazio, janina, JeffAdams-UN, jkline, Mark_Miller, Sheri_B-H, SusiPallero
Regrets
-
Chair
David Fazio
Scribe
CharlesL

Meeting minutes

New Business

Sheri_B-H: New Book Published!

https://www.amazon.com/gp/product/1041018681/ref=ox_sc_act_title_1?smid=ATVPDKIKX0DER&psc=1
… published with T&F, which is GCA certified by Benetech

Follow Up with Mark and Jeff on Github Issues #328 #331

w3c/maturity-model#331

<gb> Issue 331 "Proof points" language unclear (by iadawn)

w3c/maturity-model#334

<gb> Issue 334 Improve the About section (by iadawn)

JeffAdams-UN: maybe we don't need an about section.
… we rewrote the abstract (Mark, Jeff and Claude AI)
… , we removed the about section, and we rewrote How to use the model.
… , I didn't not rewrite the customizing part as it looked in good order.

Mark_Miller: we did this illustratively. love the feedback,

Fazio: Where is this now?

Mark_Miller: emails back and forth.

JeffAdams-UN: we can put it in Google Docs.

Fazio: if you have it handy please share it with the group.

Mark_Miller: should we do a google Docs then?

Fazio: Yes, but there can be issues with Google Docs.

janina: I don't do Google Docs, I export it to Docs
… , anything in MarkDown I am good
… , change tracking is difficult. We should all re-read this.
… , lets not nit-pic only substantive changes / issues.

Fazio: two versions maybe one we can comment on and one maybe to read.

JeffAdams-UN: I will be curious if Janina if this works for you

https://www.notion.so/jeffadams/About-Abstract-Current-Draft-358a25b4c196800f883cf1974e4b15e6?source=copy_link
… , this is a Notion Doc that allows for suggestions / comments we will find out how accessible it is.
… , I will follow up with a Google Doc afterwards
… , Claude AI Desktop can connect with this and you tell what the AI can/cant do.
… , When we put it into GitHub, that we are treating 328 and 334 together, but be clear in the wording. We don't want the About / Abstract separately.

<SusiPallero> +1

<SusiPallero> got it

Fazio: Yes we can specify that multiple issues are tagged with a PR.

JeffAdams-UN: #345 repetition, I worked on this too.

w3c/maturity-model#345
… , I can put it directly into Github if you ant.
… , the how to evaluate sections.

<gb> Issue 345 Repetition in 'how to evaluate...' (by iadawn)

Fazio: yes send that to the group as well.

JeffAdams-UN: when I create a google doc for 328 / 334, I can also provide this 345 work as well.
… , it is a long revision.
… , will put it in a doc and will send it along

<SusiPallero> no

Charles: Correction: it is not 331 the github issue is 328.

w3c/maturity-model#328

<gb> Issue 328 Clarify what model can do in abstract (by iadawn)

Github Issue #335 Clarify impact on product deliver

w3c/maturity-model#335

<gb> Issue 335 Clarify impact on product deliver (by iadawn)

Fazio: Issue: The AMM covers the accessibility of the organisational environment but hints that it is important for delivery of accessible products - these are two different things but this is not clear.

jeffK: The MM covers this some company uses products where others build products. I don't understand.

janina: If what he is asking for is unclear, or we need further information we can ask for clarification or suggestions.

Sheri_B-H: we went to lengths to avoid the word "inclusion" on purpose to avoid potential issues. i.e. support dimension.

janina: we are web focused.

Sheri_B-H: point to all the 2025 exec orders, we are trying to make this adoptable even from Gov. organizations.

Fazio: we are about everything going into the process not for creating the products which ISO addresses.
… , I will point out the differences from our model with ISOs.

JeffAdams-UN: same with Culture.

Mark_Miller: if we go back to what Janina says, lets ask for examples from him directly.
… , working on the organization and making that accessible. the inclusive of the org helps support creating a11y digital assets.
… , just lets have him explain further.

janina: Yes, we can do that.

Fazio: don't we want these part of the same, there is no value to separate it.

Mark_Miller: I would just say, "We are trying to address this issue, we still don't understand your point."

Sheri_B-H: We also had the deliberate choice to not include inclusion

JeffK: "This maturity model takes a holistic approach"

Mark_Miller: "We don't understand your issue"

<Fazio> comment to issue #335 We have discussed this issue at length on 05/06/2026. We believe that an accessible environment and accessible product development are one and the same, and would like to better understand the distinction that you see in separating them.

Minutes manually created (not a transcript), formatted by scribe.perl version 248 (Mon Oct 27 20:04:16 2025 UTC).

Diagnostics

Succeeded: s/inclusivity/not include inclusion

Succeeded: s/KIS//

Maybe present: Charles, jeffK

All speakers: Charles, Fazio, janina, JeffAdams-UN, jeffK, Mark_Miller, Sheri_B-H

Active on IRC: CharlesL, Crispy, Fazio, janina, JeffAdams-UN, jkline, Mark_Miller, Sheri_B-H, SusiPallero