CHAOSS AccessibilityDisability Inclusion WG, April 20, 2026

CHAOSS Accessibility/Disability Inclusion WG, April 20, 2026 ![rw-book-cover](https://img.youtube.com/vi/e8Thzd4Xmx4/maxresdefault.jpg) 🔗 **Source:** [CHAOSS Accessibility/Disability Inclusion WG, April 20, 2026](https://www.youtube.com/watch?v=e8Thzd4Xmx4) > [!note]+ Document Notes > tags: #accessibility #disability-inclusion #open-source #community-building #chaos #python #africa > author: CHAOSS Accessibility/Disability Inclusion Working Group > source: YouTube > reference: https://www.youtube.com/watch?v=e8Thzd4Xmx4 > date created: 2024-12-19 10:30 > > # 🏷️ Title: CHAOSS Accessibility/Disability Inclusion WG Meeting - April 2026 Planning Session >  ## 🧰 Action Inbox - [H1] Reach out to Elizabeth about GAAD collaboration opportunities — build partnership with Global Accessibility Awareness Day community #accessibility - [H2] Contact PyCon Africa organizers about accessibility partnership — explore sponsorship or workshop opportunities #python #africa - [H3] Plan June webinar on AI tools for disability accessibility — feature Kirrion's experience building custom tools #ai #webinar ## 🧭 Table of Contents - [[#📝 Summary]] - [[#📖 Main Content]] - [[#🗒️ Notes]] - [[#📚 References]] - [[#🗣️ Paraphrase]] - [[#📰 Newsletter]] - [[#✅ Action Items]] - [[#🧪 Hypotheses]] - [[#📊 Methodology]] - [[#❓ Questions]] - [[#🔮 Future Research]] - [[#💡 Implications]] - [[#🧠 Learning Styles Assessment]] - [[#📊 Accessibility Assessment]] - [[#🌍 DEIB Assessment]] - [[#✅ Logical Validity]] - [[#🛡️ DARVO Analysis]] - [[#🎯 Conclusion]] ### 🔗 References - [CHAOSS Project](https://chaoss.community) - [Global Accessibility Awareness Day](https://accessibility.day) ## 📝 Summary - CHAOSS Accessibility/Disability Inclusion Working Group met to plan 2026 activities and partnerships - Group discussed strategies for PyCon Africa collaboration, physical events, and webinar programming - New member Kirrion joined, bringing experience in building AI-powered accessibility tools - Focus on creating impact through workshops and community building rather than just presentations - Plans include partnerships with Global Accessibility Awareness Day community and disability organizations in Uganda ## 📖 Main Content The CHAOSS Accessibility/Disability Inclusion Working Group held their planning meeting for 2026, focusing on strategic partnerships and community impact initiatives. The discussion centered around moving beyond simple awareness talks to creating tangible educational opportunities and community connections for people with disabilities in open source. Key strategic directions include partnering with established conferences like PyCon Africa as accessibility sponsors, developing workshops that teach practical skills, and creating panels featuring disabled community members sharing their experiences in tech and open source. The group emphasized the importance of authentic representation, having people with disabilities speak about their own experiences rather than having others speak on their behalf. This approach aims to foster genuine connections and demonstrate real pathways for participation in open source communities. ## 🗒️ Notes #### ⏱️ [00:00](https://youtu.be/e8Thzd4Xmx4?t=0) — [H1] Conference Strategy Discussion - Key idea: Focus on workshops over lightning talks for meaningful impact - Evidence: "We do not want to talk about what we do really but we want to make impact" #### ⏱️ [03:45](https://youtu.be/e8Thzd4Xmx4?t=225) — [H2] PyCon Africa Partnership Plans - Key idea: Explore accessibility partnership rather than just speaking slots - Evidence: "We can send an email to be like accessibility partners like we can badge the event" #### ⏱️ [07:30](https://youtu.be/e8Thzd4Xmx4?t=450) — [H1] Community Building Goals - Key idea: End goal is getting people with disabilities contributing to open source - Evidence: "The end goal of having chaos accessibility team is to ensure that opensource in chaos and open source global is accessible to people with disabilities" #### ⏱️ [12:15](https://youtu.be/e8Thzd4Xmx4?t=735) — [H2] Authentic Representation Strategy - Key idea: Have disabled people speak about their own experiences - Evidence: "We can also do one where we have the community themselves, people with disability come and speak about how or what they've been doing in tech" #### ⏱️ [18:20](https://youtu.be/e8Thzd4Xmx4?t=1100) — [H3] Impact Over Scale Philosophy - Key idea: Quality connections matter more than large audiences - Evidence: "If you can reach out to two three people who are genuinely interested in tech and genuinely interested in being part of open source that works" #### ⏱️ [25:10](https://youtu.be/e8Thzd4Xmx4?t=1510) — [H2] Strategic Event Timing - Key idea: Align physical events with disability celebration days - Evidence: "It would be smart to strategize events for them to happen on days that are celebration days or months that are celebration month especially as channels for people with disability" #### ⏱️ [28:45](https://youtu.be/e8Thzd4Xmx4?t=1725) — [H1] Elizabeth Partnership Opportunity - Key idea: Leverage Elizabeth's board position with Global Accessibility Awareness community - Evidence: "Elizabeth is now one of the board of directors with GAAD global accessibility awareness community" #### ⏱️ [35:30](https://youtu.be/e8Thzd4Xmx4?t=2130) — [H1] Kirrion Introduction and Tools - Key idea: New member brings experience building AI accessibility tools - Evidence: "I have used AI to build my own tools now because some of them a lot of tools for people with disabilities are built with people asking people with disabilities what they want" #### ⏱️ [42:15](https://youtu.be/e8Thzd4Xmx4?t=2535) — [H2] Custom Tool Development Philosophy - Key idea: Building tools by disabled people for disabled people eliminates disconnect - Evidence: "Tools for people with disabilities are built with people asking people with disabilities what they want. So there's already one level of disconnect" #### ⏱️ [47:50](https://youtu.be/e8Thzd4Xmx4?t=2870) — [H3] Speed Equality Principle - Key idea: Accessibility tools should bring everyone to the same working speed - Evidence: "What you're doing is you're just trying to make it so that everyone's as fast as everyone else" #### ⏱️ [52:30](https://youtu.be/e8Thzd4Xmx4?t=3150) — [H2] Website Accessibility Audit Plan - Key idea: Start accessibility work with internal CHAOSS properties - Evidence: "We also want to start from home per se. So from our websites to know if our website are accessible" #### ⏱️ [58:00](https://youtu.be/e8Thzd4Xmx4?t=3480) — [H3] Black Python Devs Collaboration - Key idea: New opportunities for support through Black Python Devs organization - Evidence: "I'm now also original executor for black python devs so if you're organizing something and it relates to Python I can find ways to get support" ## 📚 References - [CHAOSS Community](https://chaoss.community/) - [PyCon Africa](https://pycon.africa/) - [Global Accessibility Awareness Day](https://accessibility.day/) - [Black Python Devs](https://blackpythondevs.com/) ## 🗣️ Paraphrase - The working group prioritizes creating educational workshops and authentic community connections over simple awareness presentations - Strategic partnerships with established conferences and accessibility organizations can amplify impact while reducing resource requirements - Having disabled people speak about their own experiences creates more meaningful connections than having allies speak on their behalf ## 📰 Newsletter **CHAOSS Accessibility Working Group Charts 2026 Strategy** The CHAOSS Accessibility/Disability Inclusion Working Group is planning an impactful 2026 with strategic partnerships and community-driven initiatives. Rather than focusing on awareness talks, they're prioritizing hands-on workshops and authentic representation by disabled community members sharing their open source journeys. Key initiatives include collaborating with PyCon Africa as accessibility partners, leveraging Global Accessibility Awareness Day connections, and featuring developers who build AI-powered accessibility tools. The group emphasizes quality community connections over large audiences, aiming to genuinely onboard disabled developers into open source contribution. This approach aligns perfectly with WordPress's commitment to accessibility and inclusive community building. Resources: [CHAOSS Community](https://chaoss.community/), [Global Accessibility Awareness Day](https://accessibility.day/), [Web Accessibility Guidelines](https://www.w3.org/WAI/WCAG21/quickref/) ## ✅ Action Items #### Community - Maintainers: develop accessibility review templates for project onboarding - Contributors: create first-issue programs specifically tagged for accessibility improvements - Sponsors: fund travel support for disabled speakers at conferences - Ecosystem: establish cross-project accessibility coordination working group #### WordPress - Accessibility: conduct WCAG audits of CHAOSS websites and tools - Community: develop mentorship program connecting disabled developers with open source projects - Training: create lesson plans for accessibility-focused development workshops - Documentation: build accessibility contributor guides and best practices - Design: implement accessibility-first design tokens and review processes #### OSPO - Community Engagement: fund partnerships between accessibility organizations and open source conferences - Strategic Alignment: establish accessibility KPIs for open source project health metrics - Developer Support: provide accessibility testing tools and training resources ## 🧪 Hypotheses - Strategic partnerships with established conferences yield higher community impact than standalone events - Authentic representation by disabled speakers creates stronger community connections than ally advocacy - AI-powered accessibility tools built by disabled developers better meet user needs than traditional approaches - Timing events around disability awareness celebrations increases engagement and attendance ### 📊 Methodology - Survey disabled developers about barriers to open source contribution before and after workshops - Track conference partnership outcomes through speaker feedback and community growth metrics - Measure accessibility tool adoption rates when built by disabled developers versus external teams ### ❓ Questions - How can open source projects systematically identify and remove barriers for disabled contributors? - What partnership models between accessibility organizations and tech conferences create the most sustainable impact? - How do AI-powered accessibility tools change the development workflow for disabled programmers? ### 🔮 Future Research - Long-term impact assessment of disability inclusion initiatives on open source project health - Comparative analysis of accessibility tool effectiveness across different disability types - Economic impact study of inclusive design practices on open source software adoption ### 💡 Implications - Practice: Development teams need disabled developers involved in accessibility tool creation - Policy: Conference organizing requires accessibility partnership frameworks and speaker support - Education: Accessibility training must move beyond compliance to authentic community inclusion - Funding: Disability inclusion initiatives require sustained investment in travel support and tool development ### 🧠 Learning Styles Assessment Reading level estimate: 12th grade #### 👀 Visual learners - Present: Meeting structure discussion, partnership diagrams implied - Improve: Conference collaboration flowcharts, accessibility audit visualization #### 🔊 Aural learners - Present: Video meeting format with natural discussion flow - Improve: Podcast episodes featuring disabled developers, recorded workshops #### 🗣️ Verbal learners - Present: Clear definitions of partnership types, terminology explanation - Improve: Glossary of accessibility terms, comparative examples #### 🧩 Kinesthetic learners - Present: Workshop planning with hands-on components mentioned - Improve: Interactive accessibility testing labs, tool building exercises #### 🧠 Logical learners - Present: Strategic decision trees for event planning - Improve: Impact measurement frameworks, partnership evaluation matrices #### 🧑‍🤝‍🧑 Social learners - Present: Community building focus, collaborative planning - Improve: Peer mentoring programs, group accessibility reviews #### 🧘‍♀️ Solitary learners - Present: Individual tool development stories - Improve: Self-assessment accessibility checklists, personal reflection prompts #### 🌿 Naturalistic learners - Present: Organic community growth approaches - Improve: Ecosystem thinking about accessibility across projects ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Meeting transcript with clear speaker identification - Improve: Structured headings for topic transitions, landmark navigation #### Keyboard navigation - Present: Standard video controls accessible via keyboard - Improve: Timestamped navigation shortcuts, chapter markers #### Contrast and readability - Present: Clear audio with distinct voices - Improve: Visual transcript with high contrast formatting #### Text resizing and reflow - Present: Transcript can be enlarged and reflowed - Improve: Responsive transcript layout optimization #### Media and captions - Present: Full transcript provided for video content - Improve: Synchronized captions with speaker identification #### Forms and interactions - Present: Simple video interface - Improve: Accessible video chapter navigation ### 🌍 DEIB Assessment #### Cultural breadth - Present: African focus with Nigeria, Uganda, Canada representation - Improve: Broader geographic inclusion, multiple language support #### Inclusive language - Present: Respectful disability terminology discussion - Improve: Consistent person-first vs identity-first language guidelines #### Neurodiversity support - Present: Structured meeting format with clear agendas - Improve: Multiple participation options, processing time accommodation #### Representation - Present: Disabled people speaking about their own experiences - Improve: Intersectional representation across disability types #### Psychological safety - Present: Welcoming approach to new members, supportive tone - Improve: Explicit community guidelines, conflict resolution processes ### ✅ Logical Validity #### Strong reasoning - Deductive strength: Partnership strategy follows from community impact goals - Inductive strength: Tool development approach based on user experience patterns - Causal reasoning: Authentic representation leads to stronger community connections - Analogical strength: Conference partnerships compared to established open source collaboration models #### Fallacies - Appeal to authority: Assuming GAAD board position automatically enables collaboration (minor) - False dichotomy: Workshops vs talks presented as only options (addressed by exploring partnerships) #### Tone of voice - Overall tone: Collaborative and strategic, with emphasis on practical impact over theory ### 🛡️ DARVO Analysis - Deny: No denial patterns present - Attack: No attacking behavior observed - Reverse victim/offender: No reversal patterns - Emotional cues and rhetoric: Positive, solution-focused language throughout ## 🎯 Conclusion The CHAOSS Accessibility/Disability Inclusion Working Group demonstrates strategic thinking by prioritizing authentic community engagement over traditional awareness approaches. Their emphasis on partnerships, disabled leadership, and practical skill-building workshops offers a model for meaningful accessibility inclusion in open source communities. The integration of AI-powered tool development by disabled developers represents an innovative approach to addressing accessibility barriers while building technical capacity within the community. ## 🧱 Refactor Appendix ### 📚 Literature Split Pad ### [H1] Authentic representation creates stronger community connections > [!quote] CHAOSS Accessibility WG Meeting by CHAOSS Community via YouTube. Published 2026-04-20. Accessed 2024-12-19. > "They'll be able to relate more when they see person that is actually disabled." Partnership strategy emphasizing disabled speakers over ally advocacy. [view highlight](https://youtu.be/e8Thzd4Xmx4#H1) #xref #articleseed ID:rw_chaoss_authentic_rep ### [H2] Impact measurement focuses on quality over scale > [!quote] CHAOSS Accessibility WG Meeting > "If you can reach out to two three people who are genuinely interested that works." Community building philosophy prioritizing meaningful connections over large audiences. [view highlight](https://youtu.be/e8Thzd4Xmx4#H2) #xref ID:rw_chaoss_quality_impact --- ### 🔖 Atomic Split Pad (Zettel Candidates) #### [Z1] Accessibility tools built by disabled developers eliminate design disconnect - Scope: Software development for disability accommodation - Pointer: 35:30 timestamp discussion - Links: [[User-Centered-Design]] [[Accessibility-Tools]] #### [Z2] Strategic event timing amplifies accessibility awareness impact - Scope: Community event planning and disability celebration coordination - Pointer: 25:10 strategic timing discussion - Links: [[Event-Planning]] [[Disability-Awareness]] --- ### ✏️ Fleeting Queue - [F1] Research Global Accessibility Awareness Day partnership opportunities — Elizabeth connection #fleeting #inbox - [F2] Document AI accessibility tool development patterns — Kirrion's approach #fleeting #inbox - [F --- ## Full Transcript [00:00] It doesn't work that way. [00:02] >> Okay. [00:04] >> So, I was able to figure it out. Yeah. [00:07] >> Okay. [00:08] >> We're back. [00:08] >> That's why. [00:09] >> Yeah. [00:10] >> Okay. So, if that always doesn't work, [00:13] then we always just submit talks and [00:16] maybe also submit like sprints and we [00:18] hope that they get accepted. But I think [00:20] we've just missed the window for PON [00:22] Africa cuz Pon Africa proposals just [00:24] closed last this Monday. I think last on [00:27] Sunday. So we might not be able to [00:31] >> to do to to do maybe submit a talk or [00:34] anything unless maybe now Chaos Africa [00:36] decides to sponsor the event then we can [00:38] be able to maybe now come in and [00:42] support. But I think those are the ways [00:44] I think I can get ideas cuz I think one [00:47] of the things is we do not want to like [00:50] um we do not want to uh talk about what [00:53] we do really but we want to make impact. [00:55] So it it don't make sense to get a [00:56] lightning talk. where I just go and talk [00:58] about what I do. I actually want people [01:01] to learn what I do. So if I get a [01:02] workshop to teach people accessibility [01:05] that makes more sense compared to say [01:07] hey join the community you know do and [01:10] most of them rarely even end up joining. [01:12] >> So I feel like that is always more [01:14] impactful [01:15] >> and you can even mention something like [01:16] oh I trained a couple of number of [01:18] people in this and this and this that [01:21] makes no sense. So that's my thinking [01:22] around it. So, it's either we do a [01:24] workshop or we partner with them as [01:26] accessibility partners. I think that's [01:28] something they'll be open if you just [01:30] send an email to the organizers. Good [01:32] thing I'm part of the organizing team [01:33] for PCON Africa this year. [01:35] >> So, [01:35] >> Oh, great. [01:37] >> We can send an email to be like [01:38] accessibility partners like we can badge [01:40] the event, we can do what and then once [01:43] we do that [01:44] >> so I think we have different ideas. So, [01:47] let me just start writing them. [01:49] >> All right. [01:49] >> All right. Um so which country will are [01:52] you [01:54] um having a blast? [01:55] >> It's happening in Uganda this year. [01:58] >> Uganda. Okay. Um [02:02] >> so you know at the end of the day the [02:06] end goal of having chaos accessibility [02:10] team is to ensure that opensource [02:15] in chaos and open source global is [02:18] accessible to people with disabilities [02:20] in terms of them also contributing right [02:23] building products and all of that. So we [02:26] should also bear in mind that while we [02:28] collaborate with these people we want to [02:33] put that end game in mind. [02:36] >> So while we collaborating are we trying [02:39] to meet their community for people with [02:41] disabilities? Are we trying to um tell [02:45] them that they also can contribute to [02:47] open thoughts in chaos and open source [02:50] in general? um we're trying to tell them [02:56] how they can contribute to open source [02:59] as it concerns accessibility and most [03:02] importantly we are creating awareness [03:03] for people with disabilities [03:06] in open source. So we're also talking to [03:08] people who do not have disabilities [03:11] who have either open source communities [03:13] or are building open source software or [03:15] product [03:16] >> to include disability accessibility and [03:21] in general people with disability why [03:22] they're trying to either build a [03:24] community or build a software right so [03:28] in this case how do we approach the [03:32] community in Uganda do we meet with [03:35] people with disabilities in Uganda [03:37] Are they new to tech? Are we trying to [03:40] like do a workshop where we're [03:41] introducing [03:43] people with disabilities in Uganda to [03:46] tech and to open source in general? [03:49] Let's take Chaos Con for instance. Chaos [03:51] Con Africa that we did where there was [03:53] like a workshop specifically for people [03:55] with disabilities where [03:58] um few people with one person with [04:00] disability came and spoke about using [04:03] open source software and um being part [04:07] of the open source community and how it [04:09] benefits her and how it has been useful [04:12] to her and the community in general. So [04:13] is that what we want to do in Pyon? I [04:16] think it would be a great idea aside [04:19] having a personal talk where we come and [04:20] talk about accessibility and what we do [04:23] in open source uh what we do in tech as [04:26] it concerns accessibility and people [04:28] with disabilities. We can also do one [04:30] where we have the community themselves, [04:33] people with disability come and speak [04:35] about how or what they've been doing in [04:37] tech and how they can be part of the [04:41] open source space either building the [04:43] open source community or building open [04:46] source software because that's like the [04:47] end goal. The end goal is we want people [04:49] with disabilities to be building [04:50] software technology. We want them to be [04:53] part of the open source community, [04:55] right? So I mean since you're part of [04:57] the organizers we can talk about that [04:59] like a panel session or a conversation [05:02] where it helps us to not only reach out [05:05] to um people with disabilities [05:11] in open source but the people with [05:14] disabilities community in Uganda I don't [05:16] know if that has ever been touched for [05:18] people with disabilities who want to get [05:20] into tech right M [05:24] >> because the access now that we are [05:27] global now that chaos accessibility [05:30] inclusion team is no longer just Africa [05:33] or [05:34] >> making it look like it's just Nigeria or [05:36] just Kenya we want more African people [05:39] more African community to be part of the [05:42] group right we go from Africa we spread [05:45] so if this can be an opportunity for us [05:47] to reach out to to people with [05:49] disabilities in Uganda [05:52] >> the community. We form like a community. [05:54] It doesn't for me personally I'm always [05:56] about impact like it doesn't have to you [05:58] don't have to have a crowd. If you can [06:00] reach out to two three people who are [06:02] genuinely interested in tech and [06:03] genuinely interested in being part of [06:05] open source genuinely interested in [06:07] building something in open source that [06:10] works. If that workshop or the panel [06:12] session is going to achieve that that is [06:14] amazing that's impact right. So if we [06:16] can actually do that for Python I think [06:18] that would be great. So I've been [06:20] talking for a long time. Please, anybody [06:22] has any other idea? [06:32] I know Winfred blessing [06:36] I don't know who else is in the meeting [06:37] because I can't see the participants but [06:42] >> so yeah I agree with bringing [06:46] um people with disabilities to come out [06:48] so it doesn't look like like you [06:50] mentioned that we are not really [06:52] bringing they will not be able I they'll [06:54] be able to relate more when they see [06:56] person that is actually disabled. Sorry [06:59] for the word like person with [07:01] disability. [07:02] >> It's not a slow you can say disabled. [07:05] Disabled is fine. You can say disabled [07:07] people. I mean notable. I think they'll [07:10] be able to relate more compared to [07:13] people who are not having disability [07:16] speaking. [07:17] they they might be able to say oh yeah [07:20] this person is actually disability and [07:23] they they they might even tend to want [07:25] to speak to such person more to open up [07:29] faster compared to someone who's lost. [07:32] So I agree with that way it makes it [07:35] easy. They can even be like um the [07:37] spokesperson for the um community at the [07:41] end of the day to say oh I have this [07:43] particular community that is inclusive [07:46] and join the community if based on their [07:49] experience if they're able to relate [07:51] more. [07:54] >> So I I agree with [08:01] okay that's fine that's that's okay. I [08:04] don't know. Can someone else be writing [08:05] the meeting notes? Cuz I feel like [08:06] there's a lot I'm missing out um from [08:09] that. [08:11] I don't know if [08:14] you always help us. Please help us with [08:16] the meeting notes. It's true. Oh my god. [08:18] I actually forgot to send the meeting. [08:20] >> Can you share the link? [08:23] >> Yeah, I was going to say that the [08:25] meeting minutes for the Yeah, let me [08:27] just quickly show that. Uh [08:40] I was going to ask you how was um is it [08:45] is it Pyon Namibia? How was Pyon [08:47] Namibia? [08:48] >> Oh, Pon Namibia was lovely. Definitely [08:51] going next year. I love how organized [08:53] they are. They already have a website [08:55] for next year by the way. So if you want [08:58] to go next supposed to attend but [09:03] >> um [09:04] >> what happened [09:04] >> there wasn't honestly I would say there [09:08] wasn't um clear information [09:12] right [09:13] >> okay [09:13] >> they were not going to do like a full [09:15] sponsorship and I think that was a [09:17] problem [09:19] >> right that was a problem [09:21] >> for one then two I had personal issues I [09:26] lost my dad. So at the burial and [09:29] everything, I had to cancel. I had to [09:31] cancel like I mean the plan was for me [09:33] to like travel regardless like whether [09:35] it's sponsorship or not, right? [09:39] >> But that again was like a limiting [09:42] factor because I was like they're not [09:44] going to be sponsoring me like doing the [09:47] sponsorship thing. There's no need for [09:49] me to stress since I'm already under so [09:51] much pressure. [09:52] It's not like there's something I'm [09:56] missing out or how do I put this? [10:00] It's not like there's something that I'm [10:02] missing out based on maybe free or [10:05] complete sponsorship for the trip and [10:07] I'm missing out on that and I can maybe [10:09] compromise or something you get. So I [10:11] just like have to let it go [10:14] >> completely and I was supposed to be [10:16] speaking at the event so it was very [10:18] limited. [10:21] >> Okay. No worries. I totally understand. [10:23] I think for Pon Namibia, they're really [10:25] a small conference, so they don't get [10:27] that much to support, but they [10:29] definitely do support. So, uh, but you [10:33] do just always just email them, [10:35] especially if you're a speaker. They [10:37] always don't support that much, but they [10:39] always willing to support in terms of [10:41] accommodation or paying a little bit of [10:44] your flight. Let's say if it's half the [10:46] price or something. So yes, they always [10:49] do offer support, but just always draw. [10:51] I think for any conference, just shoot [10:54] them an email. Just tell them what [10:56] you're going through and they're [10:57] probably going to support you. So yeah, [11:01] >> maybe next maybe this year. When when is [11:04] Python a baby? This year? [11:06] >> Next year. It's going to be it always [11:08] happens in February. So it's going to be [11:09] 19th to 25th of February in 2027. [11:16] So their call for speakers always comes [11:18] around October, November, August, [11:22] October and then by November you know if [11:25] you're going uh by December [11:28] >> yeah they've always always accepted [11:29] their speakers by around December. So by [11:32] January you always know you've started [11:34] planning your visas and everything. So [11:36] yeah [11:39] >> I think I saw one Nigerian at the event. [11:41] I don't remember their name, but I think [11:43] I met one person from Nigeria at the [11:45] event. [11:48] >> Okay, let's see how it goes. Yeah, [11:51] hopefully everything goes as planned. I [11:54] was supposed to go for chaos from [11:56] Europe, but my my and um Europe and [12:00] first them, but my visa got denied. [12:04] So, [12:05] >> were they were they offering travel [12:06] support? [12:08] First them was offering and you know [12:11] first them and um [12:14] first them and [12:16] and [12:18] chaos Europe they were like merging sort [12:21] of they were concurrent. [12:24] >> Yeah. [12:25] >> Chaos con Europe was on the 29 was on [12:28] the 2nd of February and I think they [12:31] were partnering in a way. So and I was [12:34] speaking at first then I got an [12:36] opportunity to speak at first then right [12:37] so I was like oh great so I can just [12:40] come earlier attend chaos going up then [12:44] so it's kind of worked out the plan and [12:46] everything but my visa was denied so I [12:51] couldn't travel. [12:53] Oh, sorry. I think I'm also planning to [12:55] go to first next year. So, yeah, [13:00] >> hopefully I do it I do it better this [13:03] next because I plan to actually apply [13:05] again for the SH this hopefully this [13:08] time is better. [13:10] >> Okay. Okay. I'm rooting for you but [13:13] Winnie and Blessing I think I guess [13:15] anyone who wants us to do anything in [13:17] April I think it's already 20th of [13:20] April. Uh, do we want to do anything in [13:23] April? [13:25] >> The only thing we could possibly do that [13:29] would maybe beat or match the um [13:33] the last minute which I don't really [13:36] recommend because I don't like to rush [13:40] participants if anything. Yeah. But the [13:43] only thing that seems that we could do [13:44] is maybe a podcast. [13:47] like we don't know when. [13:50] >> Yeah, but we don't know when harmony has [13:53] planned for podcast of the year of the [13:56] month to be, [13:57] >> right? Maybe we must find out [14:00] >> find out about that. Again, we don't [14:03] know what topic we want to speak about [14:05] because we don't want something generic. [14:07] We don't want something as spoken about [14:08] before. We want something new, something [14:10] interesting and most importantly [14:12] something that involves the community [14:14] for people with disabilities and open [14:16] source as they mesh together. So we [14:19] don't know if 10 days is going to be [14:22] enough for us to figure out what we want [14:24] to do. I mean streaming is not a [14:26] problem. Streaming happens in a day. But [14:29] getting a speaker or representative, [14:32] getting a topic and arranging the [14:34] conversation if if it's something we can [14:37] do in 10 days. [14:40] >> Okay. Do you want to pick this up uh um [14:43] Toria and see if you can reach out to [14:49] to Harmony and see if anything is [14:52] possible. [14:54] >> Okay. I mean I could where I am actually [14:58] thinking or what I am actually thinking [15:00] now is how to get a speaker with [15:02] disability who is going to be available [15:06] to speak. So I'll just see what I can do [15:08] and I'll give you feedback in the next [15:11] oh the next meeting the podcast have [15:12] already been done because our next [15:15] >> so I think it's something we can always [15:17] we can give updates during uh during uh [15:22] on Slack. Okay, cool, cool, cool. I can [15:24] do that. I can give updates or I can [15:27] even tag harmony because he's also in [15:29] our Slack um group. So, I can just ask [15:33] him and then I'll tag him to give us [15:35] feedback on this so everybody gets to [15:38] know. [15:39] >> Okay, cool. [15:41] >> Okay, [15:45] >> great. [15:47] So, [15:49] that's for May. I don't know what's [15:51] happening in May. [15:54] I think I'm looking forward. Okay. So, [15:57] uh when do we think we can do like a [15:59] physical event? Do you folks in Lagos um [16:03] have like um have like the physibility [16:06] of doing a physical event? [16:10] >> You know, personally, I'd say it would [16:14] be smart to strategize events for them [16:18] to happen on like [16:23] on days that are [16:25] celebration days or months that are [16:27] celebration month especially as channels [16:30] for people with disability. Right. So um [16:34] if you're going to have an event [16:37] say open source event or something if [16:40] you have it close to or around a period [16:43] you're celebrating something for people [16:44] with disability maybe world autism day [16:47] or world um [16:50] um um [16:54] international day for people with [16:56] hearing disability or something in that [16:58] line. Right? And now the wonderful thing [17:02] is that um [17:04] Elizabeth is now one of the board of I [17:07] think she's board of is it board of [17:09] directors I don't know with GA a [17:14] um GA global accessibility awareness [17:17] community or something like that. So I [17:20] think this all makes everything easy. I [17:23] was actually going to reach out to her [17:26] after telling her that I need to take [17:30] some time off. I've not officially [17:32] spoken to her. All right. I think I saw [17:35] her took her post on LinkedIn. So, I [17:38] want to reach out to her so that we can [17:39] officially do a because she reached out [17:41] to me like sometime last year. She [17:43] talked about how we can actually merge [17:47] the two communities together, right? I [17:49] think she even introduced me to the [17:51] founder of the community, right? One of [17:53] the founders of the community. I think [17:55] Joe, I'm supposed to even reach out to [17:57] him to have something like maybe an [18:00] event or something we can celebrate that [18:02] would um be a collaboration between [18:05] Chaos and the community, right? So now I [18:08] think it is best now that she's also in [18:11] the community. I think she thinks she's [18:13] still going to be like reaching out to [18:17] we can still like reach out to her in [18:19] chaos, right? Like she's still like in [18:21] chaos. So, I plan to reach out to her [18:24] and ask her when if there's going to be [18:26] like a major event that [18:29] >> the community is going to be hosting [18:31] globally that we can maybe have a a [18:34] session or a chapter or something here [18:38] in Nigeria and then we can now use that [18:40] opportunity to have like an opensource [18:43] chaos collaborative event with it if [18:45] that makes sense. [18:49] >> Okay, that makes sense. So I I I don't [18:50] think we can put that in any month till [18:52] you reach out. Right. [18:54] >> Exactly. Like we don't know when [18:56] exactly. So for [18:58] >> you can keep that pendulum [19:00] >> until we figure out the best time to [19:03] Yeah. have it. [19:05] >> Okay. So just a quick when when are the [19:07] accessibility celebration days so that [19:09] you can just mark them. Yeah. [19:11] >> There are many. There are many. I'll [19:13] just like reach out to somebody in my [19:15] community accessibility Nigeria. I think [19:17] we have a list. I'll share it with you. [19:19] I'll share it later. Yeah, there are so [19:22] many of them [19:25] scattered through the year. [19:29] >> Okay. Do you want to run a webinar [19:31] sometime? I'm just thinking of ideas of [19:34] what we can do. [19:36] >> You mean like virtually? [19:38] >> Yeah, virtually instead of like in [19:41] person. [19:42] >> I mean, we can do that while we still [19:44] have like physical event. We can run a [19:46] webinar. [19:49] Yeah. [19:50] So, do you think we can [19:54] we can have a webinar in [19:57] uh we can have a webinar in June. [20:00] >> Okay. [20:02] >> Yeah. So that we as we figure out um [20:06] what to have and then we also think of [20:08] what we want to to have in the webinar. [20:11] >> Mhm. [20:13] >> Yeah. [20:24] Uh, I'm waiting for folks to add more. [20:27] So, blessings. I think I also saw [20:29] someone else in the meeting. I'm not [20:31] sure of the name. [20:33] >> I've not I've not heard your voice. [20:36] >> Yes, Kirrion. How you doing? Um, hope [20:39] you're doing well on your end. [20:42] We're just trying to plan out the year. [20:44] So this is a very good time if maybe you [20:47] are new to the working group or maybe [20:49] you want to contribute more uh feel free [20:52] to share ideas on how maybe your [20:54] background on how we can do make impact [20:58] with uh within chaos project. So yeah [21:00] please go ahead. [21:01] >> Thank you. I appreciate it. I'm just [21:04] kind of sitting in on all the chaos [21:05] meetings. I I'm starting a basically a [21:09] an online encyclopedia and it kind of [21:12] overlaps a lot with open source and [21:15] showing off where open source comes [21:16] from, where the code comes from. And [21:18] when I was looking out, I found chaos. [21:20] So I've been kind of sitting in [21:23] different meetings. My project is an [21:25] international 3D encyclopedia [21:28] uh meant for your phone or mobile or web [21:30] browser. So something easy for people to [21:32] find information. And uh I really find [21:35] your guys' meetings really intriguing. [21:37] Uh it's bringing me closer to the [21:39] community of what I'm trying to focus on [21:42] because I've been one person developing [21:44] for so long and I am just getting into [21:47] Python. I'm just getting into open [21:49] source. I come from a AAA game developer [21:51] background and I have tried to go the [21:54] other route and it's it's quite [21:56] difficult but I've found it very um more [21:59] rewarding. [22:02] >> Okay. Okay. That's interesting. [22:04] Looking forward to how your project pans [22:06] out. So, but if you have any ideas on [22:08] accessibility stuff, if you worked [22:10] around you've worked around that, you [22:12] have any background experience or maybe [22:13] you've had something, feel free to also [22:16] chime in and drop ideas. So, yeah, [22:18] >> for sure. I only have uh 33% of my [22:22] vision, so I'm not quite quite legally [22:24] blind, but close enough to be legally [22:26] blind. So, I do all my computer work [22:28] with lots of uh [22:30] >> uh assistance and help from uh the [22:33] computer world. So, I I that's what [22:36] brought me to this one. [22:38] >> Oh, okay. Okay. Okay. That's [22:40] interesting. Okay, that's good. Um and [22:42] how has it been for you to to work [22:45] around meetings and coding and all that? [22:48] Um just like is it just okay or you have [22:50] you have faced some barriers? It was [22:53] really hard because I started a career [22:55] in games and then experienced my sight [22:58] uh loss. Um so for a couple years I just [23:01] took time off and went away. But I have [23:04] used tools and also just [23:07] dealt with uh what I have as a vision [23:10] and gotten more uh up to speed uh what I [23:14] used to be with that. Um, now I utilize [23:18] a lot of the built-in tools and I have a [23:20] lot of my I've actually used AI to build [23:22] my own tools now because some of them a [23:25] lot of tools for people with [23:26] disabilities are built with people [23:29] asking people with disabilities what [23:31] they want. So there's already one level [23:33] of disconnect. So I'm able to build [23:35] tools that work for how I want them to [23:37] work. And I really want to share those [23:40] tools off too. um things that don't add [23:43] extra clicks that you have to click [23:44] things so that you can use your voice to [23:46] bring up magnifiers. Um they snap to [23:50] your mouse, not have to go and find the [23:52] magnifier and then drag it to where [23:54] you're looking. Um there's a lot of [23:55] little things that uh I've been working [23:57] on that I think would help. Um but I I [24:01] uh I don't know how to upload to Git [24:03] yet. I've been I I come up from an old [24:06] Perforce generation where we used a a [24:08] different tool. Um, [24:09] >> yeah, [24:10] >> just getting into uploading everything [24:12] on. Um, and I think it [24:15] >> could help. It's hard because a lot of [24:16] people with disabilities don't use the [24:18] regular tools or look in the regular [24:20] spots. Um, [24:21] >> yeah, [24:22] >> resources like in Canada where I am, the [24:24] resources don't really have a lot. They [24:26] don't really know what's out there. So, [24:28] that's where I think um I spent a lot of [24:30] years being a technical artist and I [24:32] think that I can bridge the gap between [24:34] disability and tech. [24:36] >> Oh, that's interesting. Um I think you [24:39] would actually make a very good um host [24:42] at our podcast. We always host like a [24:44] podcast for disability. I think your [24:46] experience in building tools as someone [24:48] who has um I think a little bit of [24:49] disability with your vision and talking [24:52] about how you've built them and how you [24:54] are currently working um through that [24:56] would be interesting. If maybe by any [24:59] chance you're done for that and maybe [25:00] Victoria can reach out. [25:02] >> For sure. I'll put my email in here. [25:05] >> Okay. Sure thing. Um that that's [25:07] amazing. And I think you also mentioned [25:08] something around building tools, using [25:11] AI to build tools for people with [25:13] disabilities. It's something I've been [25:15] doing recently where I'm using AI to [25:17] build tools to help me write. I was a [25:20] technical I am a technical writer but I [25:22] I first writer's blog and I've not been [25:24] writing for like a couple of months now [25:26] uh like um six eight months and I've I'm [25:29] using AI to build like an agent that [25:32] helps me brainstorm ideas and connect it [25:35] to my deployment uh to where I want to [25:37] deploy my articles and just do that [25:39] right right off. So that's also be an [25:41] interesting conversation we can have [25:43] around how you're using AI to build [25:45] tools that help persons with [25:46] disabilities. Um, I think if you drop [25:48] your email, probably we'll reach out and [25:50] have a chat and see if we can even have [25:52] that as one of our webinars on [25:54] accessibility and see how people can [25:56] build accessibility with AI. So, yeah, [25:59] that's really cool. [26:01] >> Thank you so much. I I would appreciate [26:02] that. And AI really um as someone who [26:05] used to do I used a lot of mcripting for [26:07] Maya. It's a 3D program and I was just [26:10] getting into Python, but it's really [26:12] hard when you have even slight eyesight [26:15] problems to find the missing slash, the [26:17] backslash, or the period or the comma. [26:19] So, AI allows you to [26:22] >> even I have a tool that does a diff on [26:24] code, but then it also highlights things [26:27] in multiple ways so that I can see [26:30] >> like errors or things that are not quite [26:32] errors like red and yellow. I really [26:34] really try to use visual stuff that is [26:37] really exaggerated and then it's really [26:39] because what you're doing is you're just [26:41] trying to make it so that everyone's as [26:42] fast as everyone else [26:44] >> and I think that's the most important [26:45] part with disabilities is you're just [26:47] trying to bring everyone up to the same [26:48] speed and I don't think a lot of people [26:50] think about that. They overengineer [26:52] things. Um, and the best the best tool [26:56] still for a blind person is a stick [26:58] because it's it shows that you're blind [27:00] and also gives you an extension of your [27:02] hand. [27:04] >> Oh, okay. Okay. That's that's [27:05] interesting. I think that that's pretty [27:07] cool. Um, what what you get to do. So, [27:10] yeah, I think Toya will reach out um um [27:14] and then [27:16] >> Yes. Yes. Please go ahead [27:18] >> and go. Um [27:21] it's great to meet you Korean. We love [27:24] what you're doing and I'm definitely [27:26] going to reach out. I feel like um this [27:28] conversation will really make a great [27:31] one for the podcast. I mean a lot of [27:33] people would love to hear about what [27:36] you're building and I think it would be [27:37] a great opportunity to talk about it and [27:41] um people would also love to [27:44] use what you're building. I don't know [27:46] if it's it's ready, if it's published, [27:49] if it's life. I mean, people also love [27:52] to [27:53] >> I think it's time to publish things [27:54] because it's uh even when things are [27:56] broken, it's better than when you think [27:58] they're finished. [27:59] >> Yeah, I agree with you. I mean, as [28:02] someone who who is into be the [28:04] perfectionist, it can't be that perfect. [28:06] You just have to work with it as you go. [28:09] You have to publish what is already [28:10] available, then make updates in the [28:12] future. So I I I think it's going to be [28:14] a great opportunity for for us to see [28:17] what you're working with. So but I [28:19] wanted to ask though um [28:21] you finding the PS community and the [28:24] meeting it was through the website. Yes. [28:28] >> Was it through the website? [28:30] >> It was someone named Emma. Um so I am in [28:33] Canada and a friend of mine was part of [28:35] the Victoria maker space and Emma was in [28:38] the maker space. So, multiple people [28:41] have connected me through and I've been [28:43] joining the other chaos meetings for a [28:45] while. It seems like there's um I was [28:47] with Adrian and the augur stuff, but it [28:50] seems like there's quite a bit. [28:52] >> Yeah. Somea some chaos inside of chaos. [28:54] So, I've appreciated seeing that though [28:57] because it shows that everyone's willing [28:58] to [29:00] >> uh talk about the hard stuff where a lot [29:02] of communities seem to just kind of fade [29:03] away when that stuff happens. So [29:06] >> with open source there's always the [29:08] chance to split to a new branch and [29:11] start a new project. So that's what I [29:12] really like. [29:14] >> Yeah, there's always something to do. [29:16] That's the amazing thing about oppos [29:20] different branches of the work. So um [29:24] that's great. That's great. We also love [29:26] you to be part of like maybe try to [29:28] review some of our website and see if [29:30] it's it's accessible enough for you [29:32] because again while we are trying to [29:35] build software and community that is [29:37] accessible to everyone especially people [29:40] with disabilities we also want to start [29:42] from the from like start from home per [29:46] se. Yeah. So from our websites to know [29:48] if our website [29:50] are accessible and all the products we [29:54] have currently are accessible and know [29:56] if people with disability have any [29:58] barrier at the property using them. So [30:01] maybe while we have a conversation or [30:03] while I send an email I can send you a [30:05] link to some of the website and maybe [30:07] tell us what you think and what your [30:09] experience with it was if that's fine. [30:12] >> That sounds great. That sounds exactly [30:14] where I'm trying to head towards. Um, [30:16] less corporate uh, contract job work and [30:19] more just uh, trying to see if I can be [30:22] part of the communities and help where I [30:24] can help. [30:26] >> That's nice. Nice to meet you and would [30:29] love to see more of you in our meetings. [30:31] So, we usually have our meetings [30:32] bi-weekly. So, after our meeting today, [30:35] our next meeting will be in 14 days in [30:38] the next. So, we'd love to see more of [30:40] you in our meetings. [30:42] >> Yeah. I'll be reaching out for your [30:44] email as well for the podcast. [30:46] >> Please do. Thank you so much. [30:48] >> All right. Thank you, Karen. [30:52] >> So, um, I wanted to say, you know, we we [30:56] can actually we don't have to figure all [30:58] the quarters out today. [31:02] >> Yes. [31:02] >> I mean, yeah. So since we have the [31:06] second quarter and part of the first [31:08] quarter, I mean I think after reaching [31:10] out to Elizabeth and figuring out when [31:13] the event is, we can figure out if you [31:16] want to put the um inerson event in the [31:20] second quarter or the third quarter [31:22] since we don't have anything in the [31:24] third quarter currently. And then again [31:26] we find out about um other open source [31:29] events that we probably want to [31:32] collaborate with whether it's Oscar fest [31:35] uh or any other open source events [31:38] that's currently happening in Nigeria or [31:40] any other place in Africa. I'd say also [31:43] Europe but I think we should start off [31:45] with where we have people who can um [31:49] coordinate and supervising person right [31:52] so maybe we can start from Africa and [31:54] then when we get that information we can [31:56] look for main activities for third [32:00] quarter and the last water [32:05] >> okay that's fine I think you're also [32:07] like um I don't know um 10 six minutes [32:10] to time so I didn't want to keep focus [32:12] longer unless you have so I think we can [32:15] focus on this and this and then I'm also [32:17] also so part of the other thing I'm now [32:19] also original executor for black python [32:21] devs so if you're organizing something [32:23] and it relates to Python uh uh it's also [32:26] open source so long as it's open source [32:28] it's Python um I can look I can find [32:32] ways to get support you folks if it's [32:34] financial support if it's swag over to [32:36] you folks so that um just to support um [32:40] the [32:42] a round of applause. [32:44] >> Yeah. So, I'm looking [32:45] >> congratulations and thank you for [32:48] bringing that up. [32:50] >> Thank you. Thank you. You're also going [32:51] back to I think the DISC committee is [32:54] returning to its regular activities [32:56] soon. [32:57] >> I was going to ask what's going on, [32:59] what's the update? The event for last [33:01] year did not hold anymore. [33:03] >> Yeah, I think it's cuz uh last year we [33:05] didn't have budget. That's for sure. Um [33:08] this year we are just getting started [33:11] but sadly we say with a with a heat cuz [33:13] Camila left the team and you know Camila [33:16] was our point of contact. So Camila left [33:18] >> now. Yeah. [33:20] >> So it's been it's been quite up and down [33:23] but we finally have someone who's now [33:25] representing us. That's Kar. So we want [33:28] to start fundraising see if we can do [33:30] the next disc uh and conference. The [33:33] idea was to do it at Pyon Africa this [33:35] year so that we don't have to pay for [33:38] everyone to get there but get folks who [33:40] are already there to attend the [33:42] conference but we we are not thinking [33:44] it's possible because it's a very short [33:46] time to fund raise um for that and also [33:49] we have we always had to write a [33:50] proposal and send it to the to the board [33:52] for the board to approve and it's like [33:56] once we have all it figured out I'll [33:58] definitely share to the event probably [34:00] next Yeah. [34:02] >> Okay. Oh, great. No problem. No problem. [34:06] That's cool. So, um, for me, I don't [34:09] think there's any other thing I have to [34:11] contribute now. I don't know if anybody [34:13] has anything to [34:17] >> I don't think I have. Mine is just to [34:19] say I was able to join these meetings [34:21] cuz I had like work meetings at this [34:24] time, but I'm now back to So, I had [34:27] switched to part-time. So my meetings [34:29] are happening in the evening, but I've [34:30] now switched back to full-time. So my [34:32] meetings happening during the day. So I [34:34] can now much more be more consistent [34:36] with these meetings. So yeah. [34:39] >> Yay. Another round of applause. [34:42] I'm excited to be having you back fully. [34:45] So we hope to see more of you. [34:49] >> Thank you. [34:51] >> Thank you guys for joining. Looking [34:53] forward to having you join again next [34:56] two weeks. and hopefully I'll be able to [35:00] join the general diversity meeting and [35:04] tell people that our meetings are [35:05] officially started. I don't think I [35:06] shared this in the general chaos [35:09] uh platform. I will be doing that and [35:13] then I'll also try to attend. I was [35:17] going to ask like feedback from the [35:19] diversity [35:20] uh meeting so far but since our time is [35:23] almost up maybe we can start off from [35:25] our next meeting. here where we talk [35:28] about what like the general diversity [35:30] issue is and how it applies to [35:32] accessibility and pointers we can take [35:35] and all of that all of that I know um [35:38] Fred is uh used to be our point of [35:41] contact I don't know if she has been [35:42] attending the meeting but that's fine [35:46] you've been attending the meeting yes [35:48] >> uh not in recent times I've been very [35:54] >> understandable [35:55] >> so Yeah, cool. So, yeah, thank you [36:00] everyone for joining. It was really nice [36:02] having everyone and thank you Karen. It [36:06] was nice meeting you. We hope to see [36:08] more of you. [36:10] >> Um, [36:12] yeah, I'll be reaching out to you soon. [36:15] And thank you, Brian, for facilitating [36:16] the meeting. Thank you, Blessing, for [36:20] being our secretary. [36:23] Yeah, looking forward to seeing us in [36:25] two weeks. [36:26] Bye [36:29] >> bye guys. [36:31] >> Bye guys. Take care. Nice to meet you [36:32] all. [36:34] >> Bye. [36:35] >> Thank you Brian. [36:38] >> You're welcome. Let me [36:40] >> see you in two weeks. I'll be reaching [36:41] out to you. I'll be your DM on WhatsApp [36:43] soon. How about that? [36:44] >> Okay. Okay. My boss. Okay. My boss. [36:47] >> Thank you, my boss. Bye. [36:50] >> Bye.  📄 **Full text:** ![[Full Document Contents/Articles/CHAOSS AccessibilityDisability Inclusion WG, April 20, 2026.md|CHAOSS Accessibility/Disability Inclusion WG, April 20, 2026 by YouTube]] ## Highlights - to learn what I do. So if I get a workshop to teach people accessibility that makes more sense compared to say hey join the community you know do and most of them rarely even end up joining. >> So I feel like that is always more impactful >> and you can even mention something like oh I trained a couple of number of people in this and this and this that makes no sense. So that's my thinking around it. So, it's either we do a workshop or we partner with them as accessibility partners. I think that's something they'll be open if you just ([View Highlight](https://read.readwise.io/read/01kq2ts78g816tkpps2mmevecj)) - Tags: 👻 ai highlighted - send an email to the organizers. Good thing I'm part of the organizing team for PCON Africa this year. >> So, >> Oh, great. >> We can send an email to be like accessibility partners like we can badge the event, we can do what and then once we do that >> so I think we have different ideas. So, let me just start writing them. >> All right. >> All right. Um so which country will are you um having a blast? >> It's happening in Uganda this year. >> Uganda. Okay. Um ([View Highlight](https://read.readwise.io/read/01kq2ts78q2p3s260xa20fawpq)) - Tags: 👻 ai highlighted - put that end game in mind. >> So while we collaborating are we trying to meet their community for people with disabilities? Are we trying to um tell them that they also can contribute to open thoughts in chaos and open source in general? um we're trying to tell them how they can contribute to open source as it concerns accessibility and most ([View Highlight](https://read.readwise.io/read/01kq2ts78ya0hvb256fdjwz1rw)) - Tags: 👻 ai highlighted - disability came and spoke about using open source software and um being part of the open source community and how it benefits her and how it has been useful to her and the community in general. So is that what we want to do in Pyon? I think it would be a great idea aside having a personal talk where we come and talk about accessibility and what we do in open source uh what we do in tech as it concerns accessibility and people with disabilities. We can also do one ([View Highlight](https://read.readwise.io/read/01kq2ts79fwzp36rbnf9qydq2r)) - Tags: 👻 ai highlighted - where we have the community themselves, people with disability come and speak about how or what they've been doing in tech and how they can be part of the open source space either building the open source community or building open source software because that's like the end goal. The end goal is we want people with disabilities to be building software technology. We want them to be part of the open source community, right? So I mean since you're part of the organizers we can talk about that like a panel session or a conversation ([View Highlight](https://read.readwise.io/read/01kq2ts79tchwpjprrbpjj3tvm)) - Tags: 👻 ai highlighted - helps me brainstorm ideas and connect it to my deployment uh to where I want to deploy my articles and just do that right right off. So that's also be an interesting conversation we can have around how you're using AI to build tools that help persons with disabilities. Um, I think if you drop your email, probably we'll reach out and have a chat and see if we can even have that as one of our webinars on accessibility and see how people can build accessibility with AI. So, yeah, that's really cool. ([View Highlight](https://read.readwise.io/read/01kq2ts7dzqn7n8p4ap0bamhpm)) - Tags: 👻 ai highlighted