Meeting minutes
ation - Support: Outcomes for optimize stage don't align with proof points coincides with issue 172. (Jeff was going to work on it. See previous minutes.) Agenda+ Github Issue #83 Section 3.7.2 Ratings for Evaluation - Culture: proof points vs. ratings mismatch Agenda+ Github Issue #85 Inconsistencies in Inactive ratings for various dimensions Agenda + Github Issue #89 ICT Development Lifecycle ratings outcomes a
ren't stated like the outcomes are in Silver
<gb> /issues/79 -> #79
<gb> /issues/132 -> #132
<gb> /issues/85 -> #85
<gb> /issues/83 -> #83
<gb> /issues/89 -> #89
<janina> Date 06 Dec 2023
sbyrnehaber: New Business?
… we are not meeting Dec 27th and Jan 3rd. We are meeting on the 20th.
CSUN
Lionel, not sure if I will be there or not.
Janina: some groups may have a F2F at CSUN but still too early to tell.
sbyrnehaber: I am not planning on going, but could jump on a cheap flight for a side meeting.
Charles: I will be at CSUN since I am presenting.
sbyrnehaber: CSUN submissions has pasted due in September.
janina: lets circle back in January.
Working Draft EOY update
janina: APA would like to update our title to drop "W3C" keep Accessibility Maturity Model. Sooner we can remove it from the draft W3C management will be happier.
Jeff: Can we include "IT or digital" in the title?
janina: That will be difficult to add due to charters etc.
sbyrnehaber: We have a lot of small grammar fixes, Stacey made etc? or only the title change?
janina: We can include all the updates including all changes to the editors draft.
sbyrnehaber: the editors Draft is in a good shape
RESOLUTION: participants here approve a working draft update publication once the title has been updated.
janina: Roy will take care of that. We can update working drafts without APA approval, so this is good publish updates often.
WCAG target number?
janina: ADAPT conversations, realized there is guidance in WCAG defines A/AA and AAA and A is the min. to be accessible but highly recommends striving for AA. Should we ask Maturity Model consider generic guidance look for conformance and strive for functional accessibility support.
… we can say this generically.
sbyrnehaber: we deliberately left out WCAG versions. but will need to be carefully word smith. "including but not limited to..."
janina: could cut across multiple places the minimum is not enough. where this should go? Thats a good question. suggestions?
sbyrnehaber: it doesn't belong in the dimensions, somewhere in the introduction. there is a section "scope" that seems to be one place 1.2.1 currently short 1 sentence.
… we mention you can do only 1 dimension.
… , since David is not here, I can do it with him. Janina agrees.
sbyrnehaber: David and I will take this on.
janina: I will create a ticket and assign it to Sheri.
janina: Yes this satisfies the APA.
sbyrnehaber: also satisfies Lionel concern
Topic Issue #43
<gb> /issues/43 -> #43
<kline> w3c/
<gb> Issue 43 Should "proof points" and "ratings for evaluation" sections be combined for clarity? (by jasonjgw)
sbyrnehaber: google doc
<sbyrnehaber> https://
sbyrnehaber: Stacy made this proposal. she is not here today.
… got rid of the table and replaced with a Narative.
… did we want to keep the table + Narrative?
… group agrees to also include the table, but the narrative changes look good.
Jeff: I don't have a problem with this.
sbyrnehaber: Jason's point is folks with cognitive issues it will help
Jeff: we do have the generic levels, and have those come after the proof points provides the context for those different levels.
sbyrnehaber: Stacy's example are specific to this specific dimension.
… tell them what you are going to say, is intro, sayit is what Stacy has and then include the table at the end to reinforce it.
Jeff: I am fine either way.
sbyrnehaber: need to create an issue for each dimension, I don't think we do this before the next updated working draft.
janina: we can have PR's but wouldn't approve them until Roy has released.
sbyrnehaber: do we have anyone assigned to each dimension?
… do we want to revisit this?
… Suzy owns Support, Stacy Communications, we need K&S, Sheri owns ICT, Jeff Procurement,
<sbyrnehaber> David owns personnel
<sbyrnehaber> and when I say "own" I mean is responsible for making generic changes that are being applied to all dimensions
Jeff: I will take K&S
… I will maintain Procurement and can take on K&S
sbyrnehaber: Own means generic stuff for now. anyone else for K&S?
… what about Culture?
sbyrnehaber: I will take Culture for now.
… someone should update ticket #43. Stacy does currently I will ask her to update this based on minutes
<gb> /issues/43 -> #43
issue #132
<gb> /issues/132 -> #132
<sbyrnehaber> w3c/
<gb> Issue 132 User Research is not User Experience (by jake-abma)
sbyrnehaber: asking for clarification of the language. which I agree with
Jeff: its just a title change ?
sbyrnehaber: and a little bit of the content. we want to make the title match the content and include experience not just resear.
… section 3.4.1.3
… so this is mine. Assign this ticket to me and I will take care of.
Jeff: this was originally from KH not sure who this is. someone emailed in a comment.
sbyrnehaber: might be Karen Hockins. with Level Access if she is still there.
sbyrnehaber: I will reach out to her with a draft to see if this addresses her concerns.
Issue 79
<sbyrnehaber> w3c/
<sbyrnehaber> replaced by 198: w3c/
<gb> Issue 198 Support Optimize Outcomes Statement Needs Revision to Align with Dimension Goals. Replaces Issue #79 (by jeffkline)
Jeff: we closed that and moved to 198 needs to reflect the general purpose of the dimension.
sbyrnehaber: added to the issue or link to a google doc to discuss it further.
Jeff: I can add it in there.
<kline> Proposed language: IT Accessibility support for all internal and external IT is complete. Accessible self-help features are fully integrated for all IT. Training programs are in place for IT support staff are trained and deployed. Continuous improvement plans ongoing.
Jeff: This is the optimized.
… this is in the support Dimension.
sbyrnehaber: ok. That implies to be optimized self help is mandatory.
Jeff: maybe need to tweak it a little more, some things self help others not depending. need to capture something regarding self help.
sbyrnehaber: support is available to all personal not what kind of help.
… second sentence needs tweaking.
<sbyrnehaber> Instead of "Accessible self-help features are fully integrated for all IT" how about "Help available to all personnel for all ICT"
<sbyrnehaber> and change IT to ICT in the other sentences
sbyrnehaber: two suggested changes as listed above
Jeff: OK.
… I will edit and push that before Roy freezes
sbyrnehaber: there may be a changes freeze date in W3C for holidays. Sheri will check