Updates to accessibility language

[elletjies]

The term “accommodations” can have different translations across regions (i.e., accommodation = hotel room). To promote clarity and inclusivity, the Community Engagement Team decided to change all references from “accommodations” to “accessibility support” (adding that it is also referred to as accommodations)

Changes included:

Accommodations → accessibility support
Accommodations request → accessibility support request
Accommodations request form → accessibility support request form.

[github-actions]

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:

• 🎯 correct output
• 🖼️ correct figures
• ❓ new warnings
• ‼️ new errors

Rendered Changes

🔍 Inspect the changes: https://github.com/carpentries/instructor-training/compare/md-outputs..md-outputs-PR-1932

The following changes were observed in the rendered markdown documents:

 09-eia.md  | 22 +++++++++++++++-------
 md5sum.txt |  2 +-
 2 files changed, 16 insertions(+), 8 deletions(-)

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-11-12 13:55:02 +0000

[ndporter]

I like the impetus here, but the language "accessibility support" also seems to kind of obscure the difference between accommodation (or other words that fit better in a non-US context) and universal design. That is, UD provides accessibility support, as do accommodations. But accommodations are specifically contrasted because they're reactive instead of proactive. I don't have a better choice to hand (though I'll try to think of one), but I think it does create some side effects in the section contrasting the 2 approaches.

[ndporter]

I put out a call to disability studies colleagues and nobody had better language that wasn't either ambiguous (like "accessibility support") or loaded (afterthought, feigned effort). The closest I got was "reactive modification" which is technically sound but not language anyone uses. So I guess at the end of the day, I'd be in favor of leaving it how it was (accommodation) but adding a note in the instructor notes, but also it's ultimately either Community Engagement Team or Trainer Leadership's call.

[brownsarahm]

That is such an excellent point @ndporter! I love this community.

I think that we can consider two separate cases where we refer to "accommodation" :

1. as a part of Carpentries policy for providing our participants support in cases where our overall goal to do universal design still leaves a gap and people have to request.
2. as an approach to accessibility support in contrast to universal design.

With this delineation, 1. does make sense to change(and has been in some places, via #1925) , but for case 2 we at least need to think more, but I think I actually like Nathaniel's point that maybe we leave it? and we modify the callout to explain?

What are others' thoughts.

[elletjies]

@ndporter and @brownsarahm thank you for your thoughtful feedback! We truly have a fantastic community! The term “accommodation” has often led to confusion, with many "accommodations" requests interpreted as requests for actual lodging from members outside the Global North. After careful consideration, we are moving away from this term and using “accessibility support” instead. I agree that it’s important to note that accessibility support include accommodations, but ultimately the phrasing in the Instructor Training Curriculum is up to you. Please let me know if you need any support from the CET.