Meeting minutes
<gb> /issues/78 -> #78
<gb> /issues/104 -> #104
<gb> /issues/103 -> #103
zakim next item
New Business
Fazio_: Had a meeting with Intel head of accessibility. Intel is using the maturity model. Having some difficulties as they are so big. Will be reaching out to Brian for participation.
Github Issues 43 and 85 (Doc Usability work: Stacey, Jeff, Mark, Susi)
stacey: link to google doc for potential solves for issues 43, 85, and 89. https://
stacey: Issues 43, 85 and 89: usability of understanding how to rate and evaluate proof point How to rate and evaluate the dimensions of each section
stacey: Review of google doc
<SusiPallero> +1 to Mark's comment on "measurable" term
Fazio_: Should Optimize say they have proof?
stacey: Document is editable and welcome suggestions
stacey: This removes the table
CharlesL1: Moves it above the proof points
SusiPallero: The document is a little redundant and may need review.
stacey: One or two people to read through the whole document then assign editors
Fazio_: Does it work the same if we say you have proof points that demonstrate…
jeff
kline: Put heigh up: achieved maturity level proof point should be supported by documentation.
stacey: May need to review for clarity. Use different methods to review – read, listen etc.
stacey: Each one is customized for the section. Take a look and add comments.
stacey: Read the comment Jeff and Susi added
Fazio_: Reading proof points 43, 85 and 89
Fazio_: Resolving issues. Will update later comment then.
CharlesL1: I would only close issues when in the editor’s draft.
janina: Create and editor’s draft and make changes there. Close the issue once it is in the editor’s draft.
<Fazio_> Usability google doc addresses Issues 43 and 85. Will close once Editors drsft is updated
kline: MJ is looking for consistent language across all dimensions. I think Stacey started that. We could come up with global language… Stacey has done that. Addresses 85
stacey: Will it address 89?
Fazio_: Reading 89
stacey: Looking at it aligning with clarity and consistency
Maturity Model Scoring
kline: The way the scoring is set up is confusing and not that meaningful. Need to focus on a new scoring method going forward. Trying to set up different level of scores at different stages is confusing and not meaningful Need a way to tally these things. Ie. we have 5 pp in integrate and 5 in optimize and 5 launch.
Fazio_: Scoring can be ambiguous. Same issue in WCAG.
kline: Can’t solve it now. Volunteer to take up a subgroup to come up with a better method for showing progress.
Mark_Miller: I’d like to be part of subgroup
CharlesL1: I’d like to be part of the subgroup. View for each dimension: what is the majority of proof points and get a sense.
kline: Should someone build a set of requirements for web interface?
CharlesL1: Export feature in jSon
Fazio_: Don’t want to house at W3C
Github Issue #78 3.3.2 Ratings for Evaluation - Support section: why is knowledge and skills mentioned
<gb> /issues/78 -> #78
Fazio_: Tried to address last time group was small so doing again.
<Fazio> w3c/
<gb> Issue 78 3.3.2 Ratings for Evaluation - Support section: why is knowledge and skills mentioned? (by maryjom)
Fazio: Reading 78
kline: In support: training is in place with staff to support dimension
kline: Modify to say there is no training programs in place for support staff.
CharlesL1: It is inconsistent but in tables that are going to be rewritten. Need to be consistent.
kline: K&S section is over all org plan. Dimensions need some kind of training.
Fazio: Two solutions: label them out or say in each dimension that they’re provided.
Fazio: We need to update the document for each proof point.
Fazio: Who wants to update the document?
CharlesL1: Will do
CharlesL1: With the outcome, will I have to wait for the table?
stacey: Need to align documents
Fazio: Are we ready to update documents?
stacey: Need to do updates but can do Charles’ updates first
Fazio: You can do and Charles plug in or we can do it along the way.
stacey: I can add to the updates
CharlesL1: Need to nail down language
<Fazio> charles and stacey will present updated language next week
Fazio: Stacy and Charles will present updated language