Meeting minutes
David: had a great CSUN and our Maturity Model can help a lot of companies. maybe present next year
Relevant CSUN News/Updates
Mark: 80% of pre-covid numbers. very well attended.
David: we should present next year.
… , AxeCon did a presentation on Maturity Model.
Sheri: if we did a talk later this year Knowbility in May, but the we may have missed the deadline.
… , we should look for other conferences this year.
Jeff: maybe the IAAP
Mark: I did a similar talk in 2022 there are a number of similar models.
David: Irfan did a great presentation, David attended and mentioned the Maturity Model.
Continuation of Maturity Model review discussion with Stacey
David: OKR's topic … should we move on? - Yes
… Launch and Integrate, maybe Launch is a short timeframe.
<Fazio_> I feel like there’s a stage missing between Launch and Integrate based on the criteria definition. Or, perhaps launch needs a broader scope of definition. Launch in this instance might actually be a short timeframe, and how this is defined integrate might be as well.
Stacey: there may be points later in the document to bring near the start, what are the different scopes for these. Whats the timeline? Setting the stage on how long a stage may take would be good to bring up.
David: is there a way to state this scope (waterfall vs. agile. etc.)
Stacey: broad level how long to get from start to finish of the entire process.
… as I read on I found the information I was wanting, but would be great to have this information sooner in the document for each stage of the process.
Sheri: it really depends on motivation. Factors that may impact the length of time for each stage include.
Janina: important to reinforce whats really going on is a cultural change in the company.
David: never stops as changes occur in the company. not a 1 and done.
… continuous improvements.
Stacey: cultural change, social change. should this be discussed in this model?
Janina: That would belong in an introduction.
Jeff: We have a cultural dimension.
David: we could add to it if we need to.
Janina: nice to have the details but good to have a terce summary. Doesn't matter if it takes you longer etc. goal creating a culture of maintaining accessibility.
Mark: The actual roadmap vs. the details within the maturity model. How deep do we want to get into those details.
David: we have the core dimensions, but the how is up to the company to implement
Jeff: the proof points is the n state. You are trying to achieve those proof points at the end of the day. Everyone will have their own systems, processes etc. But providing those proof points is what they need to focus on to change their organization
David: It really brings to the forefront where you are at with those proof points and brings awareness. This is what we are actually doing but up to the organization to interpret those and act upon them.
… happy to add to the introduction to make this clearer.
Jeff: from tech community all this is vey foreign to them. It may not be our main audience. This is not a technical artifact.
David: every person in the org should understand this or only management?
David: Do we need to make it clearer for the tech folks even if they aren't the main audience.
Stacey: TLDR - Too Long Didn't Read, Need the Exec Summary. Is there metrics and outcomes, how much, who will do this etc.
David: tech people need step by step. are we missing the step by step? How do we calm the tech community on board.
… I don't know where to start, how to check my work etc.
Janina: APA has a very broad scope. Whos our expert, etc.
… the TLDR should be somewhere in the introduction to help those who want more details.
… I will take a pass to see how it can be improved.
Jeff: its not a long read. Need Clevel buy in, managers.
Janina: need to make that message clear. preferred way to start a project is to write the press release first.
<Fazio_> There’s a lot of planning and potentially internal research, staffing, out-sourcing, etc. that might happen to make the items in integration come into play. So integrate feels a bit light on the criteria as well.
Stacey: we have covered that.
<Fazio_> I would expect training and education (up-skilling) to be called out somewhere in this as well as accountability. Who’s accountable? While accessibility is everyone’s job, there are definitely structures in place in organizations where performance is based on certain things…and very rarely is accessibility one of those things. So that would need to be a big lever to pull inside of a company becoming more mature.
Stacey: your company knows who is accountable.
Sheri: you need to be measuring it, maturity model is a way to measure.
Jeff: culture proof points exec sponsor, high level leadership, policy business strategy
Stacey: yes its all there, any a11y knowledge "hey we need this" If they don't have that knowledge may be hard to understand and take.
Jeff: ISO-9000 most of the time there were no experts it was on process and policy. Some exec owned it and brought someone in and they became the center of compency to ensure ISO-9000 was implemented. A strong project manager can bring in the right people. you need to go to the right people and get it done.
David: maybe a FAQ section for these (Findable Help WCAG requirement as well :)
… instead of tweaking the model we can add a FAQ
Stacey: instead of a FAQ maybe a Toolkit on how to handle it. What are first steps. Where do I find these skills if I don't have them inhouse?
David: is this similar to the spreadsheet or more?
Jeff: reference materials out there as these maturity models evolve
David: companies like DeQue, Level Access etc will put out support materials as this takes off.
Janina: I agree FAQ would be helpful and TLDR is a real thing. we need the support and future readings.
Mark: we have the model but people might need other things to make the model useful. I think FAQ & toolkit is both needed. Examples on how different orgs use the model.
Sheri: this is exactly the use-cases I started writing.
David: I sent out the use-cases yesterday. Will take it up next meeting. Will that help with explaining things better, if not we can discuss what else is needed.
Sheri: I agree although I won't be able to attend the next meeting.
Stacey: I am not getting the emails from this group. I will ask Roy.
… upskilling - do we with this model is there a rec of what level of training or knowledge is requried?
David: No that would be up to the company.
Stacey: is there a general statement, any one touching digital experience should require a basic level of a11y skills etc.
Mark: you have to have knowledge of the best practices for your particular situation.
David: Level of needs will vary dramatically, no way for us to know.
… do we need to come up with these TLDR bullet points.
Stacey: I can do that.
David: bullet points use cases etc.
<Fazio_> For the overarching maturity rating…how do you know when you get to each one via the dimensions? What if you have integrate for most things, but not for others?
Stacey: Overarching Maturity rating - is it possible can you achieve different levels of maturity.
David: could be cumulative but up to the organization.
Sheri: rather than giving the entire company a ranking, I gave them a score, every department got its overall score.
David: Read over Sheri's use-cases. come up with your thoughts will discuss in 2 weeks. Stacey come up with some TLDR bullet points, and will continue next week. Can check in with Josh and jakes github issues
Charles: Sheri when will you have time to update the spreadsheet maturity model scoring system?
Sheri: First week of April work? I should have time then.
Charles: Perfect.