Accessibilty audit of TWE and HackforLA

### Dependency
- Guides Team publishing a finished guide on how to make our guides accessible https://github.com/hackforla/knowledgebase-content/issues/134
- Implementing the guidance above into all the guide drafts

### Overview
As an inclusive community, we need to make sure that all our projects provide accessibility to people of all abilities to participate, learn and grow.
To present this simply, we need to answer these two questions:

1. Can/has someone who may have/has visual, hearing, dexterity and/or any other disability successfully join/ed, volunteer/ed and learn/ed at HackforLA?
1. Can a student who may have visual, hearing, dexterity and/or any other disability successfully join and complete the Internship Program?

### Action Items
- [x] Reach out to UI/UX CoP lead
- [ ] Conduct research on and find an expert on the subject
- [ ] Set up a special event with UI/UX CoP and invite the speaker to speak
- [ ] Research on how we can improve accessibility in the Internship Project
- [ ] Research on how we can improve accessibility all across HackforLA

### Resources/Instructions
[Digital Accessibility Foundations Free Online Course](https://www.w3.org/WAI/fundamentals/foundations-course/)
[W3C's Web Accessibility Initiative](https://www.w3.org/WAI/)
[Article on Accessibility of Remote Meetings](https://www.w3.org/TR/2021/WD-remote-meetings-20211014/#accessibility-context)
[Article on Figma plugin for accessibility](https://www.figma.com/blog/design-for-everyone-with-these-accessibility-focused-plugins/)