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

Received on Thursday, 25 September 2025 19:20:04 UTC