Help! What should we do about jargon?
Jargon and academia often go hand-in-hand, and it’s important to understand the nuance of what jargon is and when to address it before diving in to any jargon remediations. If you are very familiar with remediating jargon, however, please skip to “Should I Remediate All Jargon?” for our recommendations on what to prioritize.
Remediating Jargon
What you might hear if you bring up jargon in higher education….
- Jargon is WCAG level AAA, so considered “best practice” (aka technically optional for the current federal mandate)
- This is higher education, you’re asking me to water it down
- The technical terminology is required/essential to understanding the research
- This was meant for other faculty within this specific discipline
A bonus and often unspoken or implied reason…
- My research has to sound impressive so I can get (grant money / promotion and tenure / the respect of my colleagues)
Who does this impact?
Audience members with hidden disabilities – particularly cognitive or neurodivergent
Some quick examples:
Traumatic Brain Injury (TBI) can make processing large amounts or very technical information more difficult
ADHD or autism can make processing new or large words difficult
Dyslexia can make it difficult to read when there is a lot of unknown or large words
Who else does this impact?
As we know, accessibility is for everyone. So who else benefits from a reduction in jargon?
- Students (disabled students, but also students deciding what discipline to study)
- Children and teenagers (specifically minoritized children/teens who have been told higher education is not for them)
- Academics in other disciplines (grant, award, and conference committees are often interdisciplinary; IRB reviews are often done by broad discipline vs specific specialty reviewers)
- Everyone: is knowledge for the benefit of all, or not?
How to have this discussion
How can we communicate the importance of this to faculty and staff who are publishing content about their research or the department online?
- Start by asking questions: Who do you know reads your content? Who do you imagine or hope reads your content? Who is it possible is reading your content?
- Start small: Some change is always better than no change. Instead of requiring all jargon to be remediated right off the bat, can we compromise on anything being emailed? Content living on the home page?
- Where possible/needed, go to the source: Some faculty can be very particular, and it may be putting staff in a difficult position to ask them to remediate jargon in or about faculty’s work. Instead, involve the faculty member directly in the conversation – or offer to do a workshop for the whole department on the topic.
What does this look like in practice?
Options for remediation:
- Remove jargon and rewrite to a lower reading level
- Offer definitions or explanations for specific words or phrases
- Offer a “lay” version of the original text
These can all be used together, there is no “pick one” requirement.
Should I Remediate All Jargon?
Jargon is everywhere in academia! First, it’s important to prioritize what to address based on the following criteria:
- Is this a primary page of my website (the home page, an “about” page, a top-level navigation page)?
- Is this a page that has important information for prospective or current students?
- How many people will view or access this page? Is this a page that receives a high volume of my website’s traffic? (Site admins for a Sites@UMBC website can view Google analytics to check their site traffic!)
We recommend creating a plan to handle jargon one page at a time, prioritizing primary, high-traffic pages first. At this point in UMBC’s remediation process, we recommend de-prioritizing pages are not also primary, student-facing or high traffic pages that:
- are about individual faculty members or their research history
- are small news updates about upcoming or newly released research (large feature articles or very important research breakthroughs should be considered for jargon!)
- contain research abstracts or book summaries submitted for a specific purpose (e.g., for conferences, panel talks, lectures, etc)
- we recommend updating submission requirements to include a required lay abstract/summary in addition to the standard abstract/summary
Final Remarks
- Lay abstracts are becoming more and more commonplace required parts of applications for journal publications and grants
- Remediating jargon as it is discovered is important
- Proactive strategy for improving the culture around jargon:
- Talk about it in the same way and at the same time we talk about alt text – grouping writing-related topics together
- Host workshops for key campus partners to begin to shift university strategy – communications and marketing, academic affairs, research & creative achievement
- Host workshops for academic departments
- The reduction of jargon improves access to research and higher education…
- for disabled people who deserve and have a right to equal access of information
- across disciplines, allowing for more opportunities for interdisciplinary research to occur
- for k-12 students interacting with UMBC who are unsure about if they have a future in higher education and if college is “meant for them”
- for current UMBC students who are intimidated by the prospect of research or are unsure if they are “cut out” for a specific academic discipline
- for the general public and the court of public opinion of whether or not higher education is relevant and necessary to the average person, which can influence how many tax dollars are spent on research