Migration Checklist

The changes introduced in Fawn aims to provide improved user experience and accessibility for UTM websites. With respect to accessibility, all Universities in Ontario must comply with the Web Content Accessibility Guidelines (WCAG) 2.0 Level AA (except for guidelines 1.2.4 and 1.2.5) by Jan 1, 2021. Read more about the AODA.

Migrating to the new theme requires you to clean up your content and take advantage of the new and improved tools. This is not only to improve the look, feel, and experience of your site, but to ensure compliance with AODA as well.

Please review the overview of changes and use the list below to help you identify problem areas and how to fix them once your site has been staged. 

 

1. Feature Image / Box Content

Recreate Feature content as Hero Image content.

The feature image and box content is now deprecated. If your site used a feature image or feature box content type, you must now recreate that content as a Hero Image content.

Learn How: 

 

2. Call to Action Content

Move CTA Blocks to the right sidebar region.

CTA blocks are now limited only to the right side bar region. If you have CTA blocks on any other region other than the right side bar, you must move them. This is also a good opportunity to organize and clean up your CTA content and provide better assets if needed.

Learn How:

 

3. Faculty & Staff Profiles

Use the Faculty & Staff Profiles Content Type.

Using the content type provided for people profiles ensures that it will be responsive and accessible, as well as provide consistency throughout your sites. If your profile content/listing does not use the specified content type and is presented in a way that is non AODA compliant, you must change it.

Learn How:

 

4. Tables

Remove improper use of tables.

Tables are strictly for tabular data. If you are using tables for any other reason than tabular data, you are causing your site to be unaccessible and unresponsive. Do not use tables as a means of organizing your content for layout.

In Fawn, we have introduced multi-column layouts within the Rich Text Editor that does not compromise accessibility. These new tools need to be used in place of tables for layout purposes.

Learn How:

 

5. Formatting & Predefined Styles

Use formats and styles appropriately and keep best practices in mind.

Misuse of formats negatively affects accessibility and experience. Best practices will ensure both visual and semantic consistency for readability and experience across multiple devices including screen readers.

Learn More:

 

6. Social Media

Use the social media contect with us block.

The twitter block has been removed. To provide consistency, use the social media settings to list your social media accounts.

Learn How: