-
Notifications
You must be signed in to change notification settings - Fork 635
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
Create ACCESSIBILITY.md file #3145
Labels
accessibility
For issues related to book and infrastructure accessibility
Comments
27 tasks
aleesteele
changed the title
Create ACCESSIBILITY.md file - accessibility policy for the community - drawing from the Slack policies: https://hackmd.io/@turingway/ttw-slack-intro
Create ACCESSIBILITY.md file
May 25, 2023
aleesteele
added
the
accessibility
For issues related to book and infrastructure accessibility
label
May 25, 2023
Notes & citations:
|
Examples of accessibility policies (list developed with @LizHareDogs) |
Adding a note here to add materials related to use of visual tools like miro, excalibur, mermaid after discussions with @RichardJActon, thank you! |
4 tasks
Open
48 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
After discussing with folks during the November 2022 Book Dash and May 2023 Book Dash, this issue is to propose an accessibility policy for the community.
Most accessibility policies that we have seen within other Github repositories relate to web accessibility as perhaps opposed to (or in addition to) a wider set of practices that extend across a whole project: from how we use communication channels, to organising events, designing websites and resources, and more.
In our accessibility policy for TTW, we would like to draw upon the wider suite of tools that exist, while putting forth how we specifically consider accessibility within TTW
The text was updated successfully, but these errors were encountered: