Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

How to Submit

  • Send workflows as documents or links to the Internal Training Team at SILS-TOC-STAFF-TRAINING-L@listserv.ucop.edu) or contact your local IT member: https://uc-sils.atlassian.net/l/c/1BNTk4gh

  • If you have questions about submitting workflows, you can reach out to the Internal Training team at the above listserv or on the #internal-training-questions Slack channel.

  • Submission is ongoing, please submit as you complete workflows.

    • If you submit a workflow and there are subsequent changes to the workflow, please reach out to the Internal Training Team to provide updates so that workflows remain current.

Required or Desired Elements?

  • Descriptive File Title

  • Author?

  • Desired Audience

Format Guidelines for Accessibility and Privacy (move to sub page)

Please submit workflow documentation using the following guidelines to ensure accessibility and currency of information.

Images/Non-Text Content

  • Avoid using screenshots as interfaces in Alma are frequently updated.

  • If using images or graphs, provide a text alternative

    • For all non-decorative images, provide alternative text that conveys the same information as the images. Alternative text should be succinct, but complete and take into account the context of the image.

    • If you use a chart or a complex table, consider adding a caption that describes the contents of the chart, which would be available for visual users and those using assistive technologies

    • When an image is purely decoration and provides no information, ensure that the alt text is blank

    • If you have other types of visual or audio media and aren’t sure how to represent it in a text format, please reach out!

Headings and Lists

Users accessing a site using assistive technology rely on the page structure to navigate, so using headings and lists, can help them (and other users) navigate and comprehend the site more easily.

When using headings, avoid using bold and font sizes, instead use the built-in heading options available, making sure to select the appropriate heading level to structure the content. Similarly, when making a list try to use the built-in list options, rather than using asterisks or other quasi-bullet points.

When creating a link, try to encapsulate where the user will land when they click on the link in the text used, rather than using something like “click here” or just a URL. Screen readers can access a link list for any page, but users only see the hyperlinked text (this text, but not this text). Descriptive link text helps screen reader users navigate web pages more easily.

Do Not Rely on Color Alone

When using color to convey information, be sure that the information can be understood without the use of color. For example, a chart should provide labels in a way that the user will not have to identify which color is associated with each label, an alternative method should be used (for example, by labeling within the sections of the chart or by adding a number or letter to the chart sections and label).

When using color to emphasize parts of a text, consider an alternate way to convey that information, such as restructuring with headers, using bold or italics, or breaking up paragraphs to ensure the important sections stand out.

Privacy

Avoid using examples of identifying information

  • No labels