-
Notifications
You must be signed in to change notification settings - Fork 624
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Accessibility Guide Landing Page #3426
Comments
Hi @aleesteele, based on the conversation happening around PR #3340, the chapters in the Inclusive Events guidance might not be relevant or able to be put in the accessibility guide 🙂 |
Hi @BrainonSilicon - thanks for your message. I have read the thread and spoken to the Accessibility Working Group, and will respond there. It might take a few days because of book dash, but this landing page still makes sense in both contexts. |
Summary
In November 2022, @AndreaSanchezTapia and @LizHareDogs began the process of drafting a landing page for a new Guide for Accessibility (see more here) in response to the proposal for a new guide.
In the following year, a lot of work has been done within the Accessibility Working Group to understand how we work through accessibility within the community, and the practices that we might employ in the process. In the process, we've focused particularly on the accessibility policy, rather than the guide itself.
This issue is connected to #2730, which proposes a new guide for accessibility. It also is means that many of the chapters from #3307 (thank you @BrainonSilicon for drafting, @JFormoso, @PatriLoto and many other reviewers and editors from the accessibility working group and from Turing and otherwise!) now have a new home. It is also connected to #3146, which notes how we within the community think about and process access-related content and work.
What needs to be done?
This landing page is just the beginning – and from here, we can build out the structure together. There's a lot in #2730 that we can bring back in the planning process.
There are lots of initial questions here to discuss with the working group:
Who can help?
The Accessibility Working Group - particularly @LizHareDogs @AndreaSanchezTapia @PatriLoto @JFormoso @aliasLaurel
The text was updated successfully, but these errors were encountered: