Login or Register to make a submission.

About InULA Notes

We Publish stories about the work you have done with regards to service, instruction, research, or any other cool projects that you have been part of this year. We welcome submissions from both librarian faculty as well as staff.

Articles can range from 500-2,500 words. Images or diagrams are encouraged as long as they follow the accessibility guides (listed below). If you are unsure if your submission idea is a good fit please reach out to us or contact the chair of InULA Communications directly.

InULA Notes does not publish peer-reviewed content.


Author Submission Guidelines for Accessibility:

These directions are to ensure that the final issue is usable, readable, and accessible to adaptive technology. Please reach out to us if you have questions.

Submit all files as a Word document (.docx):

This format is easiest for transferring to a PDF form. It is easy to download a Google Drive Document to a .docx as well, if you don’t have Microsoft Word on the machine you are using.

Document Structure and Headings:

Use headings to structure your document into navigable sections. This makes it easy for users of adaptive technology to “scan” your documents and navigate them. It also makes your document look more inviting to users who aren’t using adaptive technology.

Hypertext Links:

Embed the hyperlink into text. Make sure the text you hyperlink is descriptive and isn’t “Click more” or “Learn more”. Describe what content the user can expect to find if they click on the link. This improves the usability and accessibility of your document.

Examples: “These core skills were taken from the Accessibility U curriculum from the University of Minnesota.”

Not: “Click here to learn more about accessibility.”

The exception to this rule is email addresses: spell those out on the page AND hyperlink them. For example: “Email Jaci at wilkinj@iu.edu .” Not: email Jaci Wilkinson.

Bulleted and Numbered Lists:

Use your word processor’s built-in bulleted list function to organize lists and key concepts. Lists make your document more readable with and without assistive technology. They provide a break in the document’s wall of text which prevents reader burnout. Additionally, numbered lists provide an opportunity to convey procedures in sequential order.

Don’t create lists manually by inserting symbols or numbers. Assistive technology cannot identify these lists.

Color and Images:

When creating graphics, visualizations, or text, test to make sure that all colors have sufficient contrast. Lack of contrast can make information invisible or difficult to read for individuals who have a variety of conditions including color blindness, low vision, or macular degeneration. WebAIM has a free color contrast tool available to use. If any text or visualization colors don’t “pass” the WCAG AA test, please modify the shade.

For graphics, consider using color in combination with another visual technique like pattern to be sure all information is readable. The University of Minnesota has a good example of a before and after pie chart which illustrates this technique for graphical emphasis.

Alt Text:

Alt text is necessary for all visual content (images, graphics, visualizations) unless you have already written a description in an image caption or in the body of your document. These visuals can be in .jpg or .png file format. To add alt text in most word processors (including Word and Google), right click the image and select “Edit alt text”. In Google Docs, there is a title field and description field: put that alt text in the description field and the title field can be left blank.

When crafting good alt text, consider the context and the information you would like conveyed to the reader. For example, an image of a campus building in fall may have simple alt text:“Ball Hall at IUPUI”. But if the image is inserted in an article about fall foliage at IUPUI the following alt text would be more appropriate: “Ball Hall at IUPUI in October and trees with brown, orange, and red leaves”.

For more alt text examples and in-depth explanation, read a post from IU Bloomington’s Discovery and User Experience blog or an alt text article from WebAIM.

View step-by-step directions for using Microsoft Word’s built-in headings from Indiana University’s Accessibility office.

Taken from Accessibility U at the University of Minnesota, WebAIM, and IU’s Accessibility guidelines.