Meeting minutes
<Fazio> meeting Maturity Model Task Force
<gb> /issues/227 -> #227
<gb> /issues/228 -> #228
New Business
Fazio News from W3C – will have a publication moratorium.
Fazio News from W3C – will have a publication moratorium in April
Publication Preparation
Janian They happen. Nothing to worry about.
Janina They happen. Nothing to worry about.
<gb> /issues/228 -> #228
janina Nothing for prep of publication
<Fazio> zakim next item
Github Issue #228 Determine if the proof points in the MM document and the assessment tool should be synced
Publication Preparation
<gb> /issues/227 -> #227
<Fazio> 1.0 APA Note: Accessibility Maturity Model
<Fazio> The Accessible Platform Architectures (APA) Maturity Model Task Force (MMTF) welcomes feedback on the updated 1.0 version of the W3C Group Note: Accessibility Maturity Model. The Accessibility Maturity Model (AMM) describes an overall framework for establishing a robust ICT accessibility program and identifying areas for improvement. The
<Fazio> Accessibility Maturity Model is a tool that:
<Fazio> Assesses the current effectiveness and capabilities of an entire organization or subunits within the organization
<Fazio> Supports identification of gaps between the current capabilities and the next level of accessibility maturity
<Fazio> Supports plans for next steps to improve the organization's accessibility performance over time
<Fazio> The approaches identified in this note are intended to influence organizational programs and advance accessibility focus from making a product or website accessible to creating an environment where the entire product experience can be kept accessible over time. This evolution towards proactive accessibility is relevant to all parts of an
<Fazio> organization that contributes directly or indirectly to developing a product experience.
<Fazio> The MMTF will continue to develop and refine this note. Comments are welcome at any time. We especially encourage comments by organizations implementing the model.
fazio End of paragraph: Stop at “…Kept accessible over time.”
fazio Convey every aspect of an org is accessible but not sure how.
Kline Struggle with idea of product experience… it’s really digital assets.
<CharlesL> w3c/
<gb> Issue 227 Add a Human Readable Change Log (by clapierre)
<Fazio> https://
Fazio Referring to a product is the issue
<Dr_Keith> This evolution towards proactive accessibility is relevant to all parts of an organization that contributes directly or indirectly to influencing organizational maturity.
Kline suggests: This evolution towards proactive accessibility is relevant to all parts of an organization that contribute directly or indirectly to the accessibility of its digital assets.
<Dr_Keith> This evolution towards proactive accessibility is relevant to all parts of an organization that contributes directly or indirectly to influencing digital accessibility maturity.
<janina> https://
<Dr_Keith> full suggestion: The approaches identified in this note are intended to influence organizational programs and advance accessibility focus from making a product or website accessible to creating an environment in which organizational maturity specific to digital accessibility may be measured and evaluated over time. This evolution towards
<Dr_Keith> proactive accessibility is relevant to all parts of an organization that contributes directly or indirectly to influencing digital accessibility maturity.
<jkline> I need to bounce. Have fun!
fazio Need to phrase it in a way everyone can understand.
<Dr_Keith> The approaches identified in this note are intended to influence organizational programs and advance accessibility focus from making digital assets and services accessible to creating an environment in which organizational maturity, specific to digital accessibility, may be measured and evaluated over time. This evolution towards proactive
<Dr_Keith> accessibility is relevant to all parts of an organization that contributes directly or indirectly to influencing digital accessibility maturity.
<CharlesL> Suggested: The approaches identified in this note are intended to influence organizational programs and advance accessibility focus from making digital assets accessible to creating an environment in which organizational maturity specific to digital accessibility may be measured and evaluated over time. This evolution towards proactive accessibility is relevant to all parts of an organization that contribute directly or indirectly to
<CharlesL> influencing digital accessibility maturity.
<CharlesL> The approaches identified in this note are intended to influence organizational programs and advance accessibility focus from making digital assets and services accessible to creating an environment in which organizational maturity, specific to digital accessibility, may be measured and evaluated over time. This evolution towards proactive accessibility is relevant to all parts of an organization that contribute directly or indirectly
<CharlesL> to influencing digital accessibility maturity.
RESOLUTION: The approaches identified in this note are intended to influence organizational programs and advance accessibility focus from making digital assets and services accessible to creating an environment in which organizational maturity, specific to digital accessibility, may be measured and evaluated over time. This evolution towards
<Fazio> proactive accessibility is relevant to all parts of an organization that contribute directly or indirectly influencing digital accessibility maturity.
RESOLUTION: The approaches identified in this note are intended to influence organizational programs and advance accessibility focus from making digital assets and services accessible to creating an environment in which organizational maturity, specific to digital accessibility, may be measured and evaluated over time. This evolution towards
proactive accessibility is relevant to all parts of an organization that contribute directly or indirectly influencing digital accessibility maturity.
Github Issue #228 Determine if the proof points in the MM document and the assessment tool should be synced
<gb> /issues/228 -> #228
<gb> /issues/227 -> #227
CharlesL to Add change log in the appendix after first public release.