[READY FOR REVIEW] Adding accessibility policy draft (accessibility.md) and practices #3581
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for the-turing-way ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
aleesteele
changed the title
aleesteele
changed the title
aleesteele
added
review request
aleesteele
commented
Mar 25, 2024
|
|
||
| ## Acknowledgements | ||
|
|
||
| This Accessibility Policy was created by The Turing Way. |
There was a problem hiding this comment.
Maybe need to add some more resources here.
aleesteele
commented
Mar 25, 2024
aleesteele
commented
Mar 25, 2024
aleesteele
commented
Mar 25, 2024
aleesteele
commented
Mar 25, 2024
aleesteele
commented
Mar 25, 2024
aleesteele
commented
Mar 25, 2024
aleesteele
commented
Mar 25, 2024
aleesteele
commented
Mar 25, 2024
aleesteele
commented
Mar 25, 2024
|
This was reviewed with @LizHareDogs and @BrainonSilicon today at an Accessibility Working Group meeting. Tagging @trallard, @PatriLoto, @JFormoso, @EstherPlomp, @malvikasharan, @AlexandraAAJ and other folks that have contributed to many other resources around accessibility in #2730 or in other spaces. It would be so great to have your feedback! We can also bring this guide, and many of the key points to an upcoming Collaboration Cafe or to our April Community Call to discuss openly with folks. |
JimMadge
reviewed
Mar 26, 2024
There was a problem hiding this comment.
This is looking good.
I think it gives a great sense of what we care about and how we action that.
Using semantic line breaks would help a lot with the readability and understanding diffs.
Maybe it is missing something about what happens when we fall short? Like, if you post a picture without alt text, someone might point it out, suggest some, or ask that you add some. That is fine and it isn't an attack, we are always trying to improve things together.
ACCESSIBILITY.md
Outdated
Comment on lines
5
to
8
| While accessibility is commonly understood with respect to disability, we – meaning _The Turing Way_ community – define accessibility as giving access to groups of people that encounter different barriers for participation. Barriers may be anything related to, including, and extending beyond the following: | ||
| - Age | ||
| - Disability | ||
| - Ethnicity and race |
There was a problem hiding this comment.
Suggested change
| While accessibility is commonly understood with respect to disability, we – meaning _The Turing Way_ community – define accessibility as giving access to groups of people that encounter different barriers for participation. Barriers may be anything related to, including, and extending beyond the following: | |
| - Age | |
| - Disability | |
| - Ethnicity and race | |
| While accessibility is commonly understood with respect to disability, we – meaning _The Turing Way_ community – define accessibility as giving access to groups of people that encounter different barriers for participation. Barriers may be anything related to, including, and extending beyond the following: | |
| - Age | |
| - Disability | |
| - Ethnicity and race |
|
|
||
| We recognise the complex and interlinking ways in which intersectionality affects identity, and thereby, access or inclusion within any community project like _The Turing Way_. So in this sense, our accessibility practices may overlap with practices that enable inclusion more broadly within any community. | ||
|
|
||
| In developing this policy, we aim to draw from the [access-centered framework](https://accesscenteredmovement.com/what-access-centered-means/) in describing access as a constant process that changes in each space with each individual. Therefore, while this policy outlines our commitment to access-centered practices within our community in a broad sense, we also document the specific practices we use within _The Turing Way_ our Community Handbook, as well as share broader recommendations that go beyond our current practices in the Guide for Accessibility. Each resource (our Accessibility Policy - this document, Community Handbook Accessibility Guidelines, and our Accessibility Guide) play a different yet overlapping role in enabling, documenting, and sharing our evolving language around accessible and inclusive collaboration. |
There was a problem hiding this comment.
I find this paragraph a little hard to understand.
Maybe it would help to break down the three different documents and their purpose. Is it something like,
- Accessibility policy - Our vision and the rules
- Community Handbook Accessibility Guidelines - Practical advice to build accessibility in your contributions/activity
- Accessibility Guide - A broader discussion of accessibility, not just in The Turing Way
|
|
||
| ## 1.1 Core Principles | ||
|
|
||
| These core principles are at the heart of our accessibility policy, and they extend beyond the web accessibility of our open access guides (see 2.1) to the broader practices that that we use as a community on collective platforms (see 2.2) and while hosting events (see 2.3). |
There was a problem hiding this comment.
You can use internal references here, like
[2.2](#2-2-community-platform-accessibility)
ACCESSIBILITY.md
Outdated
|
|
||
| 1. **Feedback form**: Please submit access related through [this form](https://forms.gle/Ngr2eUtQmf7aEeao6). All of the information in this form is processed anonymously, with the option of submitting contact information by choice. | ||
| 2. **Drop-in sessions**: Throughout the calendar year, we would like to facilitate drop-in session to receive feedback about access related different parts of project. These may take place at our Collaboration Cafe or may be hosted separately. | ||
| 3. **Email the Research Community Manager or project team directly directly**: You can always email the Research Community Manager directly at asteele@turing.ac.uk with direct feedback. Alternatively, you can also |
ACCESSIBILITY.md
Outdated
Comment on lines
76
to
79
| Knowing this, we are working to develop processes that enable us to action and report transparently on feedback given through these channels. This may include: | ||
| - Reporting within the Accessibility Working Group in order to discuss possible actions that can be taken to address feedback | ||
| - Liasoning with appropriate groups within The Turing Way project (i.e. the Infrastructure Working Group) in order to create or resource technical changes that may be needed | ||
| - Escalating feedback to the project co-leads, funders, and others at the constitutional level of the project as needed |
There was a problem hiding this comment.
Suggested change
| Knowing this, we are working to develop processes that enable us to action and report transparently on feedback given through these channels. This may include: | |
| - Reporting within the Accessibility Working Group in order to discuss possible actions that can be taken to address feedback | |
| - Liasoning with appropriate groups within The Turing Way project (i.e. the Infrastructure Working Group) in order to create or resource technical changes that may be needed | |
| - Escalating feedback to the project co-leads, funders, and others at the constitutional level of the project as needed | |
| Knowing this, we are working to develop processes that enable us to action and report transparently on feedback given through these channels. This may include: | |
| - Reporting within the Accessibility Working Group in order to discuss possible actions that can be taken to address feedback | |
| - Liaising with appropriate groups within The Turing Way project (i.e. the Infrastructure Working Group) in order to create or resource technical changes that may be needed | |
| - Escalating feedback to the project co-leads, funders, and others at the constitutional level of the project as needed |
| (ch-accessibility-comms-platforms)= | ||
| # Access-centered support on Communication Platforms | ||
|
|
||
| _The Turing Way_ uses a variety of platforms for communication (i.e. Slack, social media platforms like X/Twitter, Linkedin, Mastodon) and collaboration (i.e. Github, HackMD, Etherpad). |
There was a problem hiding this comment.
I think we try to avoid Latin abbreviations for readability and compatibility with screen readers.
| We aim to provide the following support and normalise the following practices within our community by doing the following places: | ||
|
|
||
| - **Adding alt text to images**: We use alt text or "alternative text" to describe images, diagrams, or other visuals within _The Turing Way_. To learn more about how to write and use alt text for your work, please use this {ref}`guidence<accessibility-alt-text>`. | ||
| - **Limit embedded links and provide alternatives for accessing information**: On many platforms, embedded links may not be accessible by screen readers, or may increase cognitive overload. If you are inserting a link into a message, limit the number of embedded links within a message. On Slac, avoid embedding links within replies to messages when possible, as links posted within threads are not readable for screen readers. |
There was a problem hiding this comment.
Suggested change
| - **Limit embedded links and provide alternatives for accessing information**: On many platforms, embedded links may not be accessible by screen readers, or may increase cognitive overload. If you are inserting a link into a message, limit the number of embedded links within a message. On Slac, avoid embedding links within replies to messages when possible, as links posted within threads are not readable for screen readers. | |
| - **Limit embedded links and provide alternatives for accessing information**: On many platforms, embedded links may not be accessible by screen readers, or may increase cognitive overload. If you are inserting a link into a message, limit the number of embedded links within a message. On Slack, avoid embedding links within replies to messages when possible, as links posted within threads are not readable for screen readers. |
There was a problem hiding this comment.
I'm not quite sure what an embedded link is. Is it different to a hyperlink? Are there non-embedded links?
There was a problem hiding this comment.
I'd agree with Jim here- we need to specify the alternative way you should share a link (spoiler: I don't know what this is)
book/website/community-handbook/accessibility/accessibility-comms-platforms.md
Outdated
Show resolved
Hide resolved
harrietrs
reviewed
Mar 28, 2024
| - **Limit use of emojis that disrupt narrative flow**: Do not replace words with emoljis or use too many emojis to communicate important information. Screen readers usually read one emoji at a time using the alternative text and while sometimes the purpose may be clear (i.e. ```:thumbsup:``` represents an icon of a thumbs up sign), at other times it may not be (i.e. ```:partyblobcat``` represents a multicolored cat that is rotating in a circle, and is generally used in the context of a celebration or celebratory news). More broadly, strings of emojis can produce a clunky, repetitive user experience for people trying to understand the core message. Remember that not all people are able to access the emoji reactions option within Slack, and normalise using written affirmations as well. | ||
| - **Cross-post information to ensure openness**: People interact with _The Turing Way_ community on many different platforms. Not everyone in the *The Turing Way* community is in the Slack workspace, or on Github, in every community call, or on every social media channel. Where possible, we aim to normalise creating issues and discussions on the Github repository or post across social media channels in order to ensure the widest reach and participation possible across the community. | ||
| - **Be sensitive to bandwidth needs**: As a digital and remote-first project, we are committed to making sure that our resources, communication platforms, and community are accessible to the widest possible audience, despite any bandwidth needs or barriers. In order to make sure that our communication platforms are accessible in low-bandwidth environments for the community, we avoid posting data-intensive content like videos directly into the channels. Instead, we prioritise hosting the content on other platforms (i.e. YouTube) where viewers have the option to adjust the data-intensiveness of the streaming platform. We also frequently turn off video streaming in team meetings in order to adjust for participants or community members that find it difficult to tune in. | ||
| - **Be descriptive and clear in communication**: Aside from these concreate recommendations that we adhere to within the community, more broadly we aim to prioritise clear communication within _The Turing Way_ in order to ensure that our messages are accessible and readible for the community. |
There was a problem hiding this comment.
Suggested change
| - **Be descriptive and clear in communication**: Aside from these concreate recommendations that we adhere to within the community, more broadly we aim to prioritise clear communication within _The Turing Way_ in order to ensure that our messages are accessible and readible for the community. | |
| - **Be descriptive and clear in communication**: Aside from these concrete recommendations that we adhere to within the community, more broadly we aim to prioritise clear communication within _The Turing Way_ in order to ensure that our messages are accessible and readible for the community. |
I assume this was supposed to be concrete? Unless you mean 'co-created'?
book/website/community-handbook/accessibility/accessibility-comms-platforms.md
Outdated
Show resolved
Hide resolved
book/website/community-handbook/accessibility/accessibility-comms-platforms.md
Outdated
Show resolved
Hide resolved
book/website/community-handbook/accessibility/accessibility-comms-platforms.md
Outdated
Show resolved
Hide resolved
book/website/community-handbook/accessibility/accessibility-comms-platforms.md
Outdated
Show resolved
Hide resolved
ACCESSIBILITY.md
Outdated
|
|
||
| _The Turing Way_ is committed to ensuring our accessibility as a community on all the platforms we use. | ||
|
|
||
| In our Community Handbook, we describe these practices more specifically and in more detail. But as a baseline, our community is dedicated to enabling access across the various platforms we use through: |
There was a problem hiding this comment.
Can we add a link through to the accessibility comms platform page? As this seems to be a summary of that content.
There was a problem hiding this comment.
Yes - added a link and description here to the Community Handbook.
| We recognise that many feedback forms and other forms for gathering feedback can often operate as "blackboxes" that receieve information without taking actionable steps to address them. | ||
|
|
||
| Knowing this, we are working to develop processes that enable us to action and report transparently on feedback given through these channels. This may include: | ||
| - Reporting within the Accessibility Working Group in order to discuss possible actions that can be taken to address feedback |
There was a problem hiding this comment.
are there links to these groups we can add? (I'm nervous of adding links given the accessibility points re embedded links so please ignore this and other comments if that advice applies)
aleesteele
changed the title
|
Hi @aleesteele! I see there's already some reviewing going on - please let me know if an additional review is helpful, otherwise I'll read it when it is merged :) |
|
Thank you so much @harrietrs and @JimMadge for your reviews so far - didn't mean to leave you hanging, I'll be tackling these tomorrow! @EstherPlomp - feel free to add any comments you would like to either now or later. Because this is a community policy that will apply broadly, it would be great to leave a place for discussion about it in real time, as well as have more eyes on the document more broadly! I was thinking that this could be a good topic to bring to our next Collab Cafe in the main room, and/or at Book Dash, to merge it there. |
Changing wording Co-authored-by: Harriet Sands <harrietrsands@gmail.com>
Co-authored-by: Harriet Sands <harrietrsands@gmail.com>
Adding collaboration cafe link
aleesteele
commented
Apr 8, 2024
Formatting changes Co-authored-by: Jim Madge <jmadge@turing.ac.uk>
Fixing typo Co-authored-by: Harriet Sands <harrietrsands@gmail.com>
Fixing typos Co-authored-by: Harriet Sands <harrietrsands@gmail.com>
Fixing wording Co-authored-by: Jim Madge <jmadge@turing.ac.uk>
Co-authored-by: Harriet Sands <harrietrsands@gmail.com>
Co-authored-by: Harriet Sands <harrietrsands@gmail.com>
Co-authored-by: Jim Madge <jmadge@turing.ac.uk>
…mms-platforms.md Co-authored-by: Jim Madge <jmadge@turing.ac.uk>
aleesteele
commented
Apr 8, 2024
book/website/community-handbook/accessibility/accessibility-comms-platforms.md
Outdated
Show resolved
Hide resolved
…mms-platforms.md Co-authored-by: Harriet Sands <harrietrsands@gmail.com>
aleesteele
commented
Apr 8, 2024
ACCESSIBILITY.md
Outdated
|
|
||
| 1. **Feedback form**: Please submit access related through [this form](https://forms.gle/Ngr2eUtQmf7aEeao6). All of the information in this form is processed anonymously, with the option of submitting contact information by choice. | ||
| 2. **Drop-in sessions**: Throughout the calendar year, we would like to facilitate drop-in session to receive feedback about access related different parts of project. These may take place at our [Collaboration Cafe](https://the-turing-way.netlify.app/community-handbook/coworking/coworking-collabcafe.html) or may be hosted separately. | ||
| 3. **Email the Research Community Manager or project team directly directly**: You can always email the Research Community Manager directly at asteele@turing.ac.uk with direct feedback. Alternatively, you can also |
There was a problem hiding this comment.
Suggested change
| 3. **Email the Research Community Manager or project team directly directly**: You can always email the Research Community Manager directly at asteele@turing.ac.uk with direct feedback. Alternatively, you can also | |
| 3. **Email the Research Community Manager or project team directly directly**: You can always email the Research Community Manager directly at asteele@turing.ac.uk with direct feedback. Alternatively, you can also also reach out to them on other community platforms such as Slack. |
…mms-platforms.md Co-authored-by: Harriet Sands <harrietrsands@gmail.com>
…mms-platforms.md Co-authored-by: Harriet Sands <harrietrsands@gmail.com>
Completed sentence
|
As we begin a wider review process, I'm tagging a few people and groups here that would be great to have input on this policy, as we invite comment and discussion across the community:
Thank you so much for engaging with us through this extended process, and I thank you so much for your help and feedback in advance as develop this policy! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Tied to #3146 / #3145▶️ had some problems with the pull request!
List of changes proposed in this PR (pull-request)
What should a reviewer concentrate their feedback on?
Acknowledging contributors