Last week in our Sign Language Interpreter community, members engaged in meaningful conversations about the evolving standards in legal and court interpreting, the historical significance of RID, and strategies for improving virtual ASL sessions. Recurring discussions on terminology and the requirements for qualified interpreters highlighted the community’s ongoing commitment to professional excellence. Other notable discussions included innovative approaches to Continuous Education Units (CEUs) and the nuances of interpreting tech acronyms.
This Week’s Hot Topics
Seeking vetted ASL legal glossaries
Members are discussing the best resources for ASL legal glossaries, emphasizing the importance of accuracy and reliability in legal settings. Read more here
Modes in court: what’s actually required
There’s a lively conversation about the different modes of interpretation required in court and how to best prepare for them. Read more here
How high for WEEK-later before you switch
This topic explores the timing and context for switching sign language variations, providing practical insights for everyday interpreting. Read more here
Birthplace of RID
A historical dive into where and how the Registry of Interpreters for the Deaf was founded, sparking interest among history buffs in our field. Read more here
Mirror view trivia for interpreters
A fun yet insightful discussion on how mirror views can affect interpreting and what that means for interpreters in training. Read more here
Which law first defined “qualified interpreter”
This thread unravels the legal history of what constitutes a “qualified interpreter” and its implications today. Read more here
Designing CEUs around prosody and reduction
A closer look at how CEUs can be tailored to focus on prosody and reduction, enhancing interpreter skills. Read more here
Adjusting session lengths for virtual ASL
Discussions focus on adapting session lengths to improve effectiveness in virtual ASL settings, a timely topic given the rise in online communication. Read more here
When ‘stool’ means chair — again
This conversation revisits the recurring theme of ambiguous terms like “stool” and how to manage them in interpretation. Read more here
First-mention strategy for tech acronyms
Members are sharing strategies for introducing tech acronyms for the first time in a conversation, ensuring clarity and understanding. Read more here
Wishing everyone a productive week ahead. Keep sharing your experiences and questions—your contributions make this community a valuable resource for all of us.
For virtual court jobs, I keep a shared “gloss doc” with my team (voir dire, stipulation, etc.) and set a 2-word cue with counsel for exhibits — it’s like labeling your spice jars before cooking under pressure. Small caveat: some judges don’t allow chat backchannels, so clear it first, and @Jamal this RID history overview is handy: https://rid.org/about-rid/history/ — it keeps me pushing for ‘qualified’ not just ‘available’ interpreters.
In a remote motion hearing last week, I asked the clerk for the exhibit list 10 minutes early and dropped a tiny numbered gloss in chat (Exh 1–6 + one keyword) so the team and counsel could reference fast — like bookmarking a novel. @Lena, if chat’s off-limits, we mirror the list in a shared note and just say “Exh 3” aloud, but only after the judge okays the workflow.
I ask to be added to the service list a day early so I get the docket and correct name spellings, then request Zoom to spotlight both interpreters and the active speaker — much less whiplash; if court IT locks that down, a quick ‘name, role, mic’ round before each witness keeps things clean.
One thing that’s saved me in virtual ASL sessions: I ask the clerk for a 90‑second pre‑gavel breakout with the Deaf party to confirm fingerspelling/name preferences and camera framing — costs nothing and prevents those moments when evidence starts flying. If the judge won’t allow it, I’ll request brief consecutive just for rights/pleas and back it with NAJIT’s position paper: https://najit.org/resources/position-papers/. Anyone else getting pushback on that lately?