130 Results

How-To

Structure and Headings Accessibility

Creating the accessible web is a lot like building a house. Once the knowledge foundation is in place, such as understanding the “who” and “why” of web accessibility, it's time to erect the frame for the information you want to provide. Using structured HTML to create your content and provide the semantic meaning it needs, helps to reach anyone who encounters it. This could be on a laptop, via Braille display, or in ways we haven’t dreamed of yet.

  • Affiliate
  • Faculty
  • Non-UCSF
  • Staff
  • Technical Partner
  • Volunteer
  • Web Services
How-To

Documents Accessibility

An accessible digital document is well-structured, providing visual information in a non-visual format. Examples of digital documents are PDFs and Microsoft Office files. There are many more. They exist on a website, sent in an email, or shared in various ways. The information on this page is specific to Microsoft Word, but the principles apply to all text documents. Building accessibility into the document from the start is best practice.

  • Affiliate
  • Faculty
  • Non-UCSF
  • Staff
  • Technical Partner
  • Volunteer
  • Web Services
How-To

Hosting Your Virtual Events

With COVID-19 and a shift to remote work, UCSF events such as Friday Town Hall Meetings, large training presentations, conventions, press conferences, and emergency communications go virtual with live broadcasts and live streaming.

  • Affiliate
  • Faculty
  • Non-UCSF
  • Staff
  • Student
  • Technical Partner
  • Web Services
How-To

PDF Accessibility

It is as easy to create a PDF document as it is to print a document. If you are only printing, then how the document looks is your only concern. However, sending that PDF document via email or putting it on a website creates different concerns.Once the PDF becomes a "digital document," it is subject to the same accessibility standards as all digital documents at UCSF.

  • Affiliate
  • Faculty
  • Staff
  • Student
  • Technical Partner
  • Volunteer
  • Web Services
How-To

Forms Accessibility

Forms are one of the most common places where accessibility problems occur.Screen readers and keyboard-only users will have issues if you do not take steps to ensure your forms are accessible. An accessible form is one that contains labeled form fields and buttons. Those labels also appear on-screen so that information is available to all users. All form fields and buttons must have explicit labels for the visual user plus in the code.

  • Affiliate
  • Faculty
  • Staff
  • Student
  • Technical Partner
  • Volunteer
  • Web Services
How-To

Images Accessibility

A blind or visually impaired person can use a screen reader to hear a description of the image. If the written content contains the information needed to convey meaning, a very simple description in the image or perhaps even a null alt attribute will do. If not, make sure your alt tag information or surrounding body text is adequate to supply meaning that would be missed in its absence.

  • Affiliate
  • Faculty
  • Staff
  • Student
  • Technical Partner
  • Volunteer
  • Web Services
How-To

Color Accessibility

People with visual impairments interpret color and contrast differently. That makes it difficult or impossible for them to access information communicated only by color.For example, to a user with red/green color blindness, a green image on a red background will not provide enough distinction to make the image visible. This type of color treatment also makes it difficult for some users to read text or identify links that are a different color but don’t have underlines.

  • Affiliate
  • Faculty
  • Non-UCSF
  • Staff
  • Technical Partner
  • Volunteer
  • Web Services