CHAOSS Accessibility/Disability Inclusion WG, June 2, 2025 ![rw-book-cover](https://i.ytimg.com/vi/Kd_1zOiUWbY/maxresdefault.jpg) ## Metadata - Author: [[CHAOSS]] - Full Title: CHAOSS Accessibility/Disability Inclusion WG, June 2, 2025 - Category: #articles - Document Note: --- tags: - #accessibility - #open_source - #disability_inclusion Author: CHAOSS Accessibility/Disability Inclusion WG Source: YouTube Meeting Transcript Reference: https://www.youtube.com/watch?v=Kd_1zOiUWbY date created: 2025-06-18 10:00 --- # Title: CHAOSS Accessibility & Disability Inclusion Working Group Meeting – June 2, 2025 ## Table of Contents: - 📝 [Summary](#-summary) - 📖 [Main Content](#-main-content) - 🗒️ [Notes](#-notes) - 📖 [References](#-references) - 🗣️ [Paraphrase](#-paraphrase) - 📰 [Newsletter](#-newsletter) - ✅ [Action Items](#-action-items) - 🧪 [Hypotheses](#-hypotheses) - 📊 [Methodology](#-methodology) - ❓ [Questions](#-questions) - 🔮 [Future Research](#-future-research) - 💡 [Implications](#-implications) - 🧠 [Learning Styles Assessment](#-learning-styles-assessment) - 📊 [Accessibility Assessment](#-accessibility-assessment) - 🌍 [DEIB Assessment](#-deib-assessment) - ✅ [Logical Validity](#-logical-validity) - 🔍 [DARVO Analysis](#-darvo-analysis) - 🔍 [SEO Evaluation](#-seo-evaluation) - 🎯 [Conclusion](#-conclusion) ### References: Include a list of sources consulted and cited in the article. --- ## 📝 Summary: This meeting focused on accessibility and disability inclusion within the CHAOSS community and broader open source projects. Key topics included onboarding new members, challenges with accessibility audits (particularly organizing findings per WCAG principles), strategies for improved collaboration, and planning inclusive activities for ChaosCon. The group emphasized including people with disabilities in the process, fostering engagement through panel sessions rather than workshops to maximize inclusivity, and addressing logistical support like transportation and sign language interpretation. Additionally, the meeting explored building a supportive environment for developers focusing on accessible coding and auditing, while acknowledging existing resource gaps. --- ## 📖 Main Content: The group introduced new member Daniel, a front-end developer from Nigeria, and reiterated the focus on improving accessibility in open source. Bi-weekly meetings serve as checkpoints for ongoing accessibility audits and community engagement. Victoria highlighted the difficulty in using the current audit reporting template, which organizes issues by WCAG principles rather than by page or feature, making duplication and collaboration harder. The team proposed adopting alternative auditing report templates to ease onboarding and improve efficiency. Inclusivity in community events was discussed, favoring panel discussions over workshops to engage both people with disabilities and allies without excluding anyone. The panel format supports diverse voices sharing their lived experience, which can increase awareness among stakeholders and lead to concrete accessibility improvements. Collaborations with Accessibility Nigeria for ChaosCon aim to enhance participation through sign language interpreters and transportation sponsorships. The group also discussed strategies to onboard developers into auditing roles, recognizing the need for self-directed learning due to the absence of mentorship. The ultimate goal is a welcoming, accessible CHAOSS community that empowers people with disabilities as contributors and leaders. --- ### 🗒️ Notes - **Introductions & Group Overview** - New member Daniel: Front-end dev with 6+ years, Lagos-based - Group diversity: Roles include developers, UX designers, advocates - Meeting cadence: Bi-weekly to maintain progress and engagement - **Accessibility Audit Challenges** - Victoria struggles with current WCAG-based audit report format - Difficulties in tracking duplicate issues and reporting efficiently - Proposal to adopt new audit report templates for clarity - **Onboarding and Collaboration** - Scheduling conflicts impede group discussions - Need for formal onboarding process, including sharing best practices - Encouragement for sharing personal audit methodologies - **Event Inclusion Strategies (ChaosCon)** - Panel discussions preferred over workshops for inclusivity - Include people with disabilities, accessibility advocates, and general contributors - Use panels to raise awareness of lived experiences and accessibility challenges - **Support for Participants with Disabilities** - Accessibility Nigeria providing sign language interpreters - Sponsorship and transport support to bring disabled participants to events - Need for broad accommodation across disability types (visual, motor, hearing) - **Developer Engagement & Accessibility Coding** - Lack of developers in auditing team creates self-learning necessity - Resources available in Slack channels for accessible coding guidance - Building an environment that welcomes people with disabilities as contributors - **Community Building** - Emphasis on creating a supportive and inclusive CHAOSS community - Encouraging collaboration among users with disabilities, developers, and advocates - Planning future meetings to finalize event details and audit procedures --- ## 📖 References: - CHAOSS Accessibility/Disability Inclusion WG Meeting, YouTube Transcript: https://www.youtube.com/watch?v=Kd_1zOiUWbY - WCAG Principles: https://www.w3.org/WAI/standards-guidelines/wcag/ - Accessibility Nigeria: https://accessibilitynigeria.org/ --- ## 🗣️ Paraphrase: 1. *Original:* "We are trying to create an environment for people with disability in this community... before now there's no specific community environment that accommodates them... so we are trying to create a specific one that accommodates people with disability." *Paraphrase:* - Summary: Minutes from this meeting can be found in this document: https://docs.google.com/document/d/1PMDWc6xMe0fNE7shxTK5_HE_ykRBG5w55_Zx5hvzsEY/edit?pli=1 - URL: https://www.youtube.com/watch?v=Kd_1zOiUWbY Right. So, hello everyone. Welcome to today's meeting. Um, welcome to our new member and attendee. So, hi Danielle. Please do a little introduction to um yeah, do a little introduction or do a full introduction, however you want to go about it. I'm sure we all are interested in knowing who our new member is. You have the microphone. Stage is your Yeah. Good evening. Evening everyone. Um my name is Daniel Shukura. Um I'm based in Lagos, Nigeria. Um I'm a front-end developer over six years of experience. Yeah, I enjoy building web and mobile application that works across all devices. Um I'm a new member here and I'm happy to be here. Great. Hold on. I feel like I called you a different name. Did I call you a different name? No, I think you said Daniel. Oh, okay. Great. Cuz sometimes my my mouth moves faster than my brain. Okay, Daniel. Welcome. We happy to have you. So, this is the um Chaos Dis Chaos Africa Disability Inclusion and Accessibility Group. So we have different people in different team um different fields. So since um you're new here it would be fine if we just go around and do an introduction as well so you get to know us too. I am Tori um Victoria Btoria for short. I am a product designer. I think I'm niching down into UX and I'm also an accessibility um advocate and niching into special being a specialist. So I am currently the co-lead I'm leading with Brian. Brian is not here currently. I'm the co-lead and maintainer of this working group and happy to meet you. So I'm going to be passing the mic to Hamza. Hi Hamza. Hi. Hi. Hi. Hi. My name is Hamza Maji. I'm a software developer. I based in Cano, Nigeria. So I just like everybody here, I'm also an open source advocate. Anything around open source really interests me and then I give it all my time as much as I can. Thank you. I yield the mic. Thank you. So um hi uh hi Vicki W cannot speak right now but I think she has typed her introduction in the chat. Hi Victoria. We have another Victoria here. Hi. Oh she left she left. Oh my god. Anyway, um I'm sure she'll be back probably. Uh so we are all working towards improving the accessibility of the chaos community and open source in general and tech in general basically. So that's what we do here. We look for ways to include people with disability in any activity that we're doing which is currently what we are trying to achieve every time we meet on Mondays. Our meetings are twice in a week um bi-weekly. So, you've looked at the agenda. We don't really have much on the agenda. So, if anybody has bi-weekly, sorry, bi-weekly. Bi-weekly. Once a week. Once a week. Once in two weeks. Once in two weeks. Okay. Okay. Yes. Every Monday. Once in two weeks. Yeah. So, we were not able to meet last two weeks. My bad. I was not really feeling good. So, but yeah, it's always once in two weeks. Victoria is back. Hi, Victoria. This we have another Victoria in the team. Hi, Victoria. Please do a little introduction. I'm sure Daniel will want to know you. Um, so I don't know if I'm the problem, but I can't hear Victoria. If you're speaking, your mic is muted. Okay. Or you have issues with your audio. That's fine. You can use the chat box. Okay. Connect your phone. Cool. Okay. So, while she connects with her phone, you can go over to the next thing we have on the agenda. Um, we want to talk about the audit that we are currently handling. So, there isn't much feedback from the audit so far. um because of clashing timing we are yet to meet but I think we are currently doing um reviews individually but we need to meet and bring our ideas together but yet to do that but individually we've been doing our work like going through the the um website and checking for doing some research it was at least I have been I think Victoria has been too but we are yet to meet to bring our ideas together to work together, right? And create more repositories on the issues that we have worked on together. I think that's what is pending so far. Uh hopefully we'll meet very soon. It's just clashing timelines. We'll look for a way to um agree on a timeline before our next meeting hopefully. But that's the feedback for the audit. Then for the research, we have made progress so far. Um we are we we are supposed to schedule this research for this week. Um we've gotten contact of people who are going to be in our first batch of user testing like they're going to be contributing to the user testing like the research process. Yeah. So um we've gotten contact of three people. So, we're looking to do it in four batches or three batches depending on our timing and the amount of people we have who are going to be interested because we want to hear we want to get feedback from different people like the experiences of different people. So, um, if you're going to be interested in the research, please send me a message on Slack and we don't want to crowd it anyway, but I know I'm going to be there and the people who are the accessibility audit team will be there too because we need to hear the um experiences of users firsthand to know which errors there are and which solutions we can provide. So if you want you're going to be interested in joining any of the batch batches of the richer, please send me a message on Slack and then we can put you on a date. Right. So I think that is it for the research. So um I don't know. Hi Vicki, this one your audio is bad. Have you been able to work on the report for the auditing? Have you had time to look at that? Okay. Can you hear me now? Yeah, perfect. We can hear you. So, you can start off with your introduction and then can continue with Yeah. Okay. So, yeah, first off, sorry for the mic issues. I don't know like I've just noticed that that's an issue I have with Zoom on like this is like the third meeting where I'm having issues with my mic on Zoom. So sorry about that. Um my name is Victoria and short form is not story or you can just call me Victoria to differentiate between the first story or my son that's fine. I'm a user experience designer with a focus on accessibility and uh recently I've been exploring the cloud native space. So that's that's my introduction. Then regarding what you just asked me now to uh I have gone through like I've tried to start the audit but I'm having issues with reporting the results of the audit. So there there are some confusions um with with the current reporting templates that we have you know when you let's say we want to start with the um chaos page to do like want to start auditing the chaos on page then I run lighthouse or asks on the page it bring out a list of issues under specific we can wag um principles. So how the current template is is structured is that we are finding issues we are reporting issues under each of these um wikag principles not based and then you now have to tag or mention where you are finding let's say you have uh what what's a common one color contrast issues so you now have to check all list all the color contrast issues that you found across all the pages on the website. Now that method is somehow difficult for me like it's yeah it's difficult for me because maybe I I may find issues on the homepage then go back to document it and see that someone else has already worked on it like someone someone has already found that issue and worked on it and it's like it's just difficult for me to navigate maybe I can't explain it without having to share my screen and I'm trying to update Zoom so it's take like it may take some time but if I'm able to get it to work I may share my screen to explain exactly what my issues are. And then I remember you asked also about the because there's a report that I used I I typically use when I'm doing audits that I find easier and I'm suggesting if you can also adopt that it's just a suggestion. So I also I'll share the link to that and then maybe if you can look at it during this call um I can just link and we can just look at it individually and share what we think about it. Oh great I think that's a great idea. I think this could be an issue especially for new members joining the team. You know you need to understand the procedure that the old that has been in use before you join in. And this is what why I was proposing like a meeting you myself and before you joined I was talking about how we've not been able to align our timings to meet meet up for the meeting as it has been clashing. Do you get? So but hopefully before the end of this week we can meet and actually understand the process at least on board you properly. Do you get so on board procedure? Yeah, that we are using and also you would also like fill us in on your own method using the report so that we can merge the both of them together and the work will be easier. Yeah. So hopefully before the end of the week we'll definitely meet you, myself and Ya. We've been planning to meet but we've been able to um I've been able to to speak to So we we would settle on a time that is going to be accommodating. We were supposed to meet this weekend but I guess activities activities. Yeah. So hopefully this week we'll be able to um have an open schedule where we can meet cuz this is actually very important. Yeah. So we can move forward. If we are not able to get more um more audits, we will not be able to create repositories for people to work on. Yes. So, all right. Um, great. So, I added something to our agenda. So, we're planning on having an activity as a team for Chaos Con, maybe a speaking engagement, maybe um a workshop or maybe a panel section session rather. So, what do we think? Because I feel like since we are also going to be inviting people with disabilities to this event because we have carried out a an outreach program, we are going to be including them in research. So the whole point is for them to be part of our community. So of course they going to be a part of the chaoscon event. They going to be there. So what kind of activity do you think is best for us to have? Are we thinking workshop? Are we thinking panel discussion? Are we thinking a session, a talk session? So talk sessions might seem a bit personal since it's either an individual speaker or two co-speakers, right? But with work with workshops, we it's it's more engaging with other people, right? Because the whole point is not just to tell them what we are doing at chaos.com but to have people more people join our work. So for me I think workshop might work either a workshop session or a panel discussion solely on open source and disability. So either of the two I don't know which one do we think works better but that's my like opinion. So in my opinion I will go I'm sorry once again in my opinion I will go with the panel session because uh when we tried a workshop so it would be centered around people living with disability so um people like people uh as in normal people people that doesn't have disability they feel like ah this is not for is for people with disability and then in that case we might missing the attention of one of the stakeholders because all we are doing is all we are advocating is like to include people living with disability in text space we feel that they they have been left behind and then uh not just only people with living with disability will attend the kos so uh normal people will also attend so that's and then among those in attendance we might have some act stakeholders who can make impact in this movement. So I believe panel session would be a better idea. Thank you. I yield the mic. I think I agree with you too on that because it was either that or workshop and I agree with the panel because we want to have everybody included in the conversation. I think Winnie Fred agrees as well. So Vicki Daniel what do we think this a discussion we used to have discussions in this meeting used to have conversation all of us used to talk so who's going first Daniel okay Vicki okay sorry yeah um so I I agree with what um Winnie Fred and Hamza and you have suggested so instead of having um someone just speak on a specific topic it would be better to have to like for the session to engaging to either a workshop or a panel session and like Hamza has pointed out a workshop might be might not be very inclusive because on the on the one hand he mentioned that there are people who may not have disabilities who may feel excluded from the conversation there's that and there's also if workshops are usually very handsome and I'm wondering how how feasible it would be to carry along everyone. Some people may not have may not come with their laptops and even if they have their like devices with them to to follow along. I'm I'm like I'm trying to imagine how possible it is to that we we have a a workshop that both people with disabilities and those who do not have like can follow through on. So the next viable option is the panel session and I'm I'm yeah I'm I'm agreeing with that and I'm suggesting we have a mix of h now maybe it's too early to decide but a suggestion would be like now now I'm thinking of maybe not a mix maybe we since we're going to do the audit like an actual like a qualitative a man we say man what's yeah a manual audit where we have people disabilities use website. So figure out where they're having issues. Maybe the panel session will be them talking about their experience not just to the auditors now but to a larger audience. So, so in that way they're creating awareness about the issues that these people face using digital products and stakeholders like mentioned who are present in the audience will also be aware of these things and find ways to can find ways to resolve them or try to resolve them. So that's my own opinion. Great. I agree with you as well. Is it my hand that is up? Oh, I agree with you as well. Um, hi Danielle. Do you have anything to add to the conversation? Yeah. Hi Tori. Hi. Agree with everyone. Um, a panel a panel session will be better. It will be more the conversation will be more diverse and you can stretch it to different direction. And like I think Vicki said, so I don't know what the how is like it's my first time. I don't know how it's going to look like but like you mentioned some people with disability will be joining the community. So I think it would be also be nice to include them in a conversation or in the panel session. Let's hear their experience. Yeah. And if we are going to I don't know how it's being organized but like um AMSA said it should not be something that sounds like it's excluding people without disability should be something that will carry everybody along coming to learn. Yeah. Thank you. Great. So, um, I was supposed to pitch this to the organizing team, the chaos organizing team, cuz I spoke to Ruth and she was like, um, a way to pitch this is to join in the community call and talk about it. So I think me being unavailable or busy was a good thing because it gave us an opportunity to run the idea by the team and then we are in agreement so that next week during the community call I can pitch this and say okay the team or the group the group agreed that the pal discussion will be um the best and then we when we pitch it I think we need more we need more details. So um pa discussion great we need a topic what topic do we want our conversation to be you know our next meeting is after the community call I think we might have to discuss it now so that we have something tangible to give the team the planning theme right so what topic are we going to so we've agreed panel discussion what topic do we want our panel discussion how many people do we want in the panel discussion discussion and what tone do we have it do we want the panel discussion to have so let's start with the topic what do we want what do we want to talk about I mean the mic is for everybody you should no let me let me allow Induka to go first. Okay. Hi Vicki. They say we should leave the stage for you. Why? Why? We should leave the stage for you. So go on. Yeah. Because because I know you are the best at what you do. So you definitely have something. Wow. That I love that. It's good to know that everybody recognizes the good work that you do. I love it. He's well. Okay. Yeah. So yeah. So I have two ideas. I've already mentioned one earlier that is having having them come to talk about their experience using chaos. Okay. What issues that they like the issues that they experience navigating through the chaos website and stuff like that. But besides the website or like contributing to Okay. either that maybe make it specific to chaos or broader to the open source community. What challenges do they have committing to contributing since chaos? Maybe we should just narrow it down to just chaos challenges that they have contributing to the chaos community from using the websites to to the to the tools that Chaos uses in meetings and stuff like that. That that's one. And second, we could make it like a a day in the life of a person. I know it's too long, but like it just it just came to me. Maybe have them talk about like regular things that most people overlook. Most people who do not have disabilities overlook in their day-to-day interaction with digital products that are pain points or that challenging for people with disabilities. Okay. Okay. I think I agree with you. The thing is at some point we will have to ask them their experience, right? Because I feel like in this um pa discussion we have we have at least one person who has a disability right? Yes. Maybe one or two people who have disability, different disabilities, maybe a blind user and a deaf user or a blind user and a user with motor disability depend at least one person who has a disability and they will talk about their experiences contributing to chaos. So now we don't want it to be a case where we put put chaos on the spot, right? Because they're going to be speaking freely their experiences. Nobody's going to Right. So, and we know that we still have a whole lot of work to do, right, with our implementing accessibility in chaos. We're not there yet. So, we don't want a case where because I'm sure at some point the the the session might be recorded or streamed or I don't know how the team is doing it, but we don't want a case where um chaos is laid bare and people start to nitpick. So just talk about their experiences because the people who are going to invite are people who are going to have contributed to chaos at some point. So let's say maybe members of the um of the user testing who are okay with being on the limelight like being having camera in their face or talking in public. Yeah. They talk about their and some ways they have contributed to chaos as I think that would be great. Then we also have people who are contributing to chaos who do not have disabilities but who are working towards improving the accessibility of the chaos project right either in event or in the in the projects that chaos has. So we can bring a developer or a designer who is either designing or coding for accessibility in chaos right somebody who is implementing accessibility or someone who is auditing anybody. Then we'll also we also bring um um a general user who is benefiting from accessibility right so we trying to like show cop cut effect sort of so a user who has disability a user who a contributor who does not have a disability but who benefit from disability and someone who is actively trying to implement accessibility something like that. I don't know if it makes sense. Yeah. Yeah. It makes Yeah. So, we can have like maybe three people. We don't have then a host. Just three people and a host. And I'm thinking maybe we can try um chaos projects, contributing to chaos or or accessibility in chaos or something. Yeah. including inclusion in chaos, including accessibility in I know we'll figure it out at some point. Maybe we'll have to like meet before the end of the week because community call is next week. So I'll probably be in the group we will brainstorm in the in the Slack channel, right? To pick it perfect. Yeah. For it even if you cannot come up with it right now. Yeah. For me like uh the topic is not necessary. We shouldn't like push oursel to the extreme end to come up with the topic. Yeah. So, uh because we have limited time and then uh the case is far away from today. So, what we should focus is like the idea on how the final sessions would be something like for example um we might just assume we might just because um some of us here are not are not physically challenged and and doesn't have disability and we are building something for people with disabilities. So we should give them time and hear from them to see what kind of the challenges are. If you can recall from um last year workshop that I hosted uh most of their general feedback was um they feel they they are like ashamed of their challenges and then some sometimes uh some group set of people like um disregard them like they don't give them fair chance to be into tech because some of them are physically challenges some of them are visually impaired and then some of them have hearing impediment as well. So it's different is dynamic uh set of community and then you are view you are building something that will carry them all along. So you should carefully uh think when you are bringing a topic you might bring a topic that will benefit only people that have visual impediment. Then what about those with physically challenge? Then how about this that have earing treatment? So it's something that we that will accommodate like 90% if not 100 to the majority of the disability community. So in nutshell what I'm trying to say uh we should continue brainstorming on this election after this meeting and come up with the topic and the idea of what kind of a thing that will accommodate all the set of people living with disability. I don't know if I'm making sense or not but this is what I feel based on my own interaction. Yes. Yes you are. You're making sense. You can always brainstorm. So I was just thinking if the idea of bringing three different um people who have three different experience in the group chat is acceptable accepted rather we can add it to the idea that we're looking to pitch right because we need to even while we like try to brainstorm we need to pitch the idea. So this is the idea we have so far. We can continue to pitch in the group. So we have a person or two persons with disabilities. Um someone who is working towards improving accessibility. It could be anything. It could be documentation. It could be design. It could be coding whatever it is. Then we can have someone who just generally contributes and benefits from accessibility implementations. Right? So, oh definitely. Yes. Um, Accessibility Nigeria will be collaborating with Chaos Con. So, there will be sign language interpreters at the event. Very, very important. One thing that I understand, one thing that I understand now is that even you don't have um people living with disability in attendance at your event, it is very important to have sign language interpretation. Yes. Especially when you're making Yeah. Even if you are like um even if you're not streaming or you are saving that, you are recording it for future reference. So it's a nice idea to have a sign language in your future. Yes, there will be. I'm already speaking to Ruth about it. We are supposed to finalize on that as well and hopefully we extend it to Oscar first. So that's the idea. Um I don't think there's any other thing we have pending unless we have concerns that we want to talk about. But please let us fill the form. Please let us I say let us edit the minutes and put our names. Hold on. Let me so that we know where we're putting our names. Yeah. So, let's just put our names. Does anybody have any other thing they would want to talk about? Yeah. So, I there was this thing that is bothering me. uh say for example um because I'm a man of a disability community here in my community because my one interaction with them and then I I engage myself in their activities in their activities fully. So when the chaos con arrives, so are we getting like a kind of support to bring like one of them O2 down to Lagos in order to ask to attend the PS event. I don't know if it would be amazing if we can do that. It would be amazing if we can do that. But then we are also checking for convenience. We're also checking for security. But if we can do that, I think I will speak to Ruth. Of course, like like I said, accessibility Nigeria will try to bring people from Lagos, but I don't know for instate. Oh. Oh, that would be fine. That would be fine. So, what we usually do is we collaborate with communities that hosting event and then we offer like a transportation sponsorship to people with disabilities so that they can be able to attend. And then we provide sign language interpreters as well. So accessibility Nigeria works with we are planning on doing that. That's part of the services that we offer. But I don't know for intra states. So where from are you trying to move them from another state to Lagos? Yeah. For chaos corn event. Uh okay. Okay. Not not them. Uh let's say one person. Okay. one person from yeah one person will be okay because like how they do their thing here they categorize the same into cluster for example visually those that have a visually impaired related like those with 75% blindness totally blind albinism and whatever they're in the same category those that are physically challenging in one category and then those that have hearing impairment also in another category So uh budget wise we know how it is in the world not just Nigeria it could not be possible. So uh I think um if it is possible so uh we can seek for sponsorship for one person that is like super active in the community and have uh general um experience in all the three categories. Right. Right. Speaking of active Thinking speaking of active also want people from your community to be part of the user testing. If you can have one or two users who are blind users to join it would love that so that when they are coming they would be coming with open source experience from chaos as well a lot of sense. Yes. Yes. So I will reach out to you about that and then maybe I can get a few contacts to reach out to them and they'll be part of the batch. And then for the um sponsorship um I will speak to Ruth about it and I'll also speak to my co-artner in accessibility since we are bringing one person. Let's see if they can be included in this sponsorship. So we'll just be in communications to know how that's going to work. That's nice. That's perfect. Okay. So, um, is there anything we are missing out? Not from my own end. I think we've covered everything. So, one more thing, Torina. Okay. You haven't sh you haven't shared the meeting though so that we can mark our Oh, I did, but let me share it again though. I did before. I think you probably did not. Well, hold on. Let me just Yeah, I think that's the only thing that remain correct me if I wrong. Okay. So, uh before we leave, hi um um Danielle. So, we happy to have you on our team. What part of the work would you be interested in contributing to? I see you're a developer, which is actually really nice. So um would you want to work with the uh auditing team to make uh accessibility implementations like is that your field? Is accessibility auditing your field or what part of what or would you want to be part of the event planners or something? I mean we want you to an active member part of us as well. So, okay. I was I was even about asking how do I start how do I contribute since I'm a new member and what's the process? But so I guess I'm reading your mind. Great. You're reading my mind. Yeah. So um I am a developer and I would like to like get to know how I can contribute um from the coding aspect and if there's any other aspects like currently you only mentioned two aspect which is the um audit part and um the event planning part. So if there other aspects so that might be of interest. Yeah. But I also be interested in you know seeing how the audit works and contributing my own kota. Okay. Great. So the thing now about being part of the auditing is there is no teacher. Yeah. We don't even have a developer in the auditing team. That which is why I would love you to be part of the auditing team. So we do not have a developer here that you can under stududy or probably learn from. So everything you're going to be doing I think it's still going to be part of your your develop your developers path or career stuff you have to like figure out figure it out for yourself how you already know how to code. So it's basically ensuring that you use the correct HTML semantic HTML semantics yeah for coding. So um it's not that easy. You have to actually know how to audit. I think that's where you doing your own personal research comes in. I mean I think on the repository there are materials you can look at that probably help you to know how to implement accessibility in coding if you get what I mean. I mean you already know how to code. It's just how to implement accessibility in the coding. So you can check out the repository. I think it's in the link in our group like is in the group Slack channel. Yeah, I think I'll check if I have issues right now. What we majorly are trying to do is we are trying to create an environment for people with disability in this community in this chaos community right cuz before now there's no specific community environment that that accommodates them right so we trying to create a specific one that accommodates people with disability which is why we are trying to create issues that people with disabilities can contribute to if you get what I with the whole user testing thing and them joining the community events and all of that. So that's where we are at now. So I'm sure there are also other um so for for a developer that's majorly where you feature in yeah implementing accessibility in quotes right but you can also join us in other community work like um like um maybe document you don't do documentation so for a developer let's maybe you want to like switch things you want to do so I don't know if what I'm saying is making sense but yeah just a reminder I'm also a developer too and Victoria also look like a developer she is though she's transitioning into cloud so she's a develop so see you have we're not like okay you you have developers you can study from so just reach out to Vicki and she will on board you I'm sorry for putting you on the spot But yeah. Yeah, I think that's it. Okay, I think this is where we come to the end of I reach out to Victoria. Yeah, I know how to get started. I've tried auditing before or Yeah. But majorly you are auditing the chaos website, right? Or to which what what's um is it chaos website for auditing? Yeah. So the projects they have is um the chaos website, the AOS project, the badging project, but we are starting with the chaos website. Okay. Okay, that's great. Okay, that's fine. Glad to be here. Okay, so thank you everyone for joining in, taking our time from a busy schedule to join our meeting. I'm happy it was very very productive. Um we have learned a lot. We have a lot to do. Hopefully before our next meeting we'll have a lot of feedback to give. So I'll see you I'll see everybody in two weeks. Thank you. And if you've not written your name, please do for documentation purposes. Thank you. Bye. Yeah. Bye. Bye. Good talk. We need friends., CHAOSS Accessibility/Disability Inclusion WG, June 2, 2025, CHAOSS, 01jy1twhvhzw21q51zfp38rmc6.