- From: Jeff Kline <jeffrey.l.kline@gmail.com>
- Date: Fri, 12 Apr 2024 08:46:08 +0000
- To: Stacey Swinehart <stacey.swinehart@gmail.com>, David Fazio <dfazio@helixopp.com>
- CC: "public-maturity@w3.org" <public-maturity@w3.org>, "Samuels, Lori (NBCUniversal)" <Lori.Samuels@nbcuni.com>
- Message-ID: <BN0P223MB00226E6FC72A079DB7EA8957A7042@BN0P223MB0022.NAMP223.PROD.OUTLOOK.COM>
In response to work items assigned to me in last meeting based on procurement elements: Issue 81 – Section 3.4.1 Proof Points for ICT Development Lifecycle: Missing planning aspects * No procurement language present. Sheri owns this dimension Issue 148 - Add information fields for metadata for each dimension * No procurement language present. Valid request. I can download and edit the version that Charles put in github, but might need guidance on how to upload it back. Issue 157 - Section 3.6: proof points should be expanded to take into account evidence of the outcomes of the procurement process. From Jason: In section 3.6, evidence of the outcomes of the procurement process should be considered in evaluating its maturity. Informally, after the fact, how accessible do the procured products and services turn out to be, compared with what the antecedent evaluation (prior to acquisition) would lead one to expect? Are there unexpected defects/shortcomings that are only discovered after procurement? If so, this indicates a lack of maturity in the process, in that the issues should have been identified in the evaluation prior to acquisition. * How well and how consistently do the procured products/services live up to the suppliers' claims about accessibility? * To what extent do suppliers correct defects brought to their attention by the organaization, effectively and in a timely manner? * How satisfied are employees, customers or others with disabilities who use procured products/services with their accessibility (once they've been deployed and used)? I think factors such as these tend to reveal the maturity (or otherwise) of the procurement process, especially when these factors are evaluated across multiple procurements. Response: While those proof points are not specifically mentioned, there are current proof points from multiple dimensions that encompass these concepts in a way that allows organizations to establish their own nonprescriptive methods and processes, consistent with the overall philosophy of the Maturity Model: * How well and how consistently do the procured products/services live up to the suppliers' claims about accessibility? * Burden of Proof subsection proof points * Proof of Vendor testing (automated and manual) * Development life cycle accessibility criteria integration and development reviews (for dev services) * Warranties and remedies section includes accessibility * Vendor corrective actions / remediation plans pre and post deployment * To what extent do suppliers correct defects brought to their attention by the organaization, effectively and in a timely manner? * Burden of Proof subsection proof points * Development life cycle accessibility criteria integration and development reviews (for dev services) * Warranties and remedies section includes accessibility * Vendor corrective actions / remediation plans pre and post deployment * Consistent use of Standardized Accessibility Procurement Document Language subsection proof points * ICT accessibility contract language * Accessibility in Procurement Program Management subsection proof points * Accessibility Audits * Contract Lifecycle Management * In the Support Dimension – Customer Support subsection proof points * Have processes put on place to guarantee that code from third parties or provided by external vendors are acce * How satisfied are employees, customers or others with disabilities who use procured products/services with their accessibility (once they've been deployed and used)? * In the Support Dimension – Customer Support subsection proof points * Establish a process for receiving and responding to feedback on accessibility * Have processes put on place to guarantee that code from third parties or provided by external vendors are accessible * Ensure that newly procured or developed digital documents offered to the customers are accessible * Provide a specific channel for customers to report accessibility issues or blockers in an easy and accessible way. e.g.: dedicated email address * Any feedback plan incorporates an accessible way of responding to the customers that provided the feedback with updates about the state and decisions on the feedback. * In the Support Dimension Organizational Support subsection proof points * Involve people with disabilities in the planning and implementation of accessibility initiatives * In the ICT Dev Process Dimension - Development subsection proof points * Documented way to triage and prioritize fixing accessibility issues and address customer-reported feedback on accessibility If there are no concerns, I plan to c/p this response into the issue record and close it. Regards, [A picture containing text, black, clock Description automatically generated]<http://strategicaccessibility.com/> jeffrey.l.kline@gmail.com 5 1 2 . 4 2 6 . 9 7 7 9 From: Stacey Swinehart <stacey.swinehart@gmail.com> Date: Wednesday, April 10, 2024 at 6:04 PM To: David Fazio <dfazio@helixopp.com> Cc: public-maturity@w3.org <public-maturity@w3.org>, Samuels, Lori (NBCUniversal) <Lori.Samuels@nbcuni.com> Subject: Re: [Maturity] Model Task Force 04-10-24 Meeting Agenda All, Minutes for April 10 meeting<https://www.w3.org/2024/04/10-maturity-minutes.html> Cheers, Stacey On Tue, Apr 9, 2024 at 7:59 PM David Fazio <dfazio@helixopp.com<mailto:dfazio@helixopp.com>> wrote: Here are the Minutes from our last meeting: https://www.w3.org/2024/04/03-maturity-minutes.html Email Archive: https://lists.w3.org/Archives/Public/public-maturity/ What: Maturity Model Weekly Teleconference When: Wednesday 10 April 2024 11:00 AM Boston -- U.S. Eastern Time (EDT: UTC -4:00) Corresponding times in other time zones are: http://timeanddate.com/worldclock/fixedtime.html?msg=Maturity+Model+Subgroup+Teleconference&iso=20240410T11&p1=43&ah=1 Where: Zoom Teleconference Service Please access Zoom via the link below: https://www.w3.org/2017/08/telecon-info_maturity-model IRC: irc.w3.org<http://irc.w3.orgqhKKY57jjn8X4XvUUNZK7qRiY9WrlWsQ6AjP9AIhAK6GwkarYyHv7O099KZWMixgDit8-uqdc3DQ4IV3uwMn> Channel: #maturity Agenda Agenda+ New Business Agenda+ Github Issues 43, 78, 85, 102, 103, 104 (Usability doc feedback)<https://docs.google.com/document/d/1Wrhomdc2gJWIkDPOveiH3_ig1bddTMonEhIDZIzohrc/edit#heading=h.93exgeg396jg> Agenda+ Maturity Model Scoring Subgroup Update Agenda+ Github Issue #107 Definition of "Full maturity" needs to be adjusted, as there is no need to optimize anymore by then<https://github.com/w3c/maturity-model/issues/107> David Fazio, President | [signature_1633184954] <https://www.linkedin.com/in/davidpfazio/> [Helix Opportunity Logo]|[signature_1943303136]<https://www.linkedin.com/company/helixopportunity> W. www.helixopp.com<http://www.helixopp.com> P. +1 415.882.6034<tel:+14158826034> [2023 Official National Minority Supplier Diversity Council Minority Business Enterprise Seal] [Disability-Owned Business Enterprise Badge] [International Association of Accessibility Professionals Organizational Member Badge] [2023 HRCI Approved Provider Seal] [Society for Human Resource Management Approved Provider Badge]
Attachments
- image/png attachment: image001.png
- image/png attachment: image002.png
- image/png attachment: image003.png
- image/png attachment: image004.png
- image/jpeg attachment: image005.jpg
- image/png attachment: image006.png
- image/jpeg attachment: image007.jpg
- image/png attachment: image008.png
- image/png attachment: 09-image001.png
Received on Friday, 12 April 2024 08:46:21 UTC