W3C

– DRAFT –
Maturity Model Task Force

17 June 2026

Attendees

Present
CharlesL, Crispy, Dr_Keith, janina, jkline, Mark_Miller, Neha, Sheri_B-H, SusiPallero
Regrets
Jeff Adams, Stacey Swineheart
Chair
David Fazio
Scribe
Crispy

Meeting minutes

New Business

MM CSUN session to be repeated for ICCHP in Czech Republic

David to be doing a session on Learning management systems

Date of Conf July 16-17th

jkline - created a whitepaper on MM and W3C version superiority, posted on LI for access download

It's out there, go take a look

David, can you post a direct link for us, and to put in the minutes?

jkline - doesn't have a link at present

Go to LI

Github Issue #323 Review Suggested Language to Strengthen Procurement Dimension

<Sheri_B-H> Here are the three concepts

<Sheri_B-H> 1) Jeff's language

<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

<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

<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.

<Sheri_B-H> 2) not sure where this came from, think it is existing language?

<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

<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.

<Sheri_B-H> 3) missing concepts identified by Sheri

<Sheri_B-H> and reduce the need for accommodations and increase disabled employment which will make accessibility throughout the organization easier

<Sheri_B-H> Here is what I came up with:

<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.

<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

<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

<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.

Sheri - above is pasted from Sheri's email sent around last week

Can be broken into 2 paragraphs maybe?

Janina - suggesting a slight amendment to the arrangement

<Dr_Keith> I'd recommend removing the "Therefore" in "Therefore, accessibility criteria must be integrated as an essential consideration of procurement processes, contract language..."

<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.

<Sheri_B-H> plus change IT to ICT

<Dr_Keith> +1

<Crispy> +1

<Sheri_B-H> and break into two paragraphs

<Mark_Miller> +1

jkline - questions the use of "solicitation"

Responded to by David and Sheri

<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

<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

<Sheri_B-H> inaccessible ICT deliverables.

<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

<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.

Final Para from Sheri with feedback

David to message Judy with the above

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

Mark - Started How to Use the MM last week but got side tracked.

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.

David - Mentioned that we do not specificy what someone should use, who to use for audit for example

Mark - agrees with idea of examples to help use of the MM

jkline - can we have a resources page

David - we have a wiki for anything to do with the taskforce

jkline - from the starts we tried making sure not to tell ppl how to do things

David agrees, and that we can use proof points

Susi - Add suggested info to wiki

David agrees

jkline - would we want to reference the wiki?

David sees no issue

<SusiPallero> ack

we will wait until it starts getting populated

Discussion of being careful whats put in the wiki

Janina - Wiki is for help towards what we need to do - collect resources there.

David - please submit case studies, etc for the wiki. Please add resources

<Fazio> Crispy using MM at Toyota

Github Issue #323 Review Suggested Language to Strengthen Procurement Dimension

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

Mark - Define what the sections should be like

Wflow for applying the MM, recording findings that can be used at each step

assessment spreadsheet and workflow

operational roles that apply during use

A worked example

Recommended practices

the 5 bullet points in scope

Janina - Spreadsheet cannot go in the narrative

Mark - it was from the AI, not to be used

David - David and Sheri originally wrote this

Sheri - Should be interesting to see the Claude update

<Mark_Miller> • A short document map orienting the reader to what's in §2, §3, and §2.4 (the assessment spreadsheet).

<Mark_Miller> • An assessment workflow (scope → identify proof points → gather evidence → determine maturity level → record and act).

<Mark_Miller> • Operational rules pulled forward from §2 that apply during use: cumulative levels, Optimize-requires-full-completion, N/A handling.

<Mark_Miller> • A worked example (Communications dimension at Launch level).

<Mark_Miller> • Recommended practices (cross-functional review team, engaging people with disabilities, reassessing on a cadence).

<Mark_Miller> These are what AI suggested.

<janina> Look at: https://bit.ly/a11yedge for the graphic

Mark - Figure out placement as we go

Mark - start with Out of Scope next week

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

Diagnostics

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