W3C

– DRAFT –
Maturity Model Task Force

08 July 2026

Attendees

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

Meeting minutes

agenda

New Business

sustainibility group meeting update

Sheri_B-H: sneek peak into the document that they are preparing

Sheri_B-H: Equity model where they 7 dimension

<Sheri_B-H> accessibility, internationalization, privacy, security, sustainable web, and web performance

Sheri_B-H: accessbility contains our model + equity

Sheri_B-H: nothing is contradictory to our model

janina: Only one point to note they are not a working group

Fazio: There can be a competition between maturity models from different groups

janina: If anyone wants to join that group can be

Continue with GitHub Issues 328 & 334: Abstract & About Section Definitions

Mark_Miller: does anyone have any additional comments for structural changes that we disucssed last week?

JeffAdams-UN: we are done with section 1.3 and now we will check the language that is revised by Sheri_B-H

<CharlesL> Looks good to me.

Sheri_B-H: Nobody has objected

<Sheri_B-H> §1.3 Extending the Accessibility Maturity Model

<Sheri_B-H> Purpose. This section describes how organizations may extend the AMM to reflect their industry and operational context while preserving its underlying framework.

<Sheri_B-H> Extending means adding to the AMM. Two forms of extension are supported:

<Sheri_B-H> Adding new dimensions, such as sustainability, and 

<Sheri_B-H> Adding new proof points, such as localization under the Communications dimension.

<Sheri_B-H> Extensions supplement the standard content; they never replace it.

<Sheri_B-H> Several common AMM adaptations are not considered extensions. 

<Sheri_B-H> Choosing to assess only certain dimensions, for example the ICT dimension on its own, is a scoping decision rather than an extension. 

<Sheri_B-H> Where content does not apply, such as the PDF proof points for an organization that produces no PDF files, mark it “not applicable” rather than deleting it. 

<Sheri_B-H> Adjusting terminology to match organizational language, for example, using the phrasing “financial forecast” instead of “budget,” within a proof point is an acceptable wording change, not an extension.

<Sheri_B-H> The original framework itself must stay intact. For extensions, the same four maturity levels and progression logic must be utilized. 

<Sheri_B-H> Organizations must maintain records of any extensions and terminology changes to support third-party sharing and auditability.

CharlesL: what is the intension of this?

Fazio: This is what we are going to change

Sheri_B-H: I am ready to hand this off and done with it

JeffAdams-UN: that makes complete sense to me and not let Claude touch it now

Sheri_B-H: Is there any of frequent flyers who will be benefitted from this?

janina: I can not recall this as an issue

Shall we add this to issues mentioned to make sure we are using this language

<Sheri_B-H> General consensus was no, we don't want to do this piecemeal.

Moving to next section 1.4

JeffAdams-UN: Reading the proposed language for the section

Fazio: This is talking about the content more and scope part

JeffAdams-UN: Covering Issue 334

<Fazio> 1.2 Audience for the Accessibility Maturity Model

<Fazio> This document is intended to guide and evaluate the levels of organizational accessibility maturity in a public or private sector organization at any scale.

<Fazio> The audience for this maturity model includes:

<Fazio> executive levels of an organization’s leadership

janina: Little hesitant - I am missing the object, people in the organization who will be working for AMM

<Fazio> other levels of management responsible for accessibility maturity

<Fazio> policy and business process subject matter experts who are responsible for putting plans, actions, metrics, and governance in place.

JeffAdams-UN: need to check this language with other paret of the about section

CharlesL: how I would approach - what we should do is before and after analysis - current 1.4 - what we want to change and feed it to LLM

Fazio: Yes that is a good idea

CharlesL: We can also mention issue part and add that this is what is added

<Dr_Keith> Do not rewrite, rephrase, or change the voice of my text. Only correct exact spelling or grammatical errors, and keep my original sentence and vocabulary in tact

Mark_Miller: Initial prompt should be what you see and ask what change is required and then discuss this in the group rather than changing the language

We are meeting on 22nd July

No meeting next week because of ICCHP

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

Diagnostics

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

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