14:43:56 RRSAgent has joined #maturity 14:44:00 logging to https://www.w3.org/2023/03/29-maturity-irc 14:44:00 RRSAgent, make logs Public 14:44:01 please title this meeting ("meeting: ..."), Fazio 14:44:22 meeting: Maturity Model Task Force 14:44:32 chair: Fazio 14:44:36 present+ 14:46:04 Agenda+ Check in with Josh about Github Issues 14:46:21 Agenda + Continuation of Maturity Model review discussion with Stacey 14:46:37 Agenda + New business 14:59:14 Stacey has joined #maturity 15:01:13 janina has joined #maturity 15:02:40 Mark_Miller has joined #maturity 15:03:06 present+ 15:03:39 present+ 15:03:51 present+ 15:06:23 CharlesL has joined #maturity 15:06:36 present+ 15:06:42 present+ 15:07:27 scribe+ 15:07:37 zakim, next item 15:07:37 agendum 1 -- Check in with Josh about Github Issues -- taken up [from Fazio] 15:07:55 Jutta Treviranus presentation -> https://www.deque.com/axe-con/sessions/preparing-accessibility-for-the-future-and-the-present/ 15:08:22 Janina: AxeCon free of cost but you need to login to get slide deck 15:09:05 … we should get the vocab. for our document. Strongly recommend it. Uta 15:09:57 S/Uta/Jutta 15:10:03 …, IT world is falling behind, she talks about it from an AI perspective and where it might get in the way. 15:11:13 David: bike/wheelchair peddling backwards AI doesn't figure out which direction they are going an can cause issues. 15:11:48 … Action to review Jutta's presentation to inform our maturity model for next week, action for everyone. 15:12:06 zakim, next item 15:12:06 agendum 2 -- Continuation of Maturity Model review discussion with Stacey -- taken up [from Fazio] 15:12:27 David: Stacey do you have an update? 15:12:45 Stacey: Yes Notes on abstracts vs. exec summary etc. what is most appropriate 15:13:29 … notes / blog posts / exec needs. I have couple paragraphs to share first draft. key highlights and stats correct. 15:13:46 … take from exec's here will get their gut reactions. 15:14:31 David: send out an email to public maturity model. so we can reference it in todays meeting. 15:15:15 Stacey: I am not github fluent? I am now fully w3c connected now. 15:15:28 s/fluent?/fluent. 15:16:21 David: Janina know of a github tutorial? 15:16:42 Janina: there is a standard ref. I will find out. We should have a beginners page and will come back. 15:20:23 https://lists.w3.org/Archives/Public/public-maturity/2023Mar/0008.html 15:20:25 https://lists.w3.org/Archives/Public/public-maturity/ 15:21:19 https://lists.w3.org/Archives/Public/public-maturity/2023Mar/0012.html 15:24:36 Janina: Most makes me nervous. there are over 200 countries. many would be better. 15:25:13 … Pointing to examples WCAG and ARIA is another good one. multiple specifications. 15:25:50 … one concept missing too many organization completion dates 1 and done (this is not) its a culture change for the rest of your existance. 15:25:56 q+ 15:26:27 … you keep putting out new products those are the same reasons why you need to continually add 15:26:34 Stacey: yes you are correct. 15:26:51 David: continuous process improvement. 15:27:31 … Evaluating, processes , policies and processes … 15:28:22 Stacey: 1 in 6 people in the world live with a disability. Providing accessible digital products and services is the right thing to do–it’s also required by law in most countries. The W3C Accessibility Maturity Model enables organizations to evaluate and improve their accessibility policies, processes, and outcomes so that their digital products and services can be used by people with disabilities and help them achieve their access 15:28:22 ibility goals.  15:28:22 Accessibility is a collaborative effort, not just one person or one department’s job. Organizations of every size need help assessing their current state, identifying gaps and opportunities, and creating a plan for short-term and long-term success. 15:28:22 15:28:24 The W3C Accessibility Maturity Model provides actionable guides for employee-communication, training, tools, as well as organizational, cultural and technical assessment and measurement documentation.  15:28:24 This model is designed to work for any size of organization, from small to large corporations or government agencies. Additionally, this is intended to be independent of the requirements set forth in relevant technical accessibility standards, such as the Web Content Accessibility Guidelines (WCAG). 15:28:59 Brian: is there an opportunity, improving an accessible workplace. 15:29:34 … you are transforming your workplace 15:29:54 Janina: verbs to a progressive "ongoing" nature action verbs. 15:30:43 Stacey: Rachel and my team looking beyond inclusive design and will look from our personal notes and I might ask her to read it over and to help phrasing. 15:31:38 Mark: accessibility is a collaborative effort. period. remove the rest about 1 person. 15:32:15 David: should we be giving examples etc. 15:32:45 Brian: you can't just tag 3 people with a11y and feel its taken care of. 15:33:26 q? 15:33:57 Stacey: welcomes any edits. 15:34:28 Mark: enables organizations, "so that their digital" enabling , remove "can" 15:35:24 ack me 15:36:38 Charles: include Nonprofit. / NGO 15:37:19 Janina: glossary to identify words. 15:37:37 agenda? 15:38:32 David: Stacey's Observations from the Maturity Model. 15:39:08 Would love to see a more “how to” type of document to compliment this document. Like a toolkit for a company or a team to use. “now that you have this info, here’s how you can go use it ASAP without tons of training.” — here’s the WHY and the WHAT now here’s the HOW. 15:40:38 Stacey: Spider graphs. which is easy to understand, but other tabs harder to understand. 15:41:30 … which tab was the newest or look at each tab, usecase / process for the spreadsheet. is it all of the tabs. 15:42:14 Brian: given the spreadsheet, there is more than just 7 lot of different examples. 15:43:06 David: I think this was Jeff's project, not sure, good to hear other experiences. we should wait for him. two competing spreadsheets. Jakes vs. Jeff, we published Jeffs. 15:43:32 Stacey: give spreadsheet to anyone and they can run with it without having an expert. 15:44:13 Janina: that is just temporary our intention we will build an HTML forms, and company could make their own database and generate own reports. bigger question. 15:44:45 Stacey: spreadsheets can be overwhelming but it is also a lower barrier for entry. 15:44:55 they still need that entry point. 15:45:22 David: I though this spreadsheet like a wireframe for our tech we are building. if its causing confusion. 15:45:47 Janina: CSV for formulas. 15:46:15 Brian: make if flexible clear that here is the structure and here is some examples where its clear. 15:47:33 Janina: can't be a host for the data. 15:48:58 Charles: the html form we do would have an exports to CSV, and also some Data visualization of the results. 15:49:27 David: this is why we started this to have data to visualize the accessibility maturity of a company. 15:49:56 … need multiple formats based on company level of expertise. 15:53:09 Charles: asked Sheri to add the the scoring. so Benetech can do an initial pass. 15:53:16 zakim, take up net item 15:53:16 I don't understand 'take up net item', CharlesL 15:53:21 zakim, next item 15:53:21 agendum 3 -- New business -- taken up [from Fazio] 15:54:41 Brian: my group found an online book / pamphlet it was really good. great info. from Sheri. 15:55:05 https://abilitynet.org.uk/building-accessibility-champions-network 15:55:49 Sheri: I am going to miss the 12 & 19. 15:55:58 Janina: I may miss the 12th. not sure. 15:56:17 s/Sheri/Stacey/ 15:56:50 rrsagent, make logs public 15:57:09 rrsagent, draft minutes 15:57:11 I have made the request to generate https://www.w3.org/2023/03/29-maturity-minutes.html CharlesL