– DRAFT –
Maturity Model

Task Force CFC Update

janina: Have to wait for the end of this voting period, if we are going to make a change.

<janina> https://www.w3.org/WAI/APA/task-forces/maturity-model/work-statement

Fazio: Looks good

janina: It's an illustrative list and not an exhaustive list
… nothing will happen until 3 Feb anyway
… more procedural news:
… APA Charter has its own CFC next week, please vote
… Tracker is being sunsetted, actions will be tracked in future via Github

Sheri_BH: Many organizations are using it in 'stealth' mode

Intersection of Equity SubGroup and Maturity Model

Sheri_BH: Bruce and Tzviya have asked for meetings with Sheri for clarifications in applying the AMM to their respective organizations

janina: The AMM allows organizations to make claims

Fazio: As long as they are doing something, and whatever is asserted can be backed up with evidence
… showcasing your process internally and externally

Sheri_BH: Equity subgroup wants to investigate the possibility of adding to the AMM an Equity dimension
… Equity refers to all things beyond a11y: gender, lgbtq, everything in the traditional DEI

janina: This can be covered in a footnote
… what would we say differently to what AMM already says, namely that it is extensible and can be used in other areas

Sheri_BH: We do state that this AMM is devoted to A11Y
… we could meet with them and demonstrate how the model can we applied to their purposes

Sheri_BH: They are discussing applying to become a WG, perhaps opening a CG

Sheri_BH: The choices are [1] Go ahead on your own [2] we work with you on the intersections [3] we include Equity in AMM

janina: for [2], I would want it demonstrated how making changes in the AMM makes it more extensible

Fazio: We see many applications in MedTech, FinTech, AI. It is adaptable as it is

Sheri_BH: I can review AMM through the lens of Equity, and see how it looks

janina: +1 to that

Draft RESOLUTION: AMM decides to remain focused on accessibility and extensibility

+1

<nadine> +1

<janina> +1

<CharlesL> +1

<Sheri_BH> +1

<Fazio> +1

RESOLUTION: AMM decides to remain focused on accessibility and extensibility

<Sheri_BH> Sheri: Tzviya's issue to be assigned to sheri, Sheri to review AMM through the lens of Equity and extensibility , and propose any additions/changes

Prioritizing Jason White’s Issues, Recap of Last Week’s Meeting

<Sheri_BH> Janina: proposes to have a conversation with Jason to settle his concerns

<Sheri_BH> David: ISO compatibility is a separate issue

<Sheri_BH> Janina: will ask Jason for specifics on ISO

<Sheri_BH> David: Jason's smaller issues can be addressed quickly

Github Issue #42 Section 3.1 (communication) should be clarified.

<Fazio> w3c/maturity-model#42

<Sheri_BH> w3c/maturity-model#42

<Sheri_BH> David: reviewed the specifics of this issue

<Sheri_BH> Sheri: We deliberately decided not to include details about what goes in an accessibility statement

<Sheri_BH> Janina: We can't be very specific because different countries have different approaches

<Sheri_BH> Janina: if MM becomes part of WCAG 3, specifics will also be a problem

<Sheri_BH> Janina: We aren't a specification, we are best practices

<Sheri_BH> Brian: There is a waterfall effect on statements when they come from executives

<Sheri_BH> Janina: Will ask Jason to break it down into multiple issues

<Sheri_BH> David to also add the same comment into 42

<Sheri_BH> David: and also close it

Github Issue#15 Potentially unfamiliar terms/abbreviations in section 3 should be defined/explained.

<Sheri_BH> w3c/maturity-model#15

<Sheri_BH> We added a section called "Key Terms" after Jason logged this issue

<Sheri_BH> David will ask Jason to identify any terms that are missing and close the issue

Github Issue#17 The application of the model to decentralized organizations could be clarified, as could the nature and roles of the valid outputs of applying the model in an evaluation.

<Sheri_BH> w3c/maturity-model#17

<Sheri_BH> David: reviewed the specifics of this issue

<Sheri_BH> Sheri: We discussed this at some depth. The end result was that we added language saying that you could constrain the scope of the review as long as that constraint was identified

<Sheri_BH> Brian: Is currently implementing the MM in a decentralized org

<Sheri_BH> Brian: Determined that there was flexibility to do the review at a business unit level

<Sheri_BH> Brian: The question is whether the reviews at the business unit level can be rolled up into a corporate level assessment

<Sheri_BH> Brian: Key takeaway is how do you reflect an overall corporate score if you have some parts of the org that are more mature than others

<Sheri_BH> Brian: Are you strongest as your weakest link or strongest link

<Sheri_BH> David: Brian will come back with a proposal to handle this issue

<Sheri_BH> Janina: Sheri should take this up with the stealth implementers that she is meeting wtih

<Sheri_BH> David will assign 15 to Brian offline

since 08:30 PST