Skip to content
Indiana University Logo
Rivet Design System
  • Components Add-ons Content guide
  • What is Rivet? Blog Roadmap Changelog
  1. February 25, 2021

    Rivet 1.8.0 release

    Rivet 1.8.0 is now available. This release adds border removal utility classes and fixes bugs related to the button, dropdown, and collapsible components.

  2. February 15, 2021

    Rivet announcements: Beta timeline, GitHub Discussions, and 1.8.0 release

    Updates about Rivet's development in the spring and beyond.

  3. January 20, 2021

    Rivet featured on Accessible Code Libraries and Design Patterns list

    Rivet was highlighted alongside the U.S. government, GOV.UK, and Salesforce design systems.

More posts Get updates in your inbox
Install via NPM Download CSS & JS Hosted assets
Navigation
    • Components
    • Add-ons
    • Content guide
    • What is Rivet?
    • Blog
    • Roadmap
    • Changelog
  • Use Rivet
Resources
  • User Experience Office
  • Accessibility Evaluations
  • Rivet Software Design System
  • IU Framework for WCMS
Version 1.8.0
  • Microcopy
    • What is microcopy?
    • Address the user
    • Active voice
    • Plain language and structure
  • Style basics
    • Capitalization
    • Naming conventions
    • Numbers and dates
    • Punctuation
    • Technical terms and acronyms

Technical terms and acronyms

Guidelines for using technical language

Technical terms and acronyms often confuse readers. Avoid them whenever possible.

It’s fine to use technical terms when they’re appropriate for the audience or the situation, but you need to explain what they mean on the first reference. You can also include a short, plain-language summary or define your terms up front.

If an acronym is necessary for future reference, spell the full word and follow with the acronym in parentheses on the first reference. For example, Office of the Vice President for IT (OVPIT).

Accessibility notes

While the <abbr> tag can serve as an enhancement to make acronyms and abbreviations more clear to some users, inconsistent screen reader support means that the expanded abbreviations will not be available to all users, so it’s important to make the same information available within the text of the page.

On this page

    • Accessibility notes
Have a question about Rivet?

We're happy to help! If you've found a bug, typo, or have a request, the best way to get in touch is to create an issue on Github.

For all other questions please feel free to email us at rivet@iu.edu

  • Accessibility
  • Privacy Notice
  • Copyright © The Trustees of Indiana University