-
-
Notifications
You must be signed in to change notification settings - Fork 290
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
fixing links - accessibility changes #1768
base: main
Are you sure you want to change the base?
Conversation
Thank you!Thank you for your pull request 😃 🤖 This automated message can help you check the rendered files in your submission for clarity. If you have any questions, please feel free to open an issue in {sandpaper}. If you have files that automatically render output (e.g. R Markdown), then you should check for the following:
Rendered Changes🔍 Inspect the changes: https://github.com/carpentries/instructor-training/compare/md-outputs..md-outputs-PR-1768 The following changes were observed in the rendered markdown documents:
What does this mean?If you have source files that require output and figures to be generated (e.g. R Markdown), then it is important to make sure the generated figures and output are reproducible. This output provides a way for you to inspect the output in a diff-friendly manner so that it's easy to see the changes that occur due to new software versions or randomisation. ⏱️ Updated at 2025-01-10 15:30:20 +0000 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In addition to inline suggestions, (template-md) and rmd version should be [template-md/rmd] to reference named link (round parentheses reference hard links). Git didn't like me putting suggestions on them.
More generally, should we use a consistent style, either:
- ...see [link][link] OR
- ...see name-of-thing at [link][link] OR
- ...see [name-of-thing][link]
I don't recall exactly where the discussion came down. Currently, these revisions are mostly a mix of 1 and 2. My understanding is 3 is best for accessibility because the surface text describes the link, but it can be an issue for copying and pasting exercises into etherpads. Either way, we should try to do them all the same.
@carpentries/core-team-curriculum what is the current guidance on link practice, given the constraints above about both accessibility and copy-paste readiness for pads? |
Indeed, accessibility best practice would be descriptive link text. But this will not play nicely with the etherpad generation. If that is a dealbreaker, I suggest either option 2 (see name-of-thing at [link][link]) or a redundant approach that makes the etherpad look nicer: see [name-of-thing][link] ([link][link]). I marginally prefer the latter, while conceding that the redundancy will still be annoying for screen reader users. I leave the final decision up to the Maintainers. |
I think the latter approach has the additional advantage of being easy to switch to the only best practice option, if the template and/or etherpad tech changes |
I don't understand:
can you give the file(s) and line(s) of at least one occurence to help me parse what you are referring to (I only resolved the merge conflicts on this PR it is not really mostly my work) |
I think it's referring to lines 239 and 240 of |
I have done the redundant thing discussed above now, I think this is ready to go. Also I remembered that |
This is a nice idea. Please open an issue on https://github.com/carpentries/sandpaper to suggest it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggesting a few more polishes, but this seems mostly ready to go.
However, I think the instructors/checkout.md
file can be removed? It looks like David's branch had that file in the instructors
directory, where I think it might have lived in the past, but now it is only in learners/
.
@@ -55,7 +55,7 @@ things that we do, things that we are, and things that we champion. Many of thes | |||
|
|||
## Discuss The Carpentries Core Values | |||
|
|||
1. Take a moment to read through the Core Values on this page: [https://carpentries.org/values/][core-values] | |||
1. Take a moment to read through the [ https://carpentries.org/about-us/#our-values][core-values] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
1. Take a moment to read through the [ https://carpentries.org/about-us/#our-values][core-values] | |
1. Take a moment to read through [The Carpentries Core Values][core-values] [https://carpentries.org/about-us/#our-values][core-values] |
Put your feedback in the Etherpad. | ||
Organize your feedback along two axes: | ||
positive vs. opportunities for growth (sometimes called "negative") | ||
and content (what was said) vs. presentation (how it was said). | ||
|
||
Note: there is a version of this video with subtitles in both Spanish and English here: [https://www.youtube.com/watch?v=jxgMVwQamO0](https://www.youtube.com/watch?v=jxgMVwQamO0) | ||
Note: there is a version of this video with subtitles in both Spanish and English: [https://www.youtube.com/watch?v=jxgMVwQamO0](https://www.youtube.com/watch?v=jxgMVwQamO0) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note: there is a version of this video with subtitles in both Spanish and English: [https://www.youtube.com/watch?v=jxgMVwQamO0](https://www.youtube.com/watch?v=jxgMVwQamO0) | |
Note: there is [a version of this video with subtitles in both Spanish and English](https://www.youtube.com/watch?v=jxgMVwQamO0) [https://www.youtube.com/watch?v=jxgMVwQamO0](https://www.youtube.com/watch?v=jxgMVwQamO0) |
@@ -37,7 +37,7 @@ Extensions may be granted for any reason up to 1 year from your training date. | |||
|
|||
## Be The Expert: Checkout Q \& A | |||
|
|||
In small groups, read and discuss one of the three checkout procedures described on this page: [https://carpentries.github.io/instructor-training/checkout](checkout.md) | |||
In small groups, read and discuss one of the three checkout procedures described on this page: [https://carpentries.github.io/instructor-training/checkout/index.html](checkout.md). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In small groups, read and discuss one of the three checkout procedures described on this page: [https://carpentries.github.io/instructor-training/checkout/index.html](checkout.md). | |
In small groups, read and discuss one of [the three checkout procedures](checkout.md) [https://carpentries.github.io/instructor-training/checkout/index.html](checkout.md). |
|
||
We recommend that contributions be directed to: | ||
|
||
- any [Data Carpentry]({{ site.dc_site }}/lessons/), [Library Carpentry]({{ site.lc_site }}/lessons/), or [Software Carpentry]({{ site.swc_site }}/lessons/) lesson |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This line contains old Jekyll-style variable substitutions, which seems strange.
I tried to resolve the conflicts on #1490 in a codespace, only to realized after I had gone through all of the conflicts that I could not push to the branch for the pr. I pushed to my own branch and I think the only choice I can do is make a new PR directly
Someone else should review this and then we can merge to get the accessibility updates.
(we could technically make a PR to @dpshelio 's branch, have him merge that and then merge #1490 but he said he is limited capacity, so I want to give us a path forward without him in the loop)