- From: Stacey Swinehart <stacey.swinehart@gmail.com>
- Date: Mon, 24 Jul 2023 12:43:23 -0500
- To: Jeff Kline <jeffrey.l.kline@gmail.com>
- Cc: Charles LaPierre <charlesl@benetech.org>, Lionel Wolberger <lionel@userway.org>, Maturity Model TF <public-maturity@w3.org>, Sheri Byrne Haber <sbyrnehaber@vmware.com>, David Fazio <dfazio@helixopp.com>, Janina Sajka <janina@rednote.net>
- Message-ID: <CADZgR=9uyEo+LNFpmbSQJzBt=aBE1SJ6+zB=B4xyzJPNzVSs1w@mail.gmail.com>
Hi! I have a few grammar tweaks for an easier read for the <jk> section. Also, for the second sentence...do you mean to say "organization's" (possessive singular) or "organizations'" (possessive plural)? I used the possessive singular for the moment: For some organizations, there may be proof points included in the model/template that may be viewed as not applicable. These proof points should be carefully analyzed to determine how/if they apply to the organization’s ability to reach full maturity. If the organization is confident that the proof point is not applicable, it can be marked as such by selecting “N/A” in the dropdown. Conversely, additional proof points can be added for any dimension by copying/pasting an existing proof point and editing the new proof point description. Thanks! ssg. On Mon, Jul 24, 2023 at 12:30 PM Jeff Kline <jeffrey.l.kline@gmail.com> wrote: > Team, please see below. > > > > I propose we include this information in Section 2.2 of the MM document. > See below encapsulated in <jk> <jk> > > > > 2.2 Proof Points > > Each dimensional outcome has a range of suggested proof points > <https://www.w3.org/TR/maturity-model/#dfn-proof-point>, which includes > any evidence or necessary measures that can be used to determine the > maturity of each dimension > <https://www.w3.org/TR/maturity-model/#dfn-dimension>. Progress towards > achieving maturity is attained by creating the proof points described for > each dimension. > > - Proof points are evidence-based, organizational deliverables which > indicate the maturity stage > <https://www.w3.org/TR/maturity-model/#dfn-maturity-stage>. > - Proof points are specific to the dimension being focused on. For > example, if only procurement maturity is being measured, only procurement > proof points should be evaluated. > - For some dimensions, proof points are further organized by category. > - Proof points can be partially completed at the Launch and Integrate > stages, but must be fully completed for the optimize stage. > > For example, if a dimension requires a plan to identify ICT accessibility > related skill levels and gaps, then the corresponding proof point would be > a document containing the evaluation of ICT accessibility related skill > levels and gaps. > > <jk> For some organizations, there may be proof points included in the > model / template that may be viewed as not applicable. A careful analysis > these proof points should be performed do determine how / if they apply to > the organizations ability to reach full maturity. If the organization is > confident that the proof point is truly not applicable, it can be marked as > such by selecting “N/A” in the dropdown. > > Conversely, additional proof points can be added for any dimension by > copying / pasting an existing proof point and editing the new proof point > description. <jk> > > > > One other comment… we might want to make the N/A dropdown available only > in the “inactive” stage. Including it in the other stages would imply that > it was applicable and being worked on and therefore applicable. > > > > > > Feedback welcome! > > > > > > > > Regards, > > > > > > [image: A picture containing text, black, clock Description automatically > generated] > > jeffrey.l.kline@gmail.com > > 5 1 2 . 4 2 6 . 9 7 7 9 > > > > *From: *Charles LaPierre <charlesl@benetech.org> > *Date: *Monday, July 24, 2023 at 9:23 AM > *To: *Jeff Kline <jeffrey.l.kline@gmail.com>, Lionel Wolberger < > lionel@userway.org>, Maturity Model TF <public-maturity@w3.org> > *Cc: *Sheri Byrne Haber <sbyrnehaber@vmware.com>, David Fazio < > dfazio@helixopp.com>, Janina Sajka <janina@rednote.net> > *Subject: *Re: New A11Y Maturity Template with Cover included > > Fair points Jeff, I agree and if you would like to draft something up we > can look at it during this week’s call. > > > > Thanks > > Charles > > EOM > > > > *From: *Jeff Kline <jeffrey.l.kline@gmail.com> > *Date: *Friday, July 21, 2023 at 5:21 PM > *To: *Charles LaPierre <charlesl@benetech.org>, Lionel Wolberger < > lionel@userway.org>, Maturity Model TF <public-maturity@w3.org> > *Cc: *Sheri Byrne Haber <sbyrnehaber@vmware.com>, David Fazio < > dfazio@helixopp.com>, Janina Sajka <janina@rednote.net> > *Subject: *Re: New A11Y Maturity Template with Cover included > > Hi Charles, > > > > I seem to recall discussions about an N/A option when we started creating > the spreadsheet. > > > > I was on the fence about it, as I felt like it would be too easy to mark > relevant proof points that way when in fact, they would be applicable. > > > > In the end, if they want to circumvent the intended and useful purpose of > the maturity model and worksheet, they would only be hurting their > organization’s maturity initiative. However, I do think that the escapes > would be fairly obvious to others familiar with organizational > accessibility criteria and the model, including knowledgeable people both > within or external to the organization, such as customers requesting > maturity information during procurements. > > > > Bottom line, I guess I’m OK with including it, as I do see it being useful > in situations where organizations, particularly smaller ones, that may not > actually do or have need to do some proof points. If we decide to proceed > with an N/A selection, I propose that we to add some instructions in the MM > document and the worksheet cautioning careful thought and consideration > before choosing to eliminate proof points with the “N/A” selection. > > > > If the group agrees, would be happy to draft something, or do it > collaboratively. > > > > My $.02 > > > > > > > > Regards, > > > > > > [image: A picture containing text, black, clock Description automatically > generated] > > jeffrey.l.kline@gmail.com > > 5 1 2 . 4 2 6 . 9 7 7 9 > > > > *From: *Charles LaPierre <charlesl@benetech.org> > *Date: *Friday, July 21, 2023 at 2:01 PM > *To: *Lionel Wolberger <lionel@userway.org>, Maturity Model TF < > public-maturity@w3.org> > *Cc: *Sheri Byrne Haber <sbyrnehaber@vmware.com>, David Fazio < > dfazio@helixopp.com>, Janina Sajka <janina@rednote.net> > *Subject: *Re: New A11Y Maturity Template with Cover included > > Hello everyone, > > > > I found an issue with the excel spreadsheet. > > We needed a “N/A” option for the dropdown list of choices for the status > in case something doesn’t apply to an organization for this particular > proof point. > > > > The template dated A11yMaturityTemplate-20230721.xlsx has that for all > dropdown lists > > I also fixed some color issues in the template and locked the row/column > headers so you know where you are when zoomed in. > > > > This is in the GitHub PR, and also is attached here for convenience until > we merge this into main. > > > > Thanks > > Charles > > EOM > > > > *From: *Charles LaPierre <charlesl@benetech.org> > *Date: *Wednesday, July 19, 2023 at 11:11 AM > *To: *Lionel Wolberger <lionel@userway.org>, Maturity Model TF < > public-maturity@w3.org> > *Cc: *Sheri Byrne Haber <sbyrnehaber@vmware.com>, David Fazio < > dfazio@helixopp.com>, Janina Sajka <janina@rednote.net> > *Subject: *New A11Y Maturity Template with Cover included > > Hello everyone, > > > > I have added the cover page to the version of the excel spreadsheet Sheri > provided us this morning. > > > > I have also fixed all the excel Accessibility issues that the automatic > checker was complaining about mainly color contrast issues and merged > cells, and cleared some test data content from some of the sheets, adjusted > row heights so all the text is visible and added alt text for the W3C logo > on the cover page. > > > > I also fixed the “Remaining proofpoints in this dimension to be assessed:” > for each dimension. > > Which was not removing the intermediate headers rows from the calculations. > > > > Attached is the latest copy with all these improvements including the > updated file name. > > > > I will be adding this version to GitHub shortly. > > > > Thanks > > Charles > > EOM > > > > *From: *Lionel Wolberger <lionel@userway.org> > *Date: *Wednesday, July 19, 2023 at 9:01 AM > *To: *Maturity Model TF <public-maturity@w3.org> > *Cc: *Sheri Byrne Haber <sbyrnehaber@vmware.com>, David Fazio < > dfazio@helixopp.com>, Janina Sajka <janina@rednote.net> > *Subject: *Spreadsheet Cover page > > In the 19 July TF meeting, I had an action to draft a cover page. > > > > Purpose: > > - Carry provenance information, with links > - Have a link to an online resource informing the user of the latest > version of the sheet, with a link to download it. Also, in future that link > may point to an online HTML version of this spreadsheet. > - Copyright info > - Change info > > > > Here is the proposed solution, attached. > > > > Thanks for everyone's help, > > > > - Lionel > > > > > [image: Image removed by sender. Lionel Wolberger] > <https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fuserway.org%2f%3futm_source%3demail-signature%26utm_medium%3demail%26utm_campaign%3dLionel_Wolberger&c=E,1,ZOVOABuBHNziXqs2Zejs8HcjqpGziZnODDEy25RT-f0kaZ0EQUXJLZvKTA0DfwGdIqpDTZ_W4vph6O6OSOOOZjZtlxecKJt25r1M8gZtRmo,&typo=1> > > *Lionel Wolberger* > > COO, UserWay Inc. > > [image: Image removed by sender. UserWay.org] > <https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fuserway.org%2f%3futm_source%3demail-signature%26utm_medium%3demail%26utm_campaign%3dLionel_Wolberger&c=E,1,vZ19QLM3w8CV2ZhMtC5JI_6uETAz0uBYayYAHuVyKRVwyk-C2iUZUUyy_yZnElV3enXr3ANZWUc9mbHugGDcXml1zUnvVEqkouarVCylR0dSHM3zKBp7EK0i&typo=1> > > [image: Image removed by sender. Phone Icon] > > +1 (415) 800-4557 > > [image: Image removed by sender. Envelope Icon] > > lionel@userway.org > > >
Attachments
- image/png attachment: image001.png
- image/png attachment: image002.png
Received on Monday, 24 July 2023 17:44:08 UTC