Meeting minutes
<gb> /issues/52 -> #52
<gb> /issues/129 -> #129
<gb> /issues/155 -> #155
<gb> /issues/45 -> #45
<stacey> FYI I'm having issues connecting to the call. Also I need to drop at the half hour mark. Happy to be back with all of you!
<gb> /issues/129 -> #129
<gb> /issues/155 -> #155
<gb> /issues/52 -> #52
<jkline> before i get dropped as usual!
<Dr_Keith> do people need the link: https://
<Fazio> anyone else joining zom?
New Business
<jkline> again
Maturity Model at TPAC
<Fazio> TPAC Proposed Maturity Model Task Force Agenda:Is the APA AMM ready for publication? Why?
<Fazio> Is the APA AMM NOT ready for publication? Why?
<Fazio> Are our approaches sufficiently coordinated? How do we do better?
<Fazio> Is the Equity CG a snapshot of APA AMM? At what point? How maintaining synchronization?
<Fazio> Has Equity (others) discovered an incompatability to the APA AMM that requires resolution?
<SusiPallero> +1 to agenda for TPAC
ISSUE: reword Equity agenda item for clarity and purpose.
<gb> Sorry, I don't know what repository to use.
Github Issue GitHub Issue #155 Section 3.4: maturity also depends on how effective the ICT development processes are in producing accessible ICT. - Update
<gb> /issues/155 -> #155
<Fazio> Jeff has proposed updated language, accepted by filer, and made edits to the Spreadsheet. Edits to Maturity Model document are still needed, once TF approves language
<Fazio> Issue 155 proposed change: new subtopic labeled "Dimension Goals and Metrics" to each dimension with a singe proof point underneath that says:
<Fazio> "Dimension related goals established, metrics defined, and progress tracked" and will add to all worksheet tabs with concurrence
RESOLUTION: language approved
General approval
<SusiPallero> Sorry I can't unmute because there's a lot of noise here. This is a detail but still important. In our page in the "Internal resources needed to implement the maturity model at your organization" section, there is a table and it says Y and N. When you translate it automatically into spanish Ns are read as "North". I think we should use the word
<SusiPallero> instead of just the letter "Y" or "N".
ISSUE: Susi to add GitHub issue to address Y and N in tables, review section 4.1 and if still needed, use Yes and No instead of abbreviations
<gb> Sorry, I don't know what repository to use.
<Fazio> Susi will create Git issue for this
GitHub Issue #129 Conflict in position Training Knowledge and Skills Vs. DLC
<gb> /issues/129 -> #129
ACTION: Susi to add GitHub issue to address Y and N in tables, review section 4.1 and if still needed, use Yes and No instead of abbreviations
<gb> Sorry, I don't know what repository to use.
<Fazio> Proposed response: Training proof points have been added to each dimension. We believe the latest Editors Draft addresses this concern. If you still find an issue with it, please file a new GitHub Issue.
<SusiPallero> +1
<JXZ> +1
RESOLUTION: closing issue with proposed response
GitHub Issue #52 Section 2 (and elsewhere, if necessary): broaden the range of standards relevant to the maturity model.
<gb> /issues/52 -> #52
<Fazio> Please take a look at the latest Editors Draft. We believe we have addressed this issue. We call your attention to section 1.1 and 1.3: The Accessibility Maturity Model has been developed using research of existing maturity models and standards outside of WCAG. For example,
<Fazio> ISO/IEC 30071-1:2019 Information Technology - Development Of User Interface Accessibility - Part 1: Code Of Practice For Creating Accessible ICT Products And Services
<Fazio> This ISO standard includes specifics to the incorporation of accessibility practices into the design and development process. This is orthogonal to the Accessibility Maturity Model which provides a way to assess an organization's accessibility maturity in dimensions beyond the design and development process. Adherence to ISO 30071-1:2019 could be
<Fazio> used as a proof point for the maturity of the ICT Development Lifecycle dimension.
<Fazio> Please, let us know if you agree and we can close this issue?
RESOLUTION: closing issue with proposed response