Meeting minutes
(backing up Susi)
New Business
Susi was authorized to add classes on maturity model to her program at the University of Barcelona
classes are available on zoom, you can hear it in English or Spanish
… When accessibility criteria are integrated as an essential consideration of procurement processes and contract language, an organization can be more capable of providing accessible products, services, and workplaces. It can save time through more efficient production of accessible content, and avoid unnecessary time spent in remediation of
Github Issue #323 Review Suggested Language to Strengthen Procurement Dimension
Mark_Miller he will be working along with Jeff on the structure of the abstract to define it and develop
there's an email with suggestions that we will go through starting with Procurement
<JeffAdams-UN> w3c/
<gb> Issue 323 Strengthen motivation for procurement language (by judbrew) [Editorial]
<Neha> .... When accessibility criteria are integrated as an essential consideration of procurement processes and contract language, an organization can be more capable of providing accessible products, services, and workplaces. It can save time through more efficient production of accessible content, and avoid unnecessary time spent in remediation of
<Neha> inaccessible content created by tools that do not support accessibility. Additionally, if an organization communicates its product selection criteria to product vendors, it can help incentivize product developers to improve their future product offerings.
inaccessible content created by tools that do not support accessibility. Additionally, if an organization communicates its product selection criteria to product vendors, it can help incentivize product developers to improve their future product offerings.
JeffAdams-UN is reading outloud the issue 323 The current text seems to under-motivate the strategic importance of procurement policy in an organization's accessibility ecosystem, and as feedback towards improving the offerings of product vendors. Please consider clarifying "When accessibility criteria..." sentence and expanding the motivations
along the following lines.
Sheri_B-H suggests not needing accomodations if you procure accessible software
it also allows more people with disabilities to join the company and bring up the accessibility topic more
<Neha> Procurement is a strategic process focused on finding and acquiring cost-effective products needed by an organization. Activities in procurement include sourcing, negotiation, and selection of goods and services.
<Neha> The majority of an organization's ICT assets result from procurement transactions and contracts. Therefore, accessibility criteria must be integrated as an essential consideration of procurement processes, contract language, etc. This ensures that an organization will be more capable of providing accessible products, services, and workplaces while
<Neha> reducing time, cost and risks of deploying inaccessible IT deliverables. Additionally, when an organization communicates to product vendors that accessibility requirements are part of the product selection criteria, it can help incentivize product developers to improve their future product offerings.
Fazio suggests adding what Sheri proposed about reducing the need of accommodations when we procure accessibility software
Sheri_B-H
suggests finding something in the middle and merge both perspectives
<Fazio> add accommodation reduction
Continue with GitHub Issues 328 & 334: Abstract & About Section Definitions
Issue 328: The abstract could benefit from a clearer description of what the model can do:
"help you measure where you are as an organisation or department.
At the moment it reads quite “salesy”." added by iadawn
Issue 334: "The “About the Accessibility Maturity Model” section could be much simplified and, again, less “salesy”.
Also, it doesn’t quite reflect what the AMM can help you achieve - first and foremost it is a way of measuring organisational maturity. This section seems to suggest that it will sort out all your organisational accessibility issues." added by iadawn
there's 2 issues as iadawn think these should be addressed separately because Abstract and About have two different purposes and are different sections
Mark_Miller is presenting a proposal for Abstract and Revised How to Use
How to Use the AMM Structure proposed is "Purpose" "Scope" "Out of Scope"
Sheri_B-H suggests working examples
maybe at bottom of section 1 as a subsection
Fazio suggest it might be an appendix with an interlink
Sheri_B-H risk of people missing all the rest of the content and the terms for going to the example before they keep reading
We agree on adding a link to the examples
Sheri_B-H suggests that if the link is taking to the spreadsheet it can be a subsection like 2.5
janina don't lock the language around the spreadsheet
we don't want people to think the spreadsheet is the only way of doing it
<Neha> +1
Mark_Miller suggests a new section "section 3" and the majority of the group agrees
Sheri_B-H suggests a section 3 in between the dimensions and the example
<SusiPallero> +1 to Sheri suggestion
The group is discussing about the spreadsheet, how to improve it and maintain it or migrating it to a different format, but addressing it is not part of the AMM just a tool with suggestions and examples on how to apply the AMM
janina The point of worked example can be left out as it doesn't belong in this document
Susi: can we write articles and include links to them in the maturity model
david: We can't have an appearance of endorsement. Articles can link into the maturity model, but the model can't link to articles
janina: we could do the example as a separate document
janina: it could be in the wiki, part of the package, but it can't be in the model itself