Meeting minutes
scribe
<Sheri_B-H> presenet+
New Business
Fazio: TPAC invited expert fund is not open and ready for applications. It was sent via W3C list, but David can send out if anyone needs it.
correction: fund is NOW open
@fazio: Jania, David, Susie will be on maturity model panel at ICCHP. David will also have another panel, and show learning management system.
<gb> @fazio
@neha: In India Neha has started non profit organization and converting books into accessible format for blind and low vision children.
<gb> @neha
<Neha> https://
@Neha: It includes making STEM content accessible.
<gb> @Neha
Sheri_B-H: Communication from Jennifer to sync up with this group on work their doing on the equity maturity model. Will invite her as a guest to an AMM meeting.
Github Issue #323 Strengthen Procurement Dimension - Review issuer comments.
<gb> Issue 323 Strengthen motivation for procurement language (by judbrew) [Editorial]
<Fazio> David, thank you for checking. This response only minimally addresses the point that I was raising; it addresses it only within the context of a single organization, or other individual organizations that might be influenced by a single organization that uses its procurement policies strategically. It does not capture the strength of coordinated
<Fazio> procurement policies that selectively purchase accessibility-supporting software and apps instead of apps that continue to perpetuate accessibility barriers in the process of creating websites, apps, and content. What is your timeline for resolving comments on the latest version of the maturity model? It would be helpful if I could look at the
<Fazio> updated draft, to ensure that I am proposing language harmonized with your current document—but I would appreciate the opportunity to propose a modified version of this language for your consideration, to try to better capture the point that I feel is still missing in this. (Difficult today, but possible over the coming weekend.)On Jun 17, 2026,
<Fazio> at 11:21 AM, David Fazio ***@***.***> wrote:Helixopp left a comment (w3c/maturity-model#323)
<Fazio> @judbrew here is what we came up with to address this issue. Please, let us know if this satisfies your request:
<Fazio> 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
<Fazio> 08:18 <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.
<gb> @judbrew
<Fazio> —Reply to this email directly, view it on GitHub, or unsubscribe.Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!
<Fazio> You are receiving this because you were mentioned.Message ID: ***@***.***>
Fazio: Once we have an updates to the document we can reach out to Jennifer to share her proposed language.
ack
janina: Could be better to ask for proposed language now
<Fazio> Proposed response: Thank you, Judy. We have made decisions regarding other sections of the document, as we work through Github Issues, that are not yet reflected in the Editors Draft. However, we do not believe that any of those changes will fundamentally alter anything related to Procurement.
<Fazio> We would appreciate your proposed language anytime. Please, take into consideration that this non-normative document focuses on "the what" not the "why" or "how".
<Fazio> comment sent
Continue with GitHub Issues 328 & 334: Abstract & About Section Definitions
Starting @ §1.2 How to Use the Accessibility Maturity Model - Out of Scope
Fazio - What is the graphic used for?
JeffAdams-UN - Graphic assessment of the workflow
Fazio yes
Fazio 2 graphics: 1. Assessment Workflow 2. Document Map
Fazio Graphic placement later
JeffAdams-UN: Moving to: §1.3 Customizing the Accessibility Maturity Model
Mark_Miller0 ack
Fazio put the framework in the wiki, then rewrite.
JeffAdams-UN - will finalize notes and send to public list for inclusion in Wiki
JeffAdams-UN move to: §1.4 Audience for the Accessibility Maturity Model
Sheri_B-H section 8.2 Internal Resources Needed... Should be referenced in the Audience section.
Fazio agrees
JeffAdams-UN: Clean up doc, vet with Mark, send final version to public list, make sure we're all good.
Fazio ... publish on the wiki, then update the model.
JeffAdams-UN working to possibly have by next meeting