Skip to main content
Apply Library A-Z Find a person Maps
Brightspace Email
University
of Victoria
Apply Library A-Z Find a person Maps
Sign in Online tools Sign out
University websites

Accessibility best practices

Web accessibility is about creating content for everyone—including people with different physical and cognitive abilities. As content creators, we must remove barriers that prevent people from doing what they need to do, online.

Making your website accessible is not a one-time project. It's an ongoing process. We all need to be accessibility champions and make our digital content accessible for everyone.

Note: This is a high-level overview of UVic's web standards. Training is available on this topic for content developers and Cascade authors.

WCAG 2.0

The Web Content Accessibility Guidelines (WCAG) is the leading authority on web accessibility. UVic aims for a minimum of level AA compliance, as defined by WCAG.

Accessible text

Page titles

Page titles (or "display names" in some Cascade versions) are very important for accessibility. Your page title is the first thing a screen reader reads to a user.

They are also:

  • visible in the browser window/tab when viewing a web page
  • displayed in search results

Good page titles help people know where they are and move between pages.

Headings

Use headings to break up sections of text; this helps readers digest information.

Users rarely read every word on the page. Most will scan the headings before deciding whether to read the text below.

For people who cannot use a mouse, headings allow a user to navigate to different sections of the page using a keyboard.

Heading levels should follow a logical order:

  • H1 for the page title
    • H2 for major headings
      • H3 for major sub-headings

H4 is used occasionally, and H5 and H6 are rarely used.

Screen readers use descriptive link text to help users understand what to expect when they click on a link. Will they go to a new site (external link) or another page within the same site (internal link)? Will clicking on the link download a file?

Plain language

Aside from how you structure your text, you also need to consider the accessibility of the content itself. Complex content is a barrier to many users.

48% of adult Canadians are estimated to have literacy skills below high school level, while one in every six Canadians is considered functionally illiterate.

This means that 17% of the adult population in Canada isn’t able to fill out forms, follow written instructions, or read maps.
–"A Plain Language Guide for Writing Inclusive Digital Content", 2021.

Find out how to ensure your web content is readable for all audiences.

Accessible images

Screen readers do not understand images. Include meaningful text alternatives to create accessible web content.

Always include a text description when using an image to communicate essential information.

Alt text

Users who are blind or have low vision rely on text alternatives to understand the purpose or context of a photo, figure, graphic, etc. In the web world, this is referred to as “alt text.”

Alt text can be accessed in different ways:

  • people using screen readers will have the text read aloud to them
  • people who have images turned off will see the text in place of the image on the page
  • search engines will crawl the alt text for use in image-based searches

Complex images

Complex images convey more information than can be captured with a simple image description/alt text:

  • charts, figures or graphs
  • maps
  • diagrams or technical illustrations

For these cases, you should provide both a short description in the alt text and a long description (linked from the alt text) which explains the essential information in the image using text.

Accessible video & audio

Multimedia (video and audio) presents unique challenges for accessibility. Use captions, transcripts and/or descriptive audio to ensure your audio and video content is accessible.

Accessible documents

Where possible, use HTML to convey text-based information. If you need to provide a PDF, use the built-in tools from Word, PowerPoint or Acrobat to ensure your document is accessible.

HTML vs PDF

Can you incorporate this content into your website instead of uploading a document? Web pages are easier to read online, and easier to update if information changes.

If you want to give people the option to print, you can provide a “print this page” option to avoid maintaining two sources of information.

When PDFs make sense:

  • secure forms, especially where a signature is required
  • complex design items (brochures, viewbooks, posters) intended for print purposes

In either case, you need an accessible version of the information, either as web page content or an accessible PDF.

PDFs produced through UCAM

University Communications + Marketing (UCAM) is working to make all new PDFs created by their designers accessible when a properly-formatted web page isn’t possible.

If you have existing web PDFs created in partnership with UCAM that need updating for accessibility, please get in touch your UCAM marketing contact.

Accessibility Checker

Normal text

  • 8.59:1 - AA AAA
  • 5.23:1 - AA AAA
  • 4.27:1 - AA AAA
  • 1.47:1 - AA AAA

Large text

  • 8.59:1 - AA AAA
  • 5.23:1 - AA AAA
  • 4.27:1 - AA AAA
  • 1.47:1 - AA AAA