Meeting minutes
New Business
janina: will miss next week
Github Issue #228 Syncing proof points in the MM document and the assessment tool
jeff: left off at procurement tab line 14, there was an error for language - should have been subheadings, so discussing the language on that. Process to validate accessibility claims...where did we leave that? Subtitle area, so no language associated, just title
jeff: left off trying to align on the language in line 15. started editing the line and boiled it down in assessment tool. Ended up proof of a11y testing as proposed language to go in both
jeff: everyone ok with that today?
yes
jeff: 15 - use what's in assessment tool. proof of a11y testing. in discussion last week do we really need to say manual and automatic? what was in the doc was too much.
jeff: so we're going to use this one? OK
jeff: line 16, we had different language, dev lifecycle criteria integration and dev reviews. Then reviews of d3v lifecycle a11y...really saying contract language has specific lang for how to handle development. Typically, a review at every checkpoint to make sure a11y work is being done. Just a difference of language there
Neha4: doc lang makes more sense, review both things, lifecycle and development. in assessment tool, just mentioning dev reviews not lifecycle. so doc makes more sense
jeff: in doc, added in procurement checkpoints...maybe that's it?
Fazio: yeah
jeff: if you're ok with it, we can move procurement checkpoint lang from line 20 to replace lang in line 16. delete line 20
CharlesL: mark as reference instead of delete
jeff: next one is the same- warranties and remedies includes a11y. I think in the one in the assessment tool is fine. This is line 17
CharlesL: agree
jeff: next two are identical. No work. Line 20 will go away. So a11y in procurement program management, all line items covered, just diff language.
Fazio: do we just say program is evaluated for a11y?
jeff: would like to give a little more direction
jeff: program management is sub topic heading, within that process and policies, lifecycle of contracts, metrics, and defined process for addressing complaints
Fazio: itemizing instead of being broad
jeff: ok with the new language?
jeff: processes and polices evaluated for a11y integration
agreed
jeff: next line, the word a11y isnt' in there anywhere. add "for a11y" at the end
CharlesL: maybe just includes a11y?
jeff: contract lifecycle management includes a11y...requirements or criteria? what do you think?
jeff: requirements
agreed
jeff: procurement related dash a11y metric - i like what's in the doc.
agreed
jeff: defined process for identifying a11y complaints..or issue management process for a11y...I could go either way
CharlesL: I like the doc
Neha4: i like the doc version
jeff: going to change it a little bit and add a11y in there. issues complaints?
Fazio: is someone saying procurement process isn't accessible? or a11y information isn't in it?
jeff: when you buy something and you deploy, and there's an issue, has to go abck to vendor for remediation
CharlesL: something in contract needs to have info about how to raise with the vendor.
jeff: where is it and how does it get tracked. all those things
Fazio: do we add "with the vendor" in there
Fazio: should we say warranty includes...remediating complaints?
jeff: remedy could be a lot of things. this is really more on individuals...complaining about issues/problems. maybe need to put the word "users" in here somehow
… defined process for identifying user a11y complaints
jeff: you as the owner of what gets deployed needs to have a process for documenting, remediating, communicating to the vendor...
Fazio: i think what's missing is coordinating with the vendor, not internally
jeff: will add with vendor
jeff: that's it, the bottom one is standard lang for dimensions, goals, metrics. Need to add procurement training one in.
fazio: last tab - culture?
jeff: don't worry abotu line 8- it's a dup. line 9 - i like what's in assessment tool for wording.
CharlesL: agreed
jeff: use assessment language
jeff: next one, business strategy and a11y as market differentiator. I like what's in the assessment tool for this one.
jeff: asking about promotion a little prescriptive.
CharlesL: delete completely?
Fazio: or rephrase...a11y part of business strategy? Telling them how is not what we should do
CharlesL: remove market differentiator.
Fazio: digital a11y is included in business strategy.
jeff: digital a11y for disability inclusion included in core values...i like whats's in the tool better.
Fazio: can't we say digital a11y is included in core values?
jeff: digital a11y included in code of conduct...
Fazio: can you do that?
janina: you can, i think w3c has it as an example in theirs
jeff: start with code of conduct or digital a11y?
jeff: to be consistent, use assessment tool version
jeff: disability focus in DEI activities.
Fazio: we gotta reword that one
janina: it's not in w3c code of conduct (going back to prior line item)
Fazio: take out DEI line item
jeff: community of practice line - for consistency should stay in and use assessment tool language.
Fazio: we might need this word in the glossary/key terms. Ok it's in there
jeff: use assessment tool lang?
agreed
pick up line item 15 in culture. Highlighted in red for next time
Fazio: need to talk about some github issues. next week might be a short meeting. When janina is back discuss publishing, then maybe take a break.