Meeting minutes
<gb> /issues/193 -> #193
<gb> /issues/228 -> #228
New Business
<Fazio> Helix Opportunity's AI-powered digital accessibility auditing tool, Ottitor, Beta 3 release is free and open to the public on all chromium based browsers. You can download at Google Chrome Store here: https://
congrats!
<SusiPallero> felicitaciones!
Fazio: Check it out let me know what you all think.
<SusiPallero> Congrats Sheri!
Sheri_B-H: Contractor with NFCU
… NFCU will be using the a11y maturity model.
<Mark_Miller> Happy to have you part of the NFCU team, Sheri!
Janina: will need endorsements during the 2nd round before Last Call.
… We will need them in about 2 months.
Fazio: We have a Masters student's Thesis using the maturity model. her advisor is a W3C member.
janina: I will be away in a couple of weeks. F2F Adapt (Symbols)
Github Issue #228 Syncing proof points in the MM document and the assessment tool
<gb> /issues/228 -> #228
<Sheri_B-H> hard stop at 8:30, sorry, and same for next week. I have my NFCU calendar blocked from 8-9 after that
Jeff: Procurement Tool / Document synchronized.
… discussion on proof points that are not in sync.
Use the document version for standardization of solicitation language including A11y Procurements & contracts, bids and proposals.
… published ICT a11y policy (document version is more descriptive)
… / procurement policy (need to include a11y in both)
JennE: We need to make sure a11y is part of the ICT Procurement policy.
Jeff: proof of a11y evaluations.
Mark_Miller: tool version is a little clearer.
Fazio: are we collecting the responses.
Jeff: got the info and have evaluated it. you are providing the evaluation of the response. Proof of responses have been evaluated.
… proof that a11y evaluation has been performed.
JennE: The onus of proof is usually done by the vendor.
Jeff: yes they have to provide it but you need to evaluate the proof.
Jeff: proof that a11y evaluation are performed on solicitation responces.
Sheri has been kicked out of IRC above *W3C Issue*
Jeff: burden of proof a11y contract language requirements.
Fazio: this is a part of the procurement process. includes verification?
Mark_Miller: included in contracts vendor / purchaser.
Jeff: perform/supply additional information.
… put vendors on notice that the vendor will need to supply additional support if requested.
Mark_Miller: BOP of accessibility compliance included in all contract language.
Fazio: we dont want to be too prescriptive here.
janina: RFP or in the contract?
Jeff, maybe solicitation language
janina: product and service Request for Offer etc.
… we need a defintion of Burden of Proof.
… documentation?
Jeff: ACR - you may want to request additional like bug report.
Fazio: validation process of a11y claims are in place.
Mark_Miller: a process to validate.
… A process to validate submitted accessibility claims for inclusion in solicitation and contract language.
Fazio: A process to validate submitted accessibility claims is in place.
Jeff: Proof of vendor testing.
janina: I did some testing... doesn't tell me much.
Jeff: we want to know if it has been tested and how.
… requirement is that the vendor has done testing.
janina: document that you have done testing.
… leave it at that.
Jeff: also remove automated / manual.
<SusiPallero> +1
Fazio: a mom/pop won't know what automated & manual testing is they just want to know a11y testing has been done.
Jeff: Proof of Vendor accessibility testing
… when I copy & pasting I messed up that some of these are Sub Titles
Charles: We will come back to this Header in the next meeting.