Re: Draft language about customization

“W3C” keeps getting removed by WAI. For now, we’re omitting it.
From: Stacey Swinehart <stacey.swinehart@gmail.com>
Date: Saturday, September 27, 2025 at 5:24 AM
To: Jeff Kline <jeffrey.l.kline@gmail.com>
Cc: Sheri Byrne-Haber <sheri@sheribyrne.com>, Maturity Model TF <public-maturity@w3.org>
Subject: Re: Draft language about customization
Agree with Jeff's comments. :)

One typo: retains should be retain

"This customization allows users to
retains the exact structure of dimensions, maturity levels..."


Cheers!
Stacey


sent from my phone

On Fri, Sep 26, 2025, 1:03 AM Jeff Kline <jeffrey.l.kline@gmail.com<mailto:jeffrey.l.kline@gmail.com>> wrote:
Sheri,

Looks great.

As far as placement in the document, I think you meant it to go in the Introduction given the heading number you included, correct? If so, its  certainly appropriate  there.

On a slightly different note, is it now being “officially” referred by the W3C as  W3C Accessibility Maturity Model (W3C AMM)? If so we should consider making that global update.

I also had a couple of small, proposed edits. Feel free to use if you see fit.  See below in RED.

Thank you for writing it all up!

Regards,


[A picture containing text, black, clock    Description automatically generated]<http://strategicaccessibility.com/>
 Jeff@strategicaccessibility.com<mailto:Jeff@strategicaccessibility.com>
 5  1  2   .   4  2  6   .   9   7  7  9

From: Sheri Byrne-Haber <sheri@sheribyrne.com<mailto:sheri@sheribyrne.com>>
Date: Thursday, September 25, 2025 at 9:20 PM
To: public-maturity@w3.org<mailto:public-maturity@w3.org> <public-maturity@w3.org<mailto:public-maturity@w3.org>>
Subject: Draft language about customization

I am proposing to add this subsection to the abstract, but am open to
other locations.  Also open to language modifications. I think the below
strikes a decent balance of informative yet concise.

Sheri


1.1.1 Customizing the Maturity Model

The AMM may be customized by the organization performing the
accessibility maturity assessment.  This customization allows users to
retains the exact structure of dimensions, maturity levels, and
progression logic, while making the model application more concise and
targeted tailored to the needs of the organization. Some examples of AMM customizations include:

1) Omitting proof points (or portions of proof points) that do not apply
to the organization, such as references to mobile apps if the
organization does not have one.

2) Renaming terms to better fit your industry, for example, changing
“proof points” to “evidence,” “ICT” to “Hardware and Software,” or
“ACR/VPAT” to “accessibility certification documents.”

3) Refining wording within proof points and dimensions so they reflect
the terms and practices used in your organization, such as replacing
“contract language for ICT procurement” with “accessibility clauses in
vendor agreements.”

These updates make AMM application more relevant and actionable to an organization , while keeping it aligned with the W3C framework. We recommend keeping a list of such changes so that if the results of the maturity model assessment are provided to a third party, they can understand what updates were made.