The Communications & Public Affairs (C&PA) department provides official web design guidelines and web publishing guidelines which can help you identify whether your website is a University of Guelph website. Some of the criteria which help identify a University of Guelph website are:
A website that bears the University of Guelph identifier.
A website with a URL that falls under a “uoguelph.ca” domain
A website that is copyrighted by the University of Guelph
A website that is directly controlled by the University of Guelph
If you are unsure whether your website is a University of Guelph website, contact the AODA Web Team by email for guidance.
No. There is no limit to the number of revisions a node can have. A new revision is created every time the "Save" button is selected.
Here are the recommended image sizes for the following features:
Banners: The recommended image size is 1140 x 292 pixels.
Event Featured Image: Images must be between 200x160 and 1140x570 pixels.
Featured Items: Images must be between 380x200 and 1140x570 pixels.
News Featured Image: Images must be between 640x240 and 1140x570 pixels.
Only SiteManagers can see layout options. If you are unable to see layout options that might mean the proper rights have not been given to you. To remediate this contact your SiteManager or the AODA Remediation Team to get the proper roles assigned.
Categories and tags are both vocabular lists created within taxonomies. Categories are specifically tied to a particular feature and are used to organize the feature within the defined terms. Tags are terms that can be shared amongst all features and help tie all the features together under common terms.
It is a good idea to update all your important and current documents to conform to WCAG 2.0 Level AA standards. Providing documents in a range of formats will enable people with different abilities and learning styles to choose the format that works best for them. The Diversity and Human Rights department has a webpage dedicated to document accessibility that clients should visit for more information on how to update their content.
No cases have been brought to light yet so it is uncertian how events will ultimately unfold. However, the responsibility for website conformity rests on the Site Manager(s) and so it will be their duty to ensure the content posted adheres to WCAG 2.0 standards.
The remediation team has many clients with different needs and so we have opted to create a solution that can adapt to as many client needs as possible. The WYSIWYG editor allows this.
Yes. Once a news item is created it gets automatically added to the news archive in
/news as well as added to the news list teaser.
No. The posted date does not change if a user edits the news item. The only time the news item's date will change is if someone edits the authoring date at the bottom of the edit section.
Please contact the DARC Team for Siteimprove access.
Please contact the AODA Remediation Team to add additional authors/editors/sitemanagers to your site.
Yes! With the Drupal platform you have the ability to include RSS feeds as through the Social Media content type.
No, you cannot. In order to limit the amount of ways a site can become inaccessible, the CMS solution we have developed keeps all headings, font colours, and sizes consistent across all pages. This also allows for a more unified University of Guelph branding.
It is the responsibility of the owner/creator of PDFs and other documents to ensure their content conforms to WCAG 2.0 AA standards. It is recommended to not host documents on your webpage if you are not the owner or creator of them, though. Instead, link to the original webpage where the PDF can be accessed.
When you are logged into Drupal you see the most recent changes made to the site when you load a page. For other users, Drupal saves a copy of the website (cache). This "cached" copy of the website will update itself with your new changes anywhere between 5 mins to an hour after making your changes. Thus, if others are not able to see the changes you've just made, their Drupal cache has most likely not updated and they have to wait.