– DRAFT –
Maturity Model Task Force

<gb> /issues/193 -> #193

<gb> /issues/228 -> #228

New Business

Github Issue ##226 Add an explanatory section on dimension goals and metrics

jkline Donated text from my book.

<Fazio> w3c/maturity-model#226

<gb> Issue 226 Add an explanatory section on dimension goals and metrics (by jasonjgw)

<jkline> Attached is some proposed language that can addresses this issue. It could be added to the Introduction section, but could also be located somewhere else in the document as appropriate. The language is taken from the book referenced below, and modified for use in the MM document. It is intended to provide general information, and is not specific to

<jkline> MM proof points or dimensions, but rather to provide examples and ideas for areas that need goals and metrics to drive progress.

<jkline> ESTABLISHING METRICS AND TRACKING PROGRESS

<jkline> Content derived from Chapter 8.1.6 of Strategic IT Accessibility: Enabling the

<jkline> Organization – 2nd Edition by Jeff Kline

<jkline> An important approach to reaching full accessibility maturity is establishing goals and measuring

<jkline> progress of the organization’s accessibility initiative.

<jkline> Developing short term and long-term goals is a meaningful and realistic approach to achieve accessibility maturity .

<jkline> Setting short-term goals is important and can be strategic or tactical, and may be indirectly related to achieving digital accessibility compliance. Some examples are but not limited to:

<jkline> • Completion of general accessibility awareness training by 50 percent of staff within eight months, and 100 percent within sixteen months

<jkline> • Completion of accessibility training by all project programmers within six months

<jkline> • Establishment of a baseline of accessibility for the organization’s external website

<jkline> • Exploration and selection of web scan tools for regular scanning of internal and external websites

<jkline> • Appointment of accessibility focal points for all necessary units and subunits

<jkline> These examples are related to organizational enablement more than actual compliance but have a long-term impact. Progress can be easily tracked and measured by using metrics such as deadlines for completion as the end goal.

<jkline> Long-term goals should be focused on measuring actual progress in making your organization’s IT accessible. Goals should established and agreed upon by the various stakeholder organizations to ensure consensus. The goals for various stakeholder organizations would customized based on the nature of their work, but common elements remain:

<jkline> • establishing goals for various areas

<jkline> • measuring progress toward meeting them over time

<jkline> • reporting the results at regular intervals (quarterly, annually, etc.)

<jkline> Some examples of metrics for long-range accessibility goals are but not limited to:

<jkline> • Percentage of Internet pages with accessibility errors

<jkline> • Percentage of intranet pages with accessibility errors

<jkline> • Percentage of procured IT products and services for internal use that are accessible

<jkline> • Number of noncompliance exceptions created

Sheri_B-H, Can take a pass at consolidating the language.

jkline, Where do we want to put the language?

Github Issue #228 Syncing proof points in the MM document and the assessment tool

<gb> /issues/228 -> #228

Sheri_B-H, Jeff to decide where it goes.

Reviewing Spreadsheet

<Sheri_B-H> https://www.w3.org/WAI/GL/task-forces/coga/wiki/Coga_terms_langauge_guide

<JennE3> https://www.plainlanguage.gov/ (as you want to trust or not)

<jxz> +1 to COGA's document as the reference

<CharlesL> consider a new Proof Point in Support: Incorporate an accessible way of responding to employee feedback which provides status updates and decisions.