KU CMS - Common Errors
Here are some common errors experienced by users across the KU CMS as they work to create their KU Sunflower sites.
All PDFs/documents hosted on KU CMS sites must be accessible. Some PDFs have only a small set of issues that can be quickly fixed. However, some will require more time and effort to remediate. You are responsible for checking and remediating them all if they are to remain on your KU CMS site. We encourage you to consider converting PDFs to webpages whenever possible.
See Documents for more information, including recommended strategies and remediation help.
Without exception, all videos hosted (i.e., embedded) on your KU CMS site must include captions - including videos with little or no talking. Additionally, those captions must be accurate (i.e., correctly transcribed, lined up accurately with the video, and free of misspellings). Captions should also include audio descriptions for music and important visual-only elements.
See Videos for more information about captioning.
Although KU CMS Sunflower provides a lot of options (e.g., header sections, buttons, dividers, etc.), you should use them sparingly to create the best user experience. Instead, identify a select group of elements that best meet your design needs and deploy them similarly across the site. Consistency in your choices will help determine how quickly your users understand how your site works.
Descriptive Link Titles
Link titles must be descriptive and tell the user succinctly what resource they will find if they follow the link.
Why? Because links titles may be read aloud by screen readers independent of the contextual information near the link. Imagine hearing a list of link options without context that said, “Link: click here, Link: website, Link: learn more.” Now imagine the same list with descriptive text: “Link: KU CMS Guide, Link: KU Admissions, Link: Our Research.”
Examples of common non-descriptive links include “Click here,” “here,” “website,” and “learn more.” Here are some example pairs showing incorrect and correct link titles:
How Do I Know if My Link Titles Are Descriptive?
To assess your link titles to see if they are descriptive, read all the links on your page aloud as a list. If your link titles provide enough information for a user to make an informed decision, you are good to proceed. But, if the link title is too vague, add the necessary detail so they can make an informed choice.
Document Link Titles
All links to documents and audio/video files on KU CMS site must state explicitly in the link title what the user will find – instead of a webpage - if they select the link. Why? Because link titles need to tell users if they will be taken to a destination other than a webpage. This is important for all users, but especially for those who are experiencing your site via screen reader.
URLs as Link Titles
Link titles must be descriptive and tell the user succinctly what resource they will find if they follow the link. Although URLs tell users literally where they will go, they do not always provide the context. For example, if you already know what CMS means, the URL https://cms.ku.edu might be meaningful to you. But, if you do not know what that means, the descriptive link title KU CMS Guide would provide the context you need to decide if you want to select that link.
Additionally, screen readers read the entire URL letter-by-letter. URLs are often quite long and contain information that may be confusing or irrelevant to the user, which is both unpleasant and time consuming.
Absolute URLs for Links to Internal Pages
When creating links on your KU CMS site, be sure to use relative URLs for your internal pages (e.g., /yourpagename or /node/#). Do not use absolute URLs (i.e., full URL with your development site name) or those links will break automatically when your new site goes live.
- A relative URL assumes that the page you are linking to is on the site and provides only the specific page path or the node (e.g., “/yourpagename” or “/node/427”).
- An absolute URL is when you provide the full path that includes the site name: yoursitename.cms-dev.ku.edu/yourpagename
See URLs for more, including the best way to create relative URLs in Drupal.
Improper Use of Headers
Headers and sub-headers (a.k.a., headlines and sub-headlines, headings and sub-headings) are a critical element of website design, organization and writing that is too often overlooked. Users should be able to find what they are looking for on your website by reading your headers and sub-headers only. Headers have a direct impact on the usability and searchability of your site.
Common Header-related Errors:
- Headers are not concise/simple
- Headers do not reflect the words users would use to search for that information
- Header classes have been applied to statements/long sentences that are not actually headers in the page organization scheme
- Header classes are used out of order (i.e., H1, H2, H3…)
- Headers are used for aesthetics (e.g., font-size, bold) instead of organization and searchability
- Header classes have been unnecessarily bolded
See Headers for more information, including guidelines and best practices.
Header Classes – Out of Order
All pages must follow the basic logic for header classes H1, H2, H3. For example, an H3 cannot occur prior to the establishment of an H2. Only one H1 can appear on any page.
See Headers for more information, including guidelines and best practices.
Header Classes - Used for Aesthetics
All headers across your site should be strategic and reflect page organization, not aesthetics like font-size and boldness. Header class styles can be changed using CSS. See “KU Custom Classes to Mimic Header Styles” on Headers for more information.
The single most important thing you can do to improve your website is have audience-centered content that follows web writing guidelines and best practices. No other strategy has greater potential to positively impact the effectiveness of your website than good web writing.
Common web writing errors include:
- Overly dense text making it difficult to scan and find information
- Need to add bullets and break up paragraphs to make pages more scannable
- Text not tailored for specific audiences
- Headers not well written and/or used properly
See Web Writing for information, including guidelines and best practices.
See Web Writing Checklist for a checklist-style resource.
Pages Not in the Site Menu
The majority of your pages should be findable in the site menu system. Without question all pages that contain important information for your primary audiences belong in the menu. Unless you have a strategic reason not to, put the pages on your site into the menu system.
Why? Users seek information in different ways. Some use the site search. Some start on the homepage and move organically from there. Some use the site menu to find what they are looking for. You want to make it easy on users to find what they are looking for regardless of how they prefer to use the site. If your pages are not in the menu, you remove a primary method of information seeking and increase the likelihood those pages will not be found by some users.
There are some instances where pages can/should remain outside of the site menu system.
Examples of Pages That Can Site Outside the Menu:
- End of the trail pages - These pages typically contain information about a single topic, but have too much information to be included on a primary page.
- Temporary One-off pages - Special pages for temporary topics
- Special landing pages - These pages are often marketing pages designed to deliver users from paid advertising to a special landing page rather than start users on the site homepage.
Common image-related errors include:
- Images do not have alternative text
- Images are pixelated due to lack of quality
- Images do not add value for the user
Stock Photography and Images Without Value for Users
When selecting photos for your site, it is important to avoid two kinds of images:
- Stock photography (i.e, stock photos from non-KU sources)
- Images that do not add emotional or contextual value in direct support of the information on a page
These kinds of images can damage the user experience because they do not provide clear and meaningful value to your users – and it puts a literal barrier between your users and the information they are seeking.
This is especially important in header sections and tops of pages. It is far better to begin with text information that adds value for users than to force them to scroll past an image that provides only aesthetic value.
Images you do not have clear and verifiable rights to use are not permitted on KU CMS websites.
Avoid Images as Text
Whenever possible, avoid using images/graphics that contain large amounts of text. Common examples include graphs and charts, screenshots, etc. If you can, put the text and graphics on the page rather than using a single image to convey the information.
Why? It is difficult to properly describe extensive/complex text and graphics for users experiencing your site via screen reader. The more information in the image, the greater your burden to use alternative text and/or description fields to properly convey the salient details of the image.